linux-kernel - Re: [bisected] system hang after boot

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

Message-ID: <20171122191013.GF22648@arm.com>
Date:   Wed, 22 Nov 2017 19:10:14 +0000
From:   Will Deacon <will.deacon@....com>
To:     Sebastian Ott <sebott@...ux.vnet.ibm.com>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...nel.org>,
        Martin Schwidefsky <schwidefsky@...ibm.com>,
        Heiko Carstens <heiko.carstens@...ibm.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [bisected] system hang after boot

Hi Sebastian,

On Wed, Nov 22, 2017 at 07:54:54PM +0100, Sebastian Ott wrote:
> On Wed, 22 Nov 2017, Will Deacon wrote:
> > Now, I can't see what the break_lock is doing here other than causing
> > problems. Is there a good reason for it, or can you just try removing it
> > altogether? Patch below.
> 
> With your patch applied the system is able to boot again.
> I did some quick additional tests - seems to be working fine.

That was quick, thanks!

So the million dollar question is: does somebody care about the break_lock
field and, if so, why?

Will