linux-kernel - Re: [PATCH 0/5] locking: Percpu-rwsem rewrite

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: <20191115171450.GJ19129@localhost.localdomain>
Date:   Fri, 15 Nov 2019 18:14:50 +0100
From:   Juri Lelli <juri.lelli@...hat.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     mingo@...nel.org, will@...nel.org, oleg@...hat.com,
        tglx@...utronix.de, linux-kernel@...r.kernel.org,
        bigeasy@...utronix.de, williams@...hat.com, bristot@...hat.com,
        longman@...hat.com, dave@...olabs.net, jack@...e.com
Subject: Re: [PATCH 0/5] locking: Percpu-rwsem rewrite

Hi,

On 13/11/19 11:21, Peter Zijlstra wrote:
> Yet another version of the percpu-rwsem rewrite..
> 
> This one (ab)uses the waitqueue in an entirely different and unique way, but no
> longer shares it like it did. It retains the use of rcuwait for the
> writer-waiting-for-readers-to-complete condition.
> 
> This one should be FIFO fair with writer-stealing.
> 
> It seems to pass locktorture torture_type=percpu_rwsem_lock. But as always,
> this stuff is tricky, please look carefully.

Backported this series to v5.2.21-rt13.

locktorture looks good (running for several hours) and DEBUG_LOCKS splat
[1] not reproducible anymore.

Tested-by: Juri Lelli <juri.lelli@...hat.com>

Thanks!

Juri

1 - https://lore.kernel.org/lkml/20190326093421.GA29508@localhost.localdomain/