From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Martin Hamrle <martin.hamrle@nangu.tv>, xfs@oss.sgi.com
Subject: Re: [2.6.32] scheduling while atomic
Date: Tue, 2 Nov 2010 12:02:01 -0400 [thread overview]
Message-ID: <20101102160201.GA924@infradead.org> (raw)
In-Reply-To: <20101102001244.GP2715@dastard>
On Tue, Nov 02, 2010 at 11:12:44AM +1100, Dave Chinner wrote:
> With a trace like that, it's almost certain that you've blown
> the stack and that is why the system is crashing. Can you turn on
> stack depth checking (might require a kernel rebuild) so we can tell
> if these problems are a result of overruning the stack?
Even better move on to a recent kernel - we're now preventing the
VM from reentering the filesystem for reclaim, which should take
care of all practical stack overlfow issues.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-11-02 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 15:11 [2.6.32] scheduling while atomic Martin Hamrle
2010-11-02 0:12 ` Dave Chinner
2010-11-02 16:02 ` Christoph Hellwig [this message]
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=20101102160201.GA924@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=martin.hamrle@nangu.tv \
--cc=xfs@oss.sgi.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