linux-kernel - Re: [PATCH] btrfs: convert data_seqcount to seqcount_mutex

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

Date:   Fri, 23 Oct 2020 18:56:26 +0200
From:   David Sterba <dsterba@...e.cz>
To:     Davidlohr Bueso <dave@...olabs.net>
Cc:     dsterba@...e.com, a.darwish@...utronix.de,
        linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
        Davidlohr Bueso <dbueso@...e.de>
Subject: Re: [PATCH] btrfs: convert data_seqcount to seqcount_mutex_t

On Wed, Oct 21, 2020 at 01:17:24PM -0700, Davidlohr Bueso wrote:
> By doing so we can associate the sequence counter to the chunk_mutex
> for lockdep purposes (compiled-out otherwise) and also avoid
> explicitly disabling preemption around the write region as it will now
> be done automatically by the seqcount machinery based on the lock type.

Thanks, the enhanced seqlock is new to me and makes sense regarding
lockdep. I've added a comment to mention the mutex association and added
it to misc-next.