linux-kernel - Re: [PATCHv5] arm64/cpufeature: don't use mutex in bringup path

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]

Date:   Thu, 29 Jun 2017 15:10:59 +0100
From:   Mark Rutland <mark.rutland@....com>
To:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:     Catalin Marinas <catalin.marinas@....com>,
        linux-arm-kernel@...ts.infradead.org, suzuki.poulose@....com,
        marc.zyngier@....com, will.deacon@....com,
        linux-kernel@...r.kernel.org, peterz@...radead.org,
        tglx@...utronix.de, Christoffer Dall <christoffer.dall@...aro.org>
Subject: Re: [PATCHv5] arm64/cpufeature: don't use mutex in bringup path

Hi,

On Tue, Jun 27, 2017 at 02:05:55PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-05-17 17:05:31 [+0100], Catalin Marinas wrote:
> > > Catalin, can you take this as a fix for v4.12?
> > 
> > I queued it for 4.12-rc2. Thanks.
> 
> I backported a few patches into v4.11-RT and the backtrace popped up
> (which is fixed by this patch). The problem existed before it has been
> made visible. Do you intend to push this patch stable?

I wasn't planning to.

This was fairly invasive (so there'd be a number of conflicts to fix
up), and we weren't seeing issues in practice for !RT kernels.

If this is causing ap roblem in practice for !RT, I'd be happy to.

Thanks,
Mark.