From: Ian <isoboroff@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Oops in NFS (RHEL4, but also in kernel bugzilla)
Date: Mon, 23 Jun 2008 14:30:20 -0400 [thread overview]
Message-ID: <ebd55800806231130l406f5490sc7c19f202ef81f8b@mail.gmail.com> (raw)
In-Reply-To: <ebd55800806231129k110febb6rc2edfc18a7af5588@mail.gmail.com>
On Mon, Jun 23, 2008 at 2:17 PM, Daniel J Blueman
<daniel.blueman@gmail.com> wrote:
> There is chance that you've overrun the 4KB stack. Can you retest with
> CONFIG_4KSTACK disabled perhaps?
Testing is hard as the oops is not easily reproducible, but I'll
prepare a non-4KSTACKS kernel so that I can boot to it if we oops
again.
I'm still interested to hear from someone if the patch in bugzilla is
good for catching a real error case, or if it's papering over a larger
problem (for example a stack overrun).
Ian
next prev parent reply other threads:[~2008-06-23 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 2:33 Daniel J Blueman
2008-06-23 16:47 ` Ian Soboroff
2008-06-23 18:17 ` Daniel J Blueman
[not found] ` <ebd55800806231129k110febb6rc2edfc18a7af5588@mail.gmail.com>
2008-06-23 18:30 ` Ian [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-17 15:15 Ian Soboroff
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=ebd55800806231130l406f5490sc7c19f202ef81f8b@mail.gmail.com \
--to=isoboroff@gmail.com \
--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
all inboxes | Powered by JetHome®