From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: xfs stack overrun, unable to handle kernel paging request
Date: Fri, 15 Apr 2011 02:02:02 -0400 [thread overview]
Message-ID: <20110415060202.GA32250@infradead.org> (raw)
In-Reply-To: <201104150631.38169@zmi.at>
On Fri, Apr 15, 2011 at 06:31:29AM +0200, Michael Monnerie wrote:
> Not sure if I didn't already post a similar crash once. This ist kernel
> 2.6.31.14-0.6-xen from openSUSE 11.2
That's still without the commits I pointed out to avoid direct reclaim
hitting the filesystem, right? Unfortunately the stack trace is
truncate so it's not possible to spot where it originated, but I suspect
it's the cause for this one as well.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-15 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 4:31 xfs stack overrun, unable to handle kernel paging request Michael Monnerie
2011-04-15 6:02 ` Christoph Hellwig [this message]
2011-04-15 6:11 ` Michael Monnerie
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=20110415060202.GA32250@infradead.org \
--to=hch@infradead.org \
--cc=michael.monnerie@is.it-management.at \
--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