[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49k37l1c6p.fsf@segfault.boston.devel.redhat.com>
Date: Thu, 10 Jul 2014 11:11:10 -0400
From: Jeff Moyer <jmoyer@...hat.com>
To: Benjamin LaHaise <bcrl@...ck.org>
Cc: "Elliott\, Robert \(Server Storage\)" <Elliott@...com>,
Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@...radead.org>,
"dgilbert\@interlog.com" <dgilbert@...erlog.com>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Bart Van Assche <bvanassche@...ionio.com>,
"linux-scsi\@vger.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: scsi-mq V2
Benjamin LaHaise <bcrl@...ck.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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists