mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel J Blueman" <daniel.blueman@gmail.com>
To: "Ian Soboroff" <isoboroff@gmail.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Oops in NFS (RHEL4, but also in kernel bugzilla)
Date: Mon, 23 Jun 2008 19:17:11 +0100	[thread overview]
Message-ID: <6278d2220806231117v551d93f1o7ecb5c7558a62b96@mail.gmail.com> (raw)
In-Reply-To: <9cfod5sayiq.fsf@rogue.ncsl.nist.gov>

On Mon, Jun 23, 2008 at 5:47 PM, Ian Soboroff <isoboroff@gmail.com> wrote:
> The following message is a courtesy copy of an article
> that has been posted to gmane.linux.kernel as well.
>
> "Daniel J Blueman" <daniel.blueman@gmail.com> writes:
>
>> Has 4KB stacks been disabled? You can check the config file for
>> CONFIG_4KSTACKS.
>
> This kernel has 4KSTACKS enabled.

There is chance that you've overrun the 4KB stack. Can you retest with
CONFIG_4KSTACK disabled perhaps?

>> It may also be worth feeding that into the bugzilla entry, to
>> eliminate one possibility, as 'bad EIP value' looks suspicious of
>> stack corrption.
>
> Ok, will do.  Although that bugzilla entry is from 2007 and no one seems
> to have looked at it at all...
-- 
Daniel J Blueman

  reply	other threads:[~2008-06-23 18:17 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 [this message]
     [not found]     ` <ebd55800806231129k110febb6rc2edfc18a7af5588@mail.gmail.com>
2008-06-23 18:30       ` Ian
  -- 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=6278d2220806231117v551d93f1o7ecb5c7558a62b96@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --cc=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®