xfs
[Top] [All Lists]

Re: BUG: sleeping function called from invalid context at kernel/rwsem.c

To: "Arjan van de Ven" <arjan@xxxxxxxxxxxxx>
Subject: Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
Date: Mon, 20 Oct 2008 18:58:09 +0400
Cc: "Christoph Hellwig" <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-next@xxxxxxxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=4y7oMEUC3Zjoq6KTYwg6+5mxfDHxVSEl8PfEZlVQw1E=; b=MRuMDDYwQaIkPIorVpFq7VXTiuvDZDkajKtuBdnqD+t9m8M5wNLZFDdR3j9JGHukhx UWIisFtjoNlkIl34WWD/5hOCRWeqqxRXT4L6Q/KOywDvD6l6FkAFuqxDJ7sa1oSpSMJo a/mgs3o8HeDjhnAGGKybtsU0WPxGX4L0l8Cn4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=HfiO15nnQ446lqIQYV+Vfu7PN1c6b/X2I3LP3N0qT0t0Qj2+qEWfCdkzffIfwdom+4 EC3yI1cu5zvUVpQVr14hsXFomwL4ss2oFTK+kif5pQbYvnYY6DTJ1SS2ZicWMaERB3fc ChlN5SiTOKBFAVrVtKCyoz4UrLokLt+IS01pE=
In-reply-to: <20081017135510.7127c4e7@xxxxxxxxxxxxx>
References: <a4423d670810170543vd6b4c39p44bf125610d8540@xxxxxxxxxxxxxx> <20081017164116.GA17375@xxxxxxxxxxxxx> <a4423d670810170954h7ca130aaw8895380a4c6b125@xxxxxxxxxxxxxx> <20081017165738.GA20818@xxxxxxxxxxxxx> <a4423d670810171013g5bc19c1cm3f7d9c014ee70349@xxxxxxxxxxxxxx> <20081017203710.GA27187@xxxxxxxxxxxxx> <20081017135510.7127c4e7@xxxxxxxxxxxxx>
2008/10/18 Arjan van de Ven <arjan@xxxxxxxxxxxxx>:
> On Fri, 17 Oct 2008 16:37:10 -0400
> Christoph Hellwig <hch@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxx>
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.

<Prev in Thread] Current Thread [Next in Thread>