linux-kernel - Re: next-20140114 - BUG: spinlock wrong CPU on CPU#3, mount/597

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <55555.1389889219@turing-police.cc.vt.edu>
Date:	Thu, 16 Jan 2014 11:20:19 -0500
From:	Valdis.Kletnieks@...edu
To:	Jan Kara <jack@...e.cz>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org
Subject: Re: next-20140114 - BUG: spinlock wrong CPU on CPU#3, mount/597

On Thu, 16 Jan 2014 11:39:34 +0100, Jan Kara said:

>   Hum, the complaint is for group->notification_waitq->lock which
> is an internal lock for the wait queue. Actually the corruption seems to be
> only a single bit flip - the whole spinlock structure looks correct, only
> owner_cpu got flipped from 0x3 to 0x23. Ah, do you have patch from Hugh:
>
> fanotify: fix corruption preventing startup
>
> The corruption would match that very well and Andrew queued it just
> recently...

Aha.  It landed after next-20140114 got put together.  WIll try -0116 (which
does have it) and if that doesn't fix it, I'll follow up...


Content of type "application/pgp-signature" skipped