From: "Alexander Beregalov" <a.beregalov@gmail•com>
To: Arjan van de Ven <arjan@infradead•org>
Cc: Christoph Hellwig <hch@infradead•org>,
xfs@oss•sgi.com, linux-next@vger•kernel.org,
LKML <linux-kernel@vger•kernel.org>
Subject: Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
Date: Mon, 20 Oct 2008 18:58:09 +0400 [thread overview]
Message-ID: <a4423d670810200758m3cea3841h40988afc8eaf81@mail.gmail.com> (raw)
In-Reply-To: <20081017135510.7127c4e7@infradead.org>
2008/10/18 Arjan van de Ven <arjan@infradead•org>:
> On Fri, 17 Oct 2008 16:37:10 -0400
> Christoph Hellwig <hch@infradead•org> wrote:
>
>> I just ran the xfs testsuite over linux-next on qemu (i386), and I
>> can't find anything at all. Really strange. Let's see if this still
>> there with mondays linux-next, and if yes can you just try the xfs
>> patch from the splitout linux-next patches and see if that alone
>> causes it?
Hi Christoph
I have the same result with next-1020 and today's xfs-2.6.git/master
(
commit bfd2bd10da76378dc4afd87d7d204a1d3d70b347
Author: David Chinner <david@fromorbit•com>
Date: Fri Oct 17 15:36:23 2008 +1000
Inode: Allow external list initialisation
)
Should I start bisecting?
>>
>> In fact that might be useful for todays linux-next, too.
>> --
>
> also if you enable lockdep, it tracks where irq's got turned off (with
> a stacktrace I think) so it would provide some good clues.
Yes, lockdep was enabled, but there is no more information than I
already posted.
next prev parent reply other threads:[~2008-10-20 14:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 12:43 BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17) Alexander Beregalov
2008-10-17 16:41 ` Christoph Hellwig
2008-10-17 16:54 ` Alexander Beregalov
2008-10-17 16:57 ` Christoph Hellwig
2008-10-17 17:13 ` Alexander Beregalov
2008-10-17 20:37 ` Christoph Hellwig
2008-10-17 20:55 ` Arjan van de Ven
2008-10-20 14:58 ` Alexander Beregalov [this message]
2008-10-20 16:33 ` Christoph Hellwig
2008-10-20 17:13 ` Alexander Beregalov
2008-10-20 22:35 ` Dave Chinner
2008-10-21 11:42 ` Alexander Beregalov
2008-10-22 7:58 ` Dave Chinner
2008-10-22 8:21 ` Alexander Beregalov
2008-10-22 8:28 ` Dave Chinner
2008-10-22 8:25 ` Dave Chinner
2008-10-22 9:12 ` Alexander Beregalov
2008-10-22 10:13 ` Christoph Hellwig
2008-10-22 21:10 ` Dave Chinner
2008-10-22 15:06 ` BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? Johannes Weiner
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=a4423d670810200758m3cea3841h40988afc8eaf81@mail.gmail.com \
--to=a.beregalov@gmail$(echo .)com \
--cc=arjan@infradead$(echo .)org \
--cc=hch@infradead$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=xfs@oss$(echo .)sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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