From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v6.1 11/11] xfs: add media verification ioctl
Date: Wed, 21 Jan 2026 11:58:05 -0800 [thread overview]
Message-ID: <20260121195805.GK5945@frogsfrogsfrogs> (raw)
In-Reply-To: <20260121070556.GA11882@lst.de>
On Wed, Jan 21, 2026 at 08:05:56AM +0100, Christoph Hellwig wrote:
> On Tue, Jan 20, 2026 at 10:00:40AM -0800, Darrick J. Wong wrote:
> > On Tue, Jan 20, 2026 at 08:18:30AM +0100, Christoph Hellwig wrote:
> > >
> > > > + unsigned int bio_bbcount;
> > > > + blk_status_t bio_status;
> > > > +
> > > > + bio_reset(bio, btp->bt_bdev, REQ_OP_READ);
> > > > + bio->bi_iter.bi_sector = daddr;
> > > > + bio_add_folio_nofail(bio, folio,
> > > > + min(bbcount << SECTOR_SHIFT, folio_size(folio)),
> > > > + 0);
> > >
> > > You could actually use bio_reuse as you implied in the previous mail here
> > > and save the bio_add_folio_nofail call. Not really going to make much
> > > of a difference, so:
> >
> > Hrm. Is that bio_reuse patch queued for upstream? Though maybe it'd be
> > easier to make a mental note (ha!) to clean this up once both appear
> > upstream.
>
> It is queued up in the xfs for-next tree.
Ah, heh. I'll see if cem merges the series atop his xfs-7.0-merge
branch and send a followup. As it is I'm already going to ask Linus if
I can remove the old fsnotify error function (and any new callers that
might pop up) right before -rc1.
--D
next prev parent reply other threads:[~2026-01-21 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <176852588473.2137143.1604994842772101197.stgit@frogsfrogsfrogs>
[not found] ` <176852588776.2137143.7103003682733018282.stgit@frogsfrogsfrogs>
[not found] ` <20260120041226.GJ15551@frogsfrogsfrogs>
[not found] ` <20260120071830.GA5686@lst.de>
[not found] ` <20260120180040.GU15551@frogsfrogsfrogs>
2026-01-21 7:05 ` [PATCH v6.1 11/11] xfs: add media verification ioctl Christoph Hellwig
2026-01-21 19:58 ` Darrick J. Wong [this message]
2026-02-06 3:01 ` Chris Mason
2026-02-06 4:53 ` Darrick J. Wong
[not found] ` <176852588582.2137143.1283636639551788931.stgit@frogsfrogsfrogs>
2026-02-06 13:07 ` [PATCH 02/11] xfs: start creating infrastructure for health monitoring Pankaj Raghav (Samsung)
2026-02-06 17:47 ` Darrick J. Wong
2026-02-06 18:54 ` Pankaj Raghav
2026-02-06 20:41 ` Darrick J. Wong
2026-02-09 6:34 ` Christoph Hellwig
2026-02-10 4:57 ` Darrick J. Wong
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=20260121195805.GK5945@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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