linux-kernel - Re: Btrfs lockdep with 3.15 merge window v3.14-751-g683b6c6f82a6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 2 Apr 2014 15:43:45 -0400
From:	Chris Mason <clm@...com>
To:	<dsterba@...e.cz>, Josh Boyer <jwboyer@...oraproject.org>,
	<jbacik@...com>, linux-btrfs <linux-btrfs@...r.kernel.org>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: Btrfs lockdep with 3.15 merge window v3.14-751-g683b6c6f82a6

On 04/02/2014 12:47 PM, David Sterba wrote:
> On Tue, Apr 01, 2014 at 06:23:11PM -0400, Josh Boyer wrote:
>> Below is a lockdep spew I have on a local VM running Linus' tree as of
>> this afternoon.  The specific git commit is v3.14-751-g683b6c6f82a6.
>
>> [  295.349016]        CPU0                    CPU1
>> [  295.349016]        ----                    ----
>> [  295.349016]   lock(&found->groups_sem);
>> [  295.349016]                                local_irq_disable();
>> [  295.349016]                                lock(&delayed_node->mutex);
>> [  295.349016]                                lock(&found->groups_sem);
>> [  295.349016]   <Interrupt>
>> [  295.349016]     lock(&delayed_node->mutex);
>
> Fixed by https://urldefense.proofpoint.com/v1/url?u=https://patchwork.kernel.org/patch/3894781/&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2FL0lzzDhu0Y1hL9xm%2BQyA%3D%3D%0A&m=R1vuFCUzlD4QksU2UH3APFiFgMVkwmMci%2Bktv%2BzqQnE%3D%0A&s=adbe2bfbb243d9781307cfff001f30c01afd35a32e0fb976ecca933ef4cebd26
>

I've got this lined up for my next pull as well.  I sent early this 
time, but more is going in.

-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/