From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>
Subject: Re: XFS stack corruption: BUG: unable to handle kernel paging request
Date: Wed, 16 Jun 2010 12:24:50 +0200 [thread overview]
Message-ID: <201006161224.50941@zmi.at> (raw)
In-Reply-To: <20100616094112.GA16216@infradead.org>
[-- Attachment #1.1: Type: Text/Plain, Size: 965 bytes --]
On Mittwoch, 16. Juni 2010 Christoph Hellwig wrote:
> This might as well be another stack overflow. You don't happen to
> have more lines of the stack trace? I fear this might be another
> case of direct reclaim hitting you.
Sorry, no. I thought it looks like it stuck, but that were the last
lines, and the VM didn't react anymore, I had to "force shutdown" it.
> Try backporting commit 070ecdca54dde9577d2697088e74e45568f48efb
> "xfs: skip writeback from reclaim context", that should get rid of
> places calling into ->writepage with already deep stack usage.
As I use a standard openSUSE 11.2 kernel, I'll report a bug at Novell
and they must fix it. Thank you!
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-06-16 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 6:10 XFS stack corruption: BUG: unable to handle kernel paging request Michael Monnerie
2010-06-16 9:41 ` Christoph Hellwig
2010-06-16 10:24 ` Michael Monnerie [this message]
2010-06-16 10:35 ` 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=201006161224.50941@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.