public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Wilfred Mallawa <wilfred.opensource@gmail.com>
To: "Darrick J . Wong" <djwong@kernel.org>, Christoph Hellwig <hch@lst.de>
Cc: Alistair Francis <alistair.francis@wdc.com>,
	Damien Le'Moal <dlemoal@kernel.org>,
	linux-xfs@vger.kernel.org,
	Wilfred Mallawa <wilfred.mallawa@wdc.com>
Subject: [PATCH 3/3] xfs_io: report rg_writepointer in report rg_info()
Date: Fri, 13 Mar 2026 10:24:56 +1000	[thread overview]
Message-ID: <20260313002456.3823811-3-wilfred.opensource@gmail.com> (raw)
In-Reply-To: <20260313002456.3823811-1-wilfred.opensource@gmail.com>

From: Wilfred Mallawa <wilfred.mallawa@wdc.com>

If the XFS_RTGROUP_GEOM_WRITEPOINTER field is set, then print the
writepointer in struct xfs_rtgroup_geometry.

Signed-off-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
---
 io/aginfo.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/io/aginfo.c b/io/aginfo.c
index f81986f0d..978f0f3b8 100644
--- a/io/aginfo.c
+++ b/io/aginfo.c
@@ -132,6 +132,9 @@ report_rginfo(
 	printf(_("Checked: 0x%x\n"),	rgeo.rg_checked);
 	printf(_("Flags: 0x%x\n"),	rgeo.rg_flags);
 
+	if (rgeo.rg_flags & XFS_RTGROUP_GEOM_WRITEPOINTER)
+		printf(_("Writepointer: 0x%u\n"), rgeo.rg_writepointer);
+
 	return 0;
 }
 
-- 
2.53.0


  parent reply	other threads:[~2026-03-13  0:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13  0:24 [PATCH 1/3] xfs: add write pointer to xfs_rtgroup_geometry Wilfred Mallawa
2026-03-13  0:24 ` [PATCH 2/3] man/xfs_rtgroup_geometry: add rg_writepointer field description Wilfred Mallawa
2026-03-13  3:27   ` Darrick J. Wong
2026-03-16  9:04   ` Christoph Hellwig
2026-03-13  0:24 ` Wilfred Mallawa [this message]
2026-03-13  3:28   ` [PATCH 3/3] xfs_io: report rg_writepointer in report rg_info() Darrick J. Wong
2026-03-16  9:04   ` 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=20260313002456.3823811-3-wilfred.opensource@gmail.com \
    --to=wilfred.opensource@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=djwong@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=wilfred.mallawa@wdc.com \
    /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