linux-kernel - Re: [tip: locking/urgent] futex: Handle transient "ownerless" rtmutex state correctly

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: <87v9egkh91.fsf@nanos.tec.linutronix.de>
Date:   Sat, 07 Nov 2020 22:07:54 +0100
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Mike Galbraith <efault@....de>, linux-kernel@...r.kernel.org,
        linux-tip-commits@...r.kernel.org
Cc:     Gratian Crisan <gratian.crisan@...com>, stable@...r.kernel.org,
        x86 <x86@...nel.org>
Subject: Re: [tip: locking/urgent] futex: Handle transient "ownerless" rtmutex state correctly

On Sat, Nov 07 2020 at 18:05, Mike Galbraith wrote:
> On Fri, 2020-11-06 at 21:26 +0000, tip-bot2 for Mike Galbraith wrote:
>> +		if (unlikely(!newowner)) {
>> +			ret = -EAGAIN;
>                         ^^^
>
> My box just discovered an unnoticed typo.  That 'ret' should read 'err'
> so we goto retry, else fbomb_v2 proggy will trigger gripeage.

Bah. I noticed and wanted to fix it before committing and then
forgot. Fixed now.