From: walt <wa1ter@myrealbox.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: neilb@cse.unsw.edu.au
Subject: [2.6.8-rc4] New nfsd-related kernel panic
Date: Wed, 11 Aug 2004 16:44:41 -0700 [thread overview]
Message-ID: <411AAF69.9080803@myrealbox.com> (raw)
The following patch of 09Aug is causing kernel panics:
$bk get -D fs/nfsd/nfsxdr.c
237d236
< int len;
237a237
> unsigned int len;
269d268
< int len;
269a269
> unsigned int len;
I can cause a kernel panic by mounting the remote filesystem
read-only and merely copying a moderately large tarball from it.
(The linux-kernel source tarball, for example.)
The panic occurs every time, after only a second or two at most.
It's so easy to reproduce that I haven't copied down the backtrace,
but I will if no one else can reproduce the problem.
Anyone else seeing this?
next reply other threads:[~2004-08-11 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 23:44 walt [this message]
2004-08-11 22:52 ` Neil Brown
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=411AAF69.9080803@myrealbox.com \
--to=wa1ter@myrealbox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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®