[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250120-tragbar-ertrinken-24f2bbc2beb4@brauner>
Date: Mon, 20 Jan 2025 16:25:19 +0100
From: Christian Brauner <brauner@...nel.org>
To: Andreas Gruenbacher <agruenba@...hat.com>
Cc: Christoph Hellwig <hch@....de>,
Andrew Morton <akpm@...ux-foundation.org>, Al Viro <viro@...iv.linux.org.uk>, Gao Xiang <xiang@...nel.org>,
Chao Yu <chao@...nel.org>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-erofs@...ts.ozlabs.org, gfs2@...ts.linux.dev
Subject: Re: [PATCH 8/8] gfs2: use lockref_init for qd_lockref
On Fri, Jan 17, 2025 at 05:03:51PM +0100, Andreas Gruenbacher wrote:
> On Thu, 16 Jan 2025 05:32:26 +0100, Christoph Hellwig <hch@....de> wrote:
> > Well, if you can fix it to start with 1 we could start out with 1
> > as the default. FYI, I also didn't touch the other gfs2 lockref
> > because it initialize the lock in the slab init_once callback and
> > the count on every initialization.
>
> Sure, can you add the below patch before the lockref_init conversion?
>
> Thanks,
> Andreas
>
> --
>
> gfs2: Prepare for converting to lockref_init
>
> First, move initializing the glock lockref spin lock from
> gfs2_init_glock_once() to gfs2_glock_get().
>
> Second, in qd_alloc(), initialize the lockref count to 1 to cover the
> common case. Compensate for that in gfs2_quota_init() by adjusting the
> count back down to 0; this case occurs only when mounting the filesystem
> rw.
>
> Signed-off-by: Andreas Gruenbacher <agruenba@...hat.com>
> ---
Can you send this as a proper separae patch, please?
Powered by blists - more mailing lists