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]
Date:   Fri, 12 Apr 2019 20:21:19 +0200
From:   Peter Zijlstra <>
To:     Waiman Long <>
Cc:     Ingo Molnar <>, Ingo Molnar <>,
        Will Deacon <>,
        Thomas Gleixner <>,,,
        Davidlohr Bueso <>,
        Linus Torvalds <>,
        Tim Chen <>,
        huang ying <>
Subject: Re: [PATCH-tip v3 02/14] locking/rwsem: Make owner available even if

On Fri, Apr 12, 2019 at 10:22:20AM -0400, Waiman Long wrote:
> Oh, I see that the WIP.locking/core is currently merged into master. I
> would say rwsem part1 patchset and patch 1 of part2 are stable. So I
> would suggest merging those into the the master will be good. The rests
> are still under review until I get an OK from Peter. If they miss the
> next merge window and have to postpone to 5.3, I am fine with that.

What I do is revert that branch so I can prod at your patches myself.

But yes, I have part1 queued. It is part2 that I am still staring at,
although today got eaten by other 'fun'.

Powered by blists - more mailing lists