From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: XFS stack corruption: BUG: unable to handle kernel paging request
Date: Wed, 16 Jun 2010 05:41:12 -0400 [thread overview]
Message-ID: <20100616094112.GA16216@infradead.org> (raw)
In-Reply-To: <201006160810.33045@zmi.at>
On Wed, Jun 16, 2010 at 08:10:23AM +0200, Michael Monnerie wrote:
> This happened while I did an "rsync" to that server, and it was searching the files to sync.
> Messages grabbed from the console:
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.
Try backporting commit 070ecdca54dde9577d2697088e74e45568f48efb
"xfs: skip writeback from reclaim context", that should get rid of
places calling into ->writepage with already deep stack usage.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-06-16 9:38 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 [this message]
2010-06-16 10:24 ` Michael Monnerie
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=20100616094112.GA16216@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 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.