From: Andrew Morton <akpm@linux-foundation.org>
To: Nadia Derbey <Nadia.Derbey@bull.net>,
Manfred Spraul <manfred@colorfullife.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <clameter@sgi.com>
Subject: Re: repeatable slab corruption with LTP msgctl08
Date: Thu, 12 Jun 2008 01:15:37 -0700 [thread overview]
Message-ID: <20080612011537.6146c41d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080612010200.106df621.akpm@linux-foundation.org>
On Thu, 12 Jun 2008 01:02:00 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 11 Jun 2008 23:34:49 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > On Wed, 11 Jun 2008 22:13:24 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > > Running current mainline on my old 2-way PIII. Distro is RH FC1. LTP
> > > version is ltp-full-20070228 (lots of retro-computing there).
> > >
> > > Config is at http://userweb.kernel.org/~akpm/config-vmm.txt
> > >
> > >
> > > ./testcases/bin/msgctl08 crashes after ten minutes or so:
> >
> > ah, it runs to completion in about ten seconds on 2.6.25, so it'll be
> > easy for someone to bisect it.
> >
> > What's that? Sigh. OK. I wasn't doing anything much anyway.
>
> Oh drat. git-bisect tells me that this one-year-old msgctl08's
> execution time vastly increased when we added
>
> commit f7bf3df8be72d98afa84f5ff183e14c1ba1e560d
> Author: Nadia Derbey <Nadia.Derbey@bull.net>
> Date: Tue Apr 29 01:00:39 2008 -0700
>
> ipc: scale msgmni to the amount of lowmem
>
>
> But we already knew that, and LTP got changed to fix it.
>
> So I was wrong in assuming that the long-execution-time correlates with
> the slab-corruption bug.
>
> And the slab corruption bug takes half an hour to reproduce and an
> unknown amount of time to not-reproduce. I don't think I'll be able to
> complete this before I disappear for over a week.
>
Doing
echo 16 > /proc/sys/kernel/msgmni
on the tree at the above bisection point
(f7bf3df8be72d98afa84f5ff183e14c1ba1e560d is most-recently-applied
patch), msgctl08 runs to completion in 15.7 seconds.
Doing the same thing on 2.6.26-rc5-mm3, msgctl08 also runs to
completion, in 20.9 seconds. So
- it got slower
- the crash requires the huge value of /proc/sys/kernel/msgmni (1746)
to reproduce.
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-06-12 8:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 5:13 Andrew Morton
2008-06-12 6:34 ` Andrew Morton
2008-06-12 8:02 ` Andrew Morton
2008-06-12 8:15 ` Andrew Morton [this message]
2008-06-12 8:16 ` Andrew Morton
2008-06-12 8:35 ` Andi Kleen
2008-06-12 9:08 ` Andrew Morton
2008-06-12 10:24 ` Andrew Morton
2008-06-12 10:41 ` Andi Kleen
2008-06-12 10:35 ` Pekka J Enberg
2008-06-12 17:13 ` Christoph Lameter
2008-06-12 18:33 ` Manfred Spraul
2008-06-12 18:41 ` Andrew Morton
2008-06-12 19:09 ` Manfred Spraul
2008-06-12 19:20 ` Andrew Morton
2008-06-12 19:27 ` Pekka Enberg
2008-06-13 7:03 ` Nadia Derbey
2008-06-13 8:33 ` Nadia Derbey
2008-06-13 8:42 ` Andrew Morton
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=20080612011537.6146c41d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Nadia.Derbey@bull.net \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=penberg@cs.helsinki.fi \
/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