linux-kernel - [PATCH -v5 00/14] the saga of FUTEX_UNLOCK

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

Message-Id: <20170304092717.762954142@infradead.org>
Date:   Sat, 04 Mar 2017 10:27:17 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     tglx@...utronix.de
Cc:     mingo@...nel.org, juri.lelli@....com, rostedt@...dmis.org,
        xlpang@...hat.com, bigeasy@...utronix.de,
        linux-kernel@...r.kernel.org, mathieu.desnoyers@...icios.com,
        jdesfossez@...icios.com, bristot@...hat.com, dvhart@...radead.org,
        peterz@...radead.org
Subject: [PATCH -v5 00/14] the saga of FUTEX_UNLOCK_PI wobbles continues

Hi all,

Here be the 5th iteration of these patches; which strive to unlock the rt_mutex
without holding hb->lock.

In total this patch-set is very much like the previous one (including the 'late'
fix) but it gets there in a slightly different -- and hopefully easier to
understand -- route.

The last 3 patches could be superfluous if we can proof that the -EAGAIN retry
in futex_unlock_pi() isn't a problem for bounded execution (or are willing to
accept it). In this case the patch-set ends up simpler than before.

I sincerely hope this is the last of it; but please consider carefully, there be
dragons here.