From: Andrew Morton <akpm@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: reuben-linux@reub.net, netdev@oss.sgi.com
Subject: Re: Kernel crash in 2.6.0-test9-mm3
Date: Tue, 18 Nov 2003 18:02:08 -0800 [thread overview]
Message-ID: <20031118180208.55eb0a14.akpm@osdl.org> (raw)
In-Reply-To: <20031118164944.54544c39.davem@redhat.com>
"David S. Miller" <davem@redhat.com> wrote:
>
> On Tue, 18 Nov 2003 11:01:39 -0800
> Andrew Morton <akpm@osdl.org> wrote:
>
> > It's one for the networking guys.
> >
> > The mm kernels have a patch which detects when atomic_dec_and_test
> > takes an atomic_t negative - it is assumed that this is a bug so
> > a warning is generated.
>
> Andrew I've analyzed this a bit. This is incredible evidence in
> these dumps that either there is a bug in Linus's atomic_dec_and_test()
> debugging hack or GCC is miscompiling it in certain cases with certain
> versions of the compiler.
>
> Look at this:
>
> > > Nov 18 23:09:00 tornado kernel: [<c029203c>] skb_release_data+0x14c/0x160
> > > Nov 18 23:09:00 tornado kernel: [<c0292063>] kfree_skbmem+0x13/0x30
> > > Nov 18 23:09:00 tornado kernel: [<c0292138>] __kfree_skb+0xb8/0x1b0
> > > Nov 18 23:09:00 tornado kernel: [<c0218815>] e100intr+0x1e5/0x290
>
> Ok, releasing an SKB data area twice.
>
> > > Nov 18 23:09:00 tornado kernel: BUG: dst underflow 0: c02921ef
>
> Freeing a 'dst' entry one too many times.
>
> > > Nov 18 23:09:00 tornado kernel: Attempt to release alive inet socket dfd4c780
>
> A socket refcount dropping to zero too early, before it's marked dead.
>
> These last two problems are very serious errors, and would have
> printed out debugging messages before the atomic_dec_and_test() patch.
> If these last two messages don't show up without the
> atomic_dec_and_test() debugging patch applied, well there you
> go... :-)
>
> In that debugging patch, I'm wondering something about x86.
> When one goes "sete %reg; sets %reg" does the first 'sete' modify
> the condition codes by chance? Probably not...
Beats me David. This is the only time where the correctness of that patch
has been questioned.
Reuben, can you please do a patch -R of
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm3/broken-out/atomic_dec-debug.patch
and see if the problem goes away?
next prev parent reply other threads:[~2003-11-19 2:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6.0.1.1.2.20031118232152.01ae5728@tornado.reub.net>
2003-11-18 19:01 ` Kernel crash in 2.6.0-test9-mm3 Andrew Morton
2003-11-18 22:22 ` David S. Miller
2003-11-19 0:49 ` David S. Miller
2003-11-19 1:22 ` Reuben Farrelly
2003-11-19 2:02 ` Andrew Morton [this message]
2003-11-19 2:22 Krishna Kumar
2003-11-19 2:24 ` David S. Miller
2003-11-19 2:58 ` Reuben Farrelly
[not found] ` <20031119185157.3edf69c8.davem@redhat.com>
2003-11-20 3:05 ` Reuben Farrelly
[not found] ` <20031119190258.4d926957.davem@redhat.com>
2003-11-20 7:30 ` Reuben Farrelly
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 2:40 Feldman, Scott
2003-11-23 20:29 ` Rask Ingemann Lambertsen
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=20031118180208.55eb0a14.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=reuben-linux@reub.net \
/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).