From: Christoph Hellwig <hch@infradead.org>
To: Simon Kirby <sim@hostway.ca>
Cc: xfs@oss.sgi.com
Subject: Re: [2.6.33.3] scheduling while atomic (inode reclaim races still?)
Date: Thu, 20 May 2010 05:03:28 -0400 [thread overview]
Message-ID: <20100520090328.GA21428@infradead.org> (raw)
In-Reply-To: <20100520083104.GA4723@hostway.ca>
On Thu, May 20, 2010 at 01:31:04AM -0700, Simon Kirby wrote:
> This started happening on host about 10 days after upgrading to 2.6.33.3
> (in hopes that it fixed all of the reclaim issues present in 2.6.33.2).
> I don't see any fixes in 2.6.33.4 relevant to this particular issue.
>
> After this first error, the kernel logs just filled with repeat
> occurrences with different backtraces.
>
> BUG: scheduling while atomic: nfsd/29671/0x00000250
The bug unfortunately doesn't tell us what caused the "atomic"
situation. But given that XFS doesn't take any spinlock in that path
it seems like this must be caused by nfsd.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-05-20 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 8:31 [2.6.33.3] scheduling while atomic (inode reclaim races still?) Simon Kirby
2010-05-20 9:03 ` 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=20100520090328.GA21428@infradead.org \
--to=hch@infradead.org \
--cc=sim@hostway.ca \
--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