All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: cem@kernel.org, stable@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: fix media verification ioctl for internal rt volumes
Date: Sun, 23 Aug 2026 22:31:29 -0700	[thread overview]
Message-ID: <20260824053129.GD6110@frogsfrogsfrogs> (raw)
In-Reply-To: <20260824045053.GA29508@lst.de>

On Mon, Aug 24, 2026 at 06:50:53AM +0200, Christoph Hellwig wrote:
> Looks good:
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> 
> I'm starting to wonder if operating on FSBs instead of BBs in the media
> verification ioctl would clean up much of this.  But I guess we care about
> being able to pinpoint media errors to sub-FSB ranges?

It would probably clean things up ... but OTOH all the other userspace
APIs use BBs and don't expose the segmented FSB/RTBs to userland.

Anyway thanks for reviewing :)

--D

      reply	other threads:[~2026-08-24  5:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  3:58 [PATCH] xfs: fix media verification ioctl for internal rt volumes Darrick J. Wong
2026-08-24  4:50 ` Christoph Hellwig
2026-08-24  5:31   ` Darrick J. Wong [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=20260824053129.GD6110@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.