Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 23 Oct 2020 18:56:26 +0200
From:   David Sterba <dsterba@suse.cz>
To:     Davidlohr Bueso <dave@stgolabs.net>
Cc:     dsterba@suse.com, a.darwish@linutronix.de,
        linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
        Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH] btrfs: convert data_seqcount to seqcount_mutex_t
Message-ID: <20201023165626.GK6756@twin.jikos.cz>
Reply-To: dsterba@suse.cz
Mail-Followup-To: dsterba@suse.cz, Davidlohr Bueso <dave@stgolabs.net>,
        dsterba@suse.com, a.darwish@linutronix.de,
        linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
        Davidlohr Bueso <dbueso@suse.de>
References: <20201021201724.27213-1-dave@stgolabs.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20201021201724.27213-1-dave@stgolabs.net>
User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12)
Precedence: bulk

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.