From: Neil Brown <neilb@suse.de>
To: Mark Hindley <mark@hindley.org.uk>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
nfs@lists.sourceforge.net
Subject: Re: [OOPS] 2.6.23-rc5 in tcp/net/nfsd
Date: Tue, 11 Sep 2007 11:26:52 +0200 [thread overview]
Message-ID: <18150.24412.855004.90148@notabene.brown> (raw)
In-Reply-To: message from Mark Hindley on Tuesday September 11
On Tuesday September 11, mark@hindley.org.uk wrote:
> This oops appeared over night on a box running 2.6.23-rc5 (recent with the
> tcp_input.c fix).
>
> I can't find a similar one reported.
Okay..... this is weird.
>
> Mark
>
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address 0000007e
^^^^^^^^
That is the bad address,
> EFLAGS: 00010246 (2.6.23-rc5-2-mcyrixiii #1)
> EIP is at ip_fragment+0x7f/0x680
> eax: c3c09c00 ebx: 00000000 ecx: b524d006 edx: 0000007b
^^^^^^^^^^^^^
It looks like an offset of 3 from edx. I got that from decoding:
> Code: .... <00> ba 03 00 00 00 bf a6 ff ff
which is
0: 00 ba 03 00 00 00 add %bh,0x3(%rdx)
However that instruction doesn't appear in ip_fragment.
The code in ip_fragment reads:
27: b9 04 00 00 00 mov $0x4,%ecx
^^
2c: ba 03 00 00 00 mov $0x3,%edx
^^^^^^^^^^^^^^
which contains the bytes of the offending instruction.
Note that $0x4 is ICMP_FRAG_NEEDED and $0x3 is ICMP_DEST_UNREACH:
these are args to icmp_send. So the latter is the correct disassembly
based on the C code.
So somehow the kernel is jumping to a bad address. I don't know how
that would happening.... maybe a single bit error in memory or a
register???
NeilBrown
prev parent reply other threads:[~2007-09-11 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 8:32 [OOPS] 2.6.23-rc5 in tcp/net/nfsd Mark Hindley
2007-09-11 9:00 ` Herbert Xu
2007-09-11 9:26 ` Neil Brown [this message]
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=18150.24412.855004.90148@notabene.brown \
--to=neilb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@hindley.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nfs@lists.sourceforge.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).