From: David Ford <david+cert@blue-labs.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Neil Brown <neilb@cse.unsw.edu.au>
Subject: [OOPS] 2.5.53 NFS (rpc.mountd)
Date: Sun, 16 Feb 2003 15:09:14 -0500 [thread overview]
Message-ID: <3E4FEFEA.3030607@blue-labs.org> (raw)
The below is what can happen infrequently after the following has occured:
1) client loses love with server (df reports 1 for all filesystem stats)
2) admin runs 'exportfs -vra' on server
3) client gets love and server burps:
Unable to handle kernel paging request at virtual address 6b6b6b87
printing eip:
c0378b4d
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0060:[<c0378b4d>] Not tainted
EFLAGS: 00010202
EIP is at auth_unix_lookup+0x3d/0x88
eax: 6b6b6b6b ebx: dbdd7b60 ecx: caf3677c edx: 6b6b6b6b
esi: 00000000 edi: dcf85f58 ebp: dbdd7b44 esp: dbdd7b1c
ds: 0068 es: 0068 ss: 0068
Process rpc.mountd (pid: 3677, threadinfo=dbdd6000 task=ddc70760)
Stack: dbdd7b60 dcf85ed0 dbdd7b40 c013d5de dffff600 dcf85ed0 c04067f8
0600000a
00000060 dbdd7f78 dbdd7f78 c01b695d 0600000a 00000008 d6e24914
00000060
dcf85ed4 ad030002 0600000a 00000000 00000000 6961722f 6f682f64
642f656d
Call Trace:
[<c013d5de>] kmalloc+0xaa/0x128
[<c01b695d>] write_getfs+0xbd/0x17c
[<c01b65b1>] fs_write+0x31/0x38
[<c017ac3c>] sys_nfsservctl+0xb4/0xf8
[<c0109283>] syscall_call+0x7/0xb
Code: 8b 40 1c 29 d0 85 c0 7e 0a b8 01 00 00 00 f0 0f ab 41 10 8b
--
I may have the information you need and I may choose only HTML. It's up to you. Disclaimer: I am not responsible for any email that you send me nor am I bound to any obligation to deal with any received email in any given fashion. If you send me spam or a virus, I may in whole or part send you 50,000 return copies of it. I may also publically announce any and all emails and post them to message boards, news sites, and even parody sites. I may also mark them up, cut and paste, print, and staple them to telephone poles for the enjoyment of people without internet access. This is not a confidential medium and your assumption that your email can or will be handled confidentially is akin to baring your backside, burying your head in the ground, and thinking nobody can see you butt nekkid and in plain view for miles away. Don't be a cluebert, buy one from K-mart today.
When it absolutely, positively, has to be destroyed overnight.
AIR FORCE
next reply other threads:[~2003-02-16 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-16 20:09 David Ford [this message]
2003-02-16 22:19 ` [OOPS] 2.5.53 NFS (rpc.mountd) Neil Brown
2003-02-16 22:23 ` David Ford
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=3E4FEFEA.3030607@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox