xfs
[Top] [All Lists]

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

To: "Dave Chinner" <david@xxxxxxxxxxxxx>, lachlan@xxxxxxx, "Christoph Hellwig" <hch@xxxxxxxxxxxxx>, "Arjan van de Ven" <arjan@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-next@xxxxxxxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx>
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: Wed, 22 Oct 2008 12:21:23 +0400
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:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=eQV67Y7oPvbQYrGabOPUXm2DhltByG+0DUf1MUBM1SI=; b=r+cl6hRKSTtCGMGgCcou3WtYzN2J9kgHHwIipKtWybDEbVMFKfacnkrhmvCG5pV7vO s/1V1ZviHzFMg+Sp7SFaJnLhqHWphs6o5eqnCQ8sQwSyGVTBXRebVWF1Q4dYzRXXJSw5 vz+zcKZfHk0An6Qimf6ErYgyC95Pcugq4477I=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=CM2Yd4kE9BquZna6e3vzi/F66a3zgbeaR1J8WTTZG6gbQprRJeS5G1fTKyCfdg3oYn CdcngHVQL4aJnkhGFe+uqh8U+ffFgx/Mu5eFYFbd2h7wvQjKRcfwUfAlNpVAJ5iGi23O Hr0yIHf25pF2TDPkoLNljf1fkcx5KrkIKkwh8=
In-reply-to: <20081022075838.GK18495@disturbed>
References: <a4423d670810170954h7ca130aaw8895380a4c6b125@xxxxxxxxxxxxxx> <a4423d670810171013g5bc19c1cm3f7d9c014ee70349@xxxxxxxxxxxxxx> <20081017203710.GA27187@xxxxxxxxxxxxx> <20081017135510.7127c4e7@xxxxxxxxxxxxx> <a4423d670810200758m3cea3841h40988afc8eaf81@xxxxxxxxxxxxxx> <20081020163327.GA15651@xxxxxxxxxxxxx> <a4423d670810201013w6448cb38w402771799cefb5f5@xxxxxxxxxxxxxx> <20081020223549.GA21152@disturbed> <a4423d670810210442y51b62fc2naf6cb649e6b26942@xxxxxxxxxxxxxx> <20081022075838.GK18495@disturbed>
> Ah, OK, I see the problem, though I don't understand why I'm not
> seeing the might_sleep() triggering all the time given that I always
> build with:
>
> $ grep SLEEP .config
> CONFIG_DEBUG_SPINLOCK_SLEEP=y
>
> Basically the above commit moved xfs_ilock() inside
> radix_tree_preload()/radix_tree_preload_end(), which means we are
> taking a rwsem() while we have an elevated preempt count. I'll
> get a patch out to fix it.
Could it cause the I/O dead lock or should I continue trying to reproduce it?

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