From: Chuck Ebbert <cebbert@redhat.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: reiserfs-dev@namesys.com
Subject: 4K stack overflow with nfs3, reiserfs, dm and raid1
Date: Fri, 20 Apr 2007 13:47:10 -0400 [thread overview]
Message-ID: <4628FC9E.9080503@redhat.com> (raw)
4K stacks still overflow:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237276
Just trying to dump the stack trace when that happens causes an oops,
and there's no good way to prevent that. In fact it's probably the
best thing to do anyway.
You can tell something Really Bad has happened because of this:
> Process nfsd (pid: 2815, ti=f3f49000 task=f582d7b0 task.ti=f3f4a000)
Note that ti and task.ti don't agree.
P. S. Does reiserfs really need to use that much stack?
reply other threads:[~2007-04-20 17:47 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=4628FC9E.9080503@redhat.com \
--to=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
/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