From: Chuck Ebbert <cebbert@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Maciej Soltysiak <solt2@dns.toxicfilms.tv>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.21.14 NFS related oops
Date: Wed, 13 Jun 2007 16:35:02 -0400 [thread overview]
Message-ID: <467054F6.7080604@redhat.com> (raw)
In-Reply-To: <1181762227.6151.55.camel@heimdal.trondhjem.org>
On 06/13/2007 03:17 PM, Trond Myklebust wrote:
> On Wed, 2007-06-13 at 14:00 +0200, Maciej Soltysiak wrote:
>> =======================
>> Code: 10 89 5c 24 10 89 c3 89 7c 24 18 89 d7 89 74 24 14 8b 70 28 75 1a 8b
>> 4e 08 89 fa 89 d8 ff 51 18 8b 5c 24 10 83 74 24 14 8b 7c 24 <18> 83 c4 1c c3
>> 89 74 24 0c 8b 40 10 8b 40 24 8b 40 10 8b 40 08 EIP: [<f0a93c94>]
>> rpcauth_checkverf+0x34/0x70 [sunrpc] SS:ESP 0068:e64b5eec
>
> At a first guess, it looks as though something has scribbled over your
> credential. Have you tried running this kernel with slab debugging
> enabled?
>
Disassembly of this code yields gibberish, like a bit got flipped
somewhere:
1c: ff 51 18 call *0x18(%ecx)
1f: 8b 5c 24 10 mov 0x10(%esp),%ebx
23: 83 74 24 14 8b xorl $0xffffff8b,0x14(%esp)
28: 7c 24 jl 4e <_EIP+0x4e>
0: 18 83 c4 1c c3 89 sbb %al,0x89c31cc4(%ebx) <=====
6: 74 24 je 2c <_EIP+0x2c>
8: 0c 8b or $0x8b,%al
a: 40 inc %eax
b: 10 8b 40 24 8b 40 adc %cl,0x408b2440(%ebx)
11: 10 .byte 0x10
12: 8b 40 08 mov 0x8(%eax),%eax
Somewhere around 23: things went horribly wrong.
At 12: it starts to make sense again.
next prev parent reply other threads:[~2007-06-13 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 12:00 2.6.21.14 NFS related oops Maciej Soltysiak
2007-06-13 19:17 ` Trond Myklebust
2007-06-13 20:35 ` Chuck Ebbert [this message]
2007-06-14 15:34 ` Maciej Soltysiak
2007-06-16 9:26 ` Maciej Sołtysiak
2007-06-16 15:08 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2007-06-20 10:35 Maciej Sołtysiak
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=467054F6.7080604@redhat.com \
--to=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=solt2@dns.toxicfilms.tv \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.