From: Daniel McNeil <daniel@osdl.org>
To: Suparna Bhattacharya <suparna@in.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, "linux-aio@kvack.org" <linux-aio@kvack.org>
Subject: Re: 2.6.0-test9-mm2 - AIO tests still gets slab corruption
Date: 12 Nov 2003 12:10:34 -0800 [thread overview]
Message-ID: <1068667834.1817.13.camel@ibm-c.pdx.osdl.net> (raw)
In-Reply-To: <20031111150229.GA4345@in.ibm.com>
Suparna,
I ran some AIO tests on your lastest patch and do not get any slab
corruptions. However, when I used different i/o sizes (the default is
64k), it looks like the AIOs never complete. I updated my tests to add
more debug output (with -d option). As usual, the tests are here:
http://developer.osdl.org/daniel/AIO/TESTS/
FYI, '-r' sets the readsize.
'-w' sets the writesize.
'-s' sets the filesize.
The tests hang waiting for the AIO writes to complete. I had to hit
^c to get out of the tests. No messages on the console.
Examples:
$ ./aiodio_sparse -d -s 180k -r 18k -w 18k
io_submit() return 10
aiodio_sparse: 10 i/o in flight
child 2223, read loop count 0
child 2223, read loop count 10
(The writes never complete)
$ ./aiodio_sparse -dd -s 180k -r 18k -w 11k
child 2128, read loop count 0
io_submit() return 16
aiodio_sparse: 16 i/o in flight
aiodio_sparse: offset 180224 filesize 184320 inflight 16
aiodio_sparse: io_getevent() returned 1
aiodio_sparse: io_getevent() res 11264 res2 0
io_submit() return 1
child 2128, read loop count 10
(1 write returns, then no more)
$ ~/AIO/AIO_TESTS/aiodio_sparse -dd -s 160k -r 18k -w 18k
[....]
io_submit() return 1
aiodio_sparse: offset 349184 filesize 1793024 inflight 16
aiodio_sparse: io_getevent() returned 1
aiodio_sparse: io_getevent() res 11264 res2 0
io_submit() return 1
aiodio_sparse: offset 360448 filesize 1793024 inflight 16
child 2300, read loop count 20
child 2300, read loop count 30
(writes complete for a while and then stop).
Let me know if you want me to test something else.
Thanks,
Daniel
On Tue, 2003-11-11 at 07:02, Suparna Bhattacharya wrote:
> On Mon, Nov 10, 2003 at 03:42:32PM -0800, Andrew Morton wrote:
> > Daniel McNeil <daniel@osdl.org> wrote:
> > >
> > > Andrew,
> > >
> > > test9-mm2 is still getting slab corruption with AIO:
> >
> > Why?
> >
> > > Maximal retry count. Bytes done 0
> > > Slab corruption: start=dc70f91c, expend=dc70f9eb, problemat=dc70f91c
> > > Last user: [<c0192fa3>](__aio_put_req+0xbf/0x200)
> > > Data: 00 01 10 00 00 02 20 00 *********6C ******************************A5
> > > Next: 71 F0 2C .A3 2F 19 C0 71 F0 2C .********************
> > > slab error in check_poison_obj(): cache `kiocb': object was modified after freeing
> > >
> > > With suparna's retry-based-aio-dio patch, there are no kernel messages
> > > and the tests do not see any uninitialized data.
> > >
> > > Any reason not to add suparna's patch to -mm to fix these problems?
> >
> > It relies on infrastructure which is not present in Linus's kernel. We
> > should only be interested in fixing mainline 2.6.x.
> >
> > Furthermore I'd like to see the direct-vs-buffered locking fixes fully
> > implemented against Linus's tree, not -mm. They're almost there, but are
> > not quite complete. Running off and making it dependent on the retry
> > infrastructure is not really helpful.
> >
>
> It was just easier to do this in a non-kludgy way, if we used the
> retry infrastructure. Here's why:
>
> For fixing some of the cases, we run into a situation when we've
> already submitted some of the I/O as AIO (with AIO callbacks set up)
> by the time we realise that we actually need to wait for that to
> complete synchronously before falling back to buffered i/o (otherwise
> we can corrupt file data).
>
> With the retry model it is only the actual wait that occurs
> differently for AIO and Sync I/O, not the submission. So we
> can simply switch to be synchronous at the latter stage.
>
> Having done that, though, I was actually working on trying
> to find a way to do this that could hold for the mainline as well
> (i.e. without using retry infrastructure). The attached patch has
> some special casing tweaks that might do the job; it
> modifies the AIO-DIO callback to wakeup the caller synchronously
> instead of issuing an aio_complete in such situations.
>
> However the existing aio-dio tests do not seem to exercise some
> of those code paths, so I haven't had a chance to verify
> if it really works for that case (i.e. A single AIO-DIO request
> overwriting an allocated region followed by a hole).
>
> The patch should apply to 2.6.0-test9-mm2.
>
> Regards
> Suparna
next prev parent reply other threads:[~2003-11-12 20:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 6:55 2.6.0-test9-mm2 Andrew Morton
2003-11-05 12:30 ` 2.6.0-test9-mm2 Alexander Hoogerhuis
2003-11-05 16:10 ` 2.6.0-test9-mm2 (compile stats) John Cherry
2003-11-05 17:02 ` 2.6.0-test9-mm2 Alistair John Strachan
2003-11-05 23:07 ` 2.6.0-test9-mm2 Martin J. Bligh
2003-11-10 23:06 ` 2.6.0-test9-mm2 - AIO tests still gets slab corruption Daniel McNeil
2003-11-10 23:42 ` Andrew Morton
2003-11-11 15:02 ` Suparna Bhattacharya
2003-11-12 20:10 ` Daniel McNeil [this message]
2003-11-13 11:29 ` Suparna Bhattacharya
2003-11-11 18:01 ` [PATCH 2.6.0-test9] AIO-ref-count.patch Daniel McNeil
2003-11-11 17:25 ` 2.6.0-test9-mm2 Daniel Drake
2003-11-12 1:18 ` 2.6.0-test9-mm2 Nick Piggin
2003-11-12 3:45 ` 2.6.0-test9-mm2 Mike Fedyk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1068667834.1817.13.camel@ibm-c.pdx.osdl.net \
--to=daniel@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=suparna@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).