From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 6/6] xfs: adjust datadev sector count to reflect internal rt volumes
Date: Tue, 18 Aug 2026 23:36:03 -0700 [thread overview]
Message-ID: <aoVO0_jWpSlZZ1Xy@infradead.org> (raw)
In-Reply-To: <aoVOIZqmmAI7FYlm@infradead.org>
On Tue, Aug 18, 2026 at 11:33:05PM -0700, Christoph Hellwig wrote:
> I still think messing with the kernel buftarg nr_sectors is wrong for
> this. The kernel view of the buftarg should be correct and just include
> the part of the device that matters. So I think the right fix in the
> kernel is changing xfs_verify_media to add the internal RT device offset
> before sending the bios. We might need additional userland fixes,
> but from a quick look I think it should be fine (famous last words)
Btw: happy to look into this myself. Just waiting if you have a
reproducer before I go off an create my own.
next prev parent reply other threads:[~2026-08-19 6:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 5:23 [PATCHSET v2 1/2] xfs: LLM-inspired bug fixes, part 5 Darrick J. Wong
2026-08-13 5:24 ` [PATCH 1/6] xfs: fix unit conversions in per_binval computation Darrick J. Wong
2026-08-13 5:24 ` [PATCH 2/6] xfs: fix short ifork reaping computation in xreap_bmapi_binval Darrick J. Wong
2026-08-13 5:24 ` [PATCH 3/6] xfs: fix name string recording in slowpath pptr tracepoints Darrick J. Wong
2026-08-13 5:24 ` [PATCH 4/6] xfs: don't leak dqacct if rhashtable insertion fails Darrick J. Wong
2026-08-13 5:25 ` [PATCH 5/6] xfs: fix the rtrmap and rtrefcount _maxlevels_ondisk functions Darrick J. Wong
2026-08-13 5:25 ` [PATCH 6/6] xfs: adjust datadev sector count to reflect internal rt volumes Darrick J. Wong
2026-08-19 6:33 ` Christoph Hellwig
2026-08-19 6:36 ` Christoph Hellwig [this message]
2026-08-19 23:08 ` Darrick J. Wong
2026-08-24 4:47 ` Christoph Hellwig
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=aoVO0_jWpSlZZ1Xy@infradead.org \
--to=hch@infradead.org \
--cc=cem@kernel.org \
--cc=djwong@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