From: David Ford <david+cert@blue-labs.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [OOPS] 2.5.61, rpciod, more NFS issues
Date: Sat, 22 Feb 2003 09:12:19 -0500 [thread overview]
Message-ID: <3E578543.3000107@blue-labs.org> (raw)
Kernel 2.5.61, gcc 3.2.2, Athlon 1Mhz. Reiserfs root filesystem. This
is an NFS client machine.
Unable to handle kernel NULL pointer dereference at virtual address 00000080
printing eip:
c04d7439
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0060:[<c04d7439>] Not tainted
EFLAGS: 00010203
EIP is at rpc_depopulate+0x29/0x270
eax: 00000000 ebx: ce2d025c ecx: 00000080 edx: e7e00000
esi: ce2d025c edi: e673ce08 ebp: e6b69e78 esp: e6b69e3c
ds: 007b es: 007b ss: 0068
Process rpciod (pid: 2099, threadinfo=e6b68000 task=e6bd8e00)
Stack: e673cd88 ce2d025c e6b69e58 c019b4f4 ce2d025c 00000000 fffffff4
e6b69e78
00000080 00000000 e6b69e64 e6b69e64 ce2d025c ce2d025c e673ce08
e6b69ecc
c04d7b9f ce2d025c e3b87504 00000010 e673cd88 e3b87504 e7feab1c
e76803a4
Call Trace:
[<c019b4f4>] simple_lookup+0x24/0x30
[<c04d7b9f>] rpc_rmdir+0x9f/0xc0
[<c04c065a>] rpc_destroy_client+0x2a/0x80
[<c04c8a28>] rpc_release_task+0x2b8/0x4c0
[<c04c7db8>] __rpc_execute+0x4f8/0x590
[<c0108a3c>] __switch_to+0x14c/0x160
[<c04c8054>] __rpc_schedule+0x174/0x3a0
[<c04c931d>] rpciod+0x7d/0x210
[<c0126940>] default_wake_function+0x0/0x20
[<c04c92a0>] rpciod+0x0/0x210
[<c010825d>] kernel_thread_helper+0x5/0x18
Code: ff 88 80 00 00 00 0f 88 0a 0e 00 00 b8 00 e0 ff ff 21 e0 ff
reply other threads:[~2003-02-22 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E578543.3000107@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
/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