gfs2 filesystem and dlm development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Christian Brauner <brauner@kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	linux-fsdevel@vger.kernel.org,
	Andreas Gruenbacher <agruenba@redhat.com>,
	gfs2@lists.linux.dev
Subject: Re: [PATCH v2 33/34] buffer: Change calling convention for end_buffer_read_sync()
Date: Sat, 30 May 2026 17:15:18 +0100	[thread overview]
Message-ID: <ahsNFkp_9q8PhLFc@casper.infradead.org> (raw)
In-Reply-To: <2lbdmkqnz62wulcq576mvhjwiirgky6vpyvpjwxkpm275qf7a4@zlkck3bcyqby>

On Sat, May 30, 2026 at 02:07:40PM +0200, Jan Kara wrote:
> On Thu 28-05-26 18:31:46, Matthew Wilcox (Oracle) wrote:
> > Unify end_buffer_read_sync() and __end_buffer_read_notouch()
> > by requiring the caller put the refcount on the buffer.  The only caller
> > is in the gfs2_meta_read() path, and there we can put the refcount
> > after locking the buffer.
> > 
> > Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> 
> It seems a bit sad to keep end_buffer_read_sync() alive only for gfs2
> metadata reading path but let's leave that for another time. Feel free to
> add:
> 
> Reviewed-by: Jan Kara <jack@suse.cz>

Thanks!  I agree that we've got two entry points (end_buffer_read_sync()
and bh_end_async_write()) each with one caller, and I'd be happier if
we could make both of them go away.

I keep reminding myself that we'd be better off converting gfs2 to iomap
than improving buffer.c to fit gfs2's needs.

As far as I can tell (... and I am so not an expert in gfs2), the main
thing we'd need to add to iomap to handle gfs2_meta_aops is the ability to
set REQ_META | REQ_PRIO.  Maybe that's an AS_METADATA flag on the mapping?

But maybe there's code elsewhere in gfs2 that depends on there being
buffer heads for the metadata address_space folios?

      parent reply	other threads:[~2026-05-30 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260528173150.1093780-1-willy@infradead.org>
2026-05-28 17:31 ` [PATCH v2 22/34] gfs2: Convert gfs2_metapath_ra to bh_submit() Matthew Wilcox (Oracle)
2026-05-30 11:47   ` Jan Kara
2026-05-28 17:31 ` [PATCH v2 23/34] gfs2: Convert gfs2_dir_readahead " Matthew Wilcox (Oracle)
2026-05-30 11:49   ` Jan Kara
2026-05-28 17:31 ` [PATCH v2 24/34] gfs2: Remove use of b_end_io in gfs2_meta_read_endio() Matthew Wilcox (Oracle)
2026-05-30 12:09   ` Jan Kara
2026-05-28 17:31 ` [PATCH v2 25/34] gfs2: Convert gfs2_aspace_write_folio to bh_submit() Matthew Wilcox (Oracle)
2026-05-30 11:54   ` Jan Kara
     [not found] ` <20260528173150.1093780-34-willy@infradead.org>
     [not found]   ` <2lbdmkqnz62wulcq576mvhjwiirgky6vpyvpjwxkpm275qf7a4@zlkck3bcyqby>
2026-05-30 16:15     ` Matthew Wilcox [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ahsNFkp_9q8PhLFc@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=agruenba@redhat.com \
    --cc=brauner@kernel.org \
    --cc=gfs2@lists.linux.dev \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox