From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Paul Blazejowski <paulb@blazebox.homeip.net>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.5-rc3-mm4
Date: Sun, 04 Apr 2004 19:34:42 -0400 [thread overview]
Message-ID: <1081121682.2585.30.camel@lade.trondhjem.org> (raw)
In-Reply-To: <32948.192.168.0.250.1081041322.squirrel@192.168.0.250>
On Sat, 2004-04-03 at 20:15, Paul Blazejowski wrote:
> Under kernel 2.6.5-rc3-mm4 i get a nice oops when trying to see the
> contents of NFS export from BSD box.The NFS share gets mounted and shows:
>
> blazebox:/usr/home/paul on /mnt/nfs type nfs (rw,addr=192.168.0.1)
>
> but any attempt to browse using ls or nautilus etc... gets seg faulted.
>
> dmesg:
>
> Unable to handle kernel NULL pointer dereference at virtual address 00000002
> printing eip:
> 43bdb08f
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT
> CPU: 0
> EIP: 0060:[<43bdb08f>] Tainted: P VLI
> EFLAGS: 00010206 (2.6.5-rc3-mm4)
> EIP is at nfs3_decode_dirent+0xf/0x250 [nfs]
If it hadn't been for Andrew sending me a copy this mail would have gone
straight to /dev/null. Please ensure that you label NFS-related mails
with a clear "NFS" in the subject header if you want me to notice them.
Nobody has enough free time on their hands to spend reading all 1000
LKML emails each day.
Mind sending me a binary tcpdump of that readdir? Please use something
like
tcpdump -s 9000 -w dump.out port 2049 and host insert_name_of_server
Cheers,
Trond
next prev parent reply other threads:[~2004-04-04 23:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 1:15 2.6.5-rc3-mm4 Paul Blazejowski
2004-04-04 23:34 ` Trond Myklebust [this message]
2004-04-05 1:25 ` 2.6.5-rc3-mm4 Paul Blazejowski
-- strict thread matches above, loose matches on Subject: below --
2004-04-02 3:09 2.6.5-rc3-mm4 Sid Boyce
2004-04-03 11:08 ` 2.6.5-rc3-mm4 Sid Boyce
2004-04-01 10:05 2.6.5-rc3-mm4 Andrew Morton
2004-04-01 12:02 ` 2.6.5-rc3-mm4 Marc-Christian Petersen
2004-04-01 15:16 ` 2.6.5-rc3-mm4 Greg KH
2004-04-01 15:32 ` 2.6.5-rc3-mm4 Marc-Christian Petersen
2004-04-01 14:12 ` 2.6.5-rc3-mm4 Norberto Bensa
2004-04-02 1:35 ` 2.6.5-rc3-mm4 Joshua Kwan
2004-04-02 2:09 ` 2.6.5-rc3-mm4 Norberto Bensa
2004-04-02 19:04 ` 2.6.5-rc3-mm4 markw
2004-04-02 19:56 ` 2.6.5-rc3-mm4 Andrew Morton
2004-04-02 20:46 ` 2.6.5-rc3-mm4 markw
2004-04-02 23:43 ` 2.6.5-rc3-mm4 Nick Piggin
2004-04-03 0:10 ` 2.6.5-rc3-mm4 Mark Wong
2004-04-03 0:12 ` 2.6.5-rc3-mm4 Nick Piggin
2004-04-06 15:20 ` 2.6.5-rc3-mm4 markw
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=1081121682.2585.30.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulb@blazebox.homeip.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
all inboxes | Powered by JetHome®