Benjamin LaHaise <b...@kvack.org> writes: >> >> [ 186.339064] ioctx_alloc: nr_events=-2 aio_max_nr=65536 >> [ 186.339065] ioctx_alloc: nr_events=-2 aio_max_nr=65536 >> [ 186.339067] ioctx_alloc: nr_events=-2 aio_max_nr=65536 >> [ 186.339068] ioctx_alloc: nr_events=-2 aio_max_nr=65536 >> [ 186.339069] ioctx_alloc: nr_events=-2 aio_max_nr=65536 > > Something is horribly wrong here. There is no way that value for nr_events > should be passed in to ioctx_alloc(). This implies that userland is calling > io_setup() with an impossibly large value for nr_events. Can you post the > actual diff for your fs/aio.c relative to linus' tree? >
fio does exactly this! it passes INT_MAX. Cheers, Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
