From: Linus Torvalds <torvalds@osdl.org>
To: pinotj@club-internet.fr
Cc: nathans@sgi.com, neilb@cse.unsw.edu.au, manfred@colorfullife.com,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Re: [Oops] i386 mm/slab.c (cache_flusharray)
Date: Fri, 5 Dec 2003 15:02:15 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0312051458540.9125@home.osdl.org> (raw)
In-Reply-To: <mnet1.1070665046.1802.pinotj@club-internet.fr>
On Fri, 5 Dec 2003 pinotj@club-internet.fr wrote:
>
> 1. Is it still usefull to get all the backtraces of the last xfs oops ?
No, I'm assuming that was due to the slab interaction.
> 2. I will test patch-slab and patch-xfs on test11,
> CONFIG_DEBUG_PAGEALLOC (only). Test on XFS root and ext3 with "small"
> and "big" kernels.
Sounds good.
> 3. What about patch-bio of Manfred ? I didn't have much time to try it
> yet but seems to stabilize too. Should I use it alone or with the others
> patchs ?
It would be interesting to hear as much as possible about this: if
Manfred's bio patch makes a difference, it's less intrusive than mine, and
as such interesting.
On the other hand, despite the small size of Manfred's patch, it does have
a big impact: since 128 bytes is a "watermark" for the slab debugging, the
patch which appears less intrusive does in fact still cause a big amount
of changes.
Anyway, the more you feel like testing, the better. But use your own
judgements.
Thanks a lot for the effort, btw,
Linus
next prev parent reply other threads:[~2003-12-05 23:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 22:57 Re: [Oops] i386 mm/slab.c (cache_flusharray) pinotj
2003-12-05 23:02 ` Linus Torvalds [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 0:57 pinotj
2003-11-29 17:41 pinotj
2003-12-02 0:36 ` Linus Torvalds
2003-11-27 18:42 pinotj
2003-11-25 17:30 pinotj
2003-11-25 22:51 ` Linus Torvalds
2003-11-24 15:20 pinotj
2003-11-21 18:12 pinotj
2003-11-21 22:48 ` Linus Torvalds
2003-11-20 2:40 pinotj
2003-11-20 1:50 pinotj
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=Pine.LNX.4.58.0312051458540.9125@home.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=nathans@sgi.com \
--cc=neilb@cse.unsw.edu.au \
--cc=pinotj@club-internet.fr \
/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).