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  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:   Tue, 4 Apr 2017 08:31:05 -0700
From:   Davidlohr Bueso <>
To:     Jan Kara <>
Cc:     Laurent Dufour <>,,,,,,,,
        Davidlohr Bueso <>
Subject: Re: [PATCH 1/5] locking: Introduce range reader/writer lock

On Mon, 03 Apr 2017, Jan Kara wrote:

>Or just a plain sequence counter of the lock operations?

So what I dislike about this is that we'd also have to enlarge
the struct range_rwlock_tree. otoh, I'm hesitant to depend on
the tick rate for lock correctness, so perhaps your suggestion
is best.


Powered by blists - more mailing lists