xfs
[Top] [All Lists]

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

To: "Christoph Hellwig" <hch@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: Fri, 17 Oct 2008 20:54:35 +0400
Cc: 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=/TLh6w3xaGUErGYqC788fSzfN3y7wi0oLcujMORjtfQ=; b=x4rRSVrKt6zpHJfitdzO85E2UyAXdgN4IqdQJUxDQH2dD/K22fuVevpKeduVr/tEa2 BrVSLKJoBP98hz9rBt054BVa+CQC0/Mg7hKo4lTmyHPspnMJArvY4xQvdCn4iwEcEHYv 3pIXsHjD/MLwPOe1Y3wHmxUl5gf+/Ibnw062A=
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=kQGsT8+Gh34JGRc2dNXKKCjP6BNlnYLWeJRmEwuTf7gHg0az7I3y7orCrUUIFEu9bo CRiowa6/5F2/TeMUFG+2MVLnkTipQAp5l6LETN+LDKJun0ZaYweohcqyxvG8t0p7Fyek gP1SDnzVrRFrxEkCYHYQbOOrzJvvXG4+eHj98=
In-reply-to: <20081017164116.GA17375@xxxxxxxxxxxxx>
References: <a4423d670810170543vd6b4c39p44bf125610d8540@xxxxxxxxxxxxxx> <20081017164116.GA17375@xxxxxxxxxxxxx>
2008/10/17 Christoph Hellwig <hch@xxxxxxxxxxxxx>:
> On Fri, Oct 17, 2008 at 04:43:07PM +0400, Alexander Beregalov wrote:
>> It is SMP x86_64, rootfs is on XFS
>
> The message comes from code in XFS, but I really wonder where the atomic
> context comes from.  xfs_iget_core has a few changes in the tree pulled
> into todays Linux-next, but it's still missing the recent updates
> redoing this area completely.  In some ways it looks like this process
> has the the atomic context flag left pending somewhere, but that should
> also trigger warnings on the VFS locks like i_mutex.
>
> Very misterious.
>
> IS there a specific workload you can reproduce this with?
>
Workload is not specific, many i/o commands trigger the message.

 dmesg|grep comm:
[    4.419605] Pid: 1396, comm: mkdir Not tainted 2.6.27-next-20081017 #2
[    6.056443] Pid: 1782, comm: dhcpcd Not tainted 2.6.27-next-20081017 #2
[   17.899905] Pid: 1791, comm: dhcpcd-run-hook Not tainted
2.6.27-next-20081017 #2
[ 3846.588549] Pid: 2005, comm: screen Not tainted 2.6.27-next-20081017 #2
[ 4416.242723] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2
[ 4430.618037] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2
[ 4431.641578] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2
[ 4432.944265] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2
[ 4590.330706] Pid: 2026, comm: git-merge Not tainted 2.6.27-next-20081017 #2
[14882.802479] Pid: 2058, comm: git-merge Not tainted 2.6.27-next-20081017 #2
[16955.026436] Pid: 2091, comm: git-merge Not tainted 2.6.27-next-20081017 #2
[18466.645935] Pid: 2119, comm: git-merge Not tainted 2.6.27-next-20081017 #2
[19165.813049] Pid: 2150, comm: git-merge Not tainted 2.6.27-next-20081017 #2

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