linux-kernel - Re: BUG: spinlock trylock failure on UP on CPU#0, vgchange/936

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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 22 Jan 2012 13:09:56 +0100
From:	Jens Axboe <axboe@...nel.dk>
To:	Christian Kujau <lists@...dbynature.de>
CC:	LKML <linux-kernel@...r.kernel.org>, peterz@...radead.org,
	dm-devel@...hat.com
Subject: Re: BUG: spinlock trylock failure on UP on CPU#0, vgchange/936

On 2012-01-22 11:36, Christian Kujau wrote:
> On Sun, 22 Jan 2012 at 11:30, Jens Axboe wrote:
>> What about with this on top?
> 
> Will try. A compile on this box takes almost two hours (PowerBook G4, 
> throttled to 70MHz), would it be enough to remove the block/*.o files and 
> continue from there?

Yes, just recompiling block/*.o is enough.

-- 
Jens Axboe

--
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/