From: Andrew Morton <akpm@osdl.org>
To: Daniel McNeil <daniel@osdl.org>
Cc: suparna@in.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-aio@kvack.org
Subject: Re: 2.6.0-test9-mm2 - AIO tests still gets slab corruption
Date: Mon, 10 Nov 2003 15:42:32 -0800 [thread overview]
Message-ID: <20031110154232.55eb9b10.akpm@osdl.org> (raw)
In-Reply-To: <1068505605.2042.11.camel@ibm-c.pdx.osdl.net>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@osdl.org>
To: Daniel McNeil <daniel@osdl.org>
Cc: suparna@in.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-aio@kvack.org
Subject: Re: 2.6.0-test9-mm2 - AIO tests still gets slab corruption
Date: Mon, 10 Nov 2003 15:42:32 -0800 [thread overview]
Message-ID: <20031110154232.55eb9b10.akpm@osdl.org> (raw)
In-Reply-To: <1068505605.2042.11.camel@ibm-c.pdx.osdl.net>
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.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-11-10 23:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 6:55 2.6.0-test9-mm2 Andrew Morton
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 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 16:10 ` John Cherry
2003-11-05 17:02 ` 2.6.0-test9-mm2 Alistair John Strachan
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-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:06 ` Daniel McNeil
2003-11-10 23:42 ` Andrew Morton [this message]
2003-11-10 23:42 ` Andrew Morton
2003-11-11 15:02 ` Suparna Bhattacharya
2003-11-11 15:02 ` Suparna Bhattacharya
2003-11-12 20:10 ` Daniel McNeil
2003-11-12 20:10 ` Daniel McNeil
2003-11-13 11:29 ` Suparna Bhattacharya
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-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 1:18 ` 2.6.0-test9-mm2 Nick Piggin
2003-11-12 3:45 ` 2.6.0-test9-mm2 Mike Fedyk
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=20031110154232.55eb9b10.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=daniel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.