linux-kernel - Re: BUG: spinlock lockup

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]

Message-ID: <20140121101407.GD30706@mudshark.cambridge.arm.com>
Date:	Tue, 21 Jan 2014 10:14:07 +0000
From:	Will Deacon <will.deacon@....com>
To:	naveen yadav <yad.naveen@...il.com>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	Catalin Marinas <Catalin.Marinas@....com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: BUG: spinlock lockup

On Tue, Jan 21, 2014 at 06:37:31AM +0000, naveen yadav wrote:
> Thanks for your reply,
> 
> We are using Cortex A15.
> yes,  this is with ticket lock.
> 
> We will check value of arch_spinlock_t and share it. It is bit
> difficult to reproduce this scenario.
> 
> If you have some idea ,please suggest how to reproduce it.

You could try enabling lockdep and see if it catches anything earlier
on.

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