From: Bob Copeland <me@bobcopeland.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Eric Paris <eparis@redhat.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org
Subject: Re: 2.6.32-rc6 BUG at mm/slab.c:2869!
Date: Fri, 21 Aug 2009 08:36:57 -0400 [thread overview]
Message-ID: <20090821123657.GA27001@hash.localnet> (raw)
In-Reply-To: <19f34abd0908202346p57de93bew257b046899d7a1da@mail.gmail.com>
On Fri, Aug 21, 2009 at 08:46:37AM +0200, Vegard Nossum wrote:
> 2009/8/21 Bob Copeland <me@bobcopeland.com>:
> > WARNING: kmemcheck: Caught 32-bit read from freed memory (f34a443c)
> > eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee008a06f700011000
> > a a a a a a a a a a a a a a a a a a a a a a a a f f f f f f f f
> >
> > I think that is list_empty() here where %eax is list_head
> > and event_list->next is the read location... which definitely
> > doesn't look like a pointer, if I'm reading it correctly.
>
> I think f34a443c is a valid pointer. On my machine, at least:
I meant list->next, which was 00100100 here. (By the way, my first
time using kmemcheck, very nice tool!)
[race condition explanation snipped]
> I think that's it. Any thoughts? I put Eric Paris on Cc.
Thanks! With a fresh pull containing the fsnotify fix the kmemcheck
warning is gone. So unless I see anything else I'll assume that this
one is already fixed, sorry for the false alarm.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-08-21 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090820015624.GE524@hash.localnet>
2009-08-20 5:08 ` 2.6.32-rc6 BUG at mm/slab.c:2869! Pekka Enberg
2009-08-20 11:19 ` Bob Copeland
2009-08-20 12:02 ` Vegard Nossum
2009-08-21 2:06 ` Bob Copeland
2009-08-21 6:46 ` Vegard Nossum
2009-08-21 8:28 ` Vegard Nossum
2009-08-21 13:00 ` Eric Paris
2009-08-21 12:34 ` Eric Paris
2009-08-21 12:36 ` Bob Copeland [this message]
2009-08-21 12:39 ` Pekka Enberg
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=20090821123657.GA27001@hash.localnet \
--to=me@bobcopeland.com \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@gmail.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).