public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org, ritesh.list@gmail.com,
	ojaswin@linux.ibm.com, djwong@kernel.org
Subject: Re: [PATCH v1] xfs: Fix xfs_grow_last_rtg()
Date: Wed, 17 Dec 2025 22:18:17 +0530	[thread overview]
Message-ID: <a9f5da12-6b0d-434f-87e5-8bd4f163c245@gmail.com> (raw)
In-Reply-To: <aTFWJrOYXEeFX1kY@infradead.org>


On 12/4/25 15:06, Christoph Hellwig wrote:
> On Wed, Dec 03, 2025 at 06:15:45PM +0530, Nirjhar Roy (IBM) wrote:
>> The last rtg should be able to grow when the size of the
>> last is less than (and not equal to) sb_rgextents.
>> xfs_growfs with realtime groups fails without this
>> patch. The reason is that, xfs_growfs_rtg() tries
>> to grow the last rt group even when the last rt group
>> is at its maximal size i.e, sb_rgextents. It fails with
>> the following messages:
> Please use up all 73 characters of the commit log to improve
> readability.
>
> The change looks good:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>

Should I have any fixes tag for this fix? I have made the change on top 
of the very first version of the function (xfs_grow_last_rtg()), so 
should I put
Fixes: ee321351487ae ("xfs: grow the realtime section when realtime 
groups are enabled") ?

Also, which Cc tag should I put here?

--NR

>
> Can you submit a test case for this to xfstests?
>
-- 
Nirjhar Roy
Linux Kernel Developer
IBM, Bangalore


      parent reply	other threads:[~2025-12-17 16:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 12:45 [PATCH v1] xfs: Fix xfs_grow_last_rtg() Nirjhar Roy (IBM)
2025-12-04  9:36 ` Christoph Hellwig
2025-12-04  9:47   ` Nirjhar Roy (IBM)
2025-12-17 16:48   ` Nirjhar Roy (IBM) [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=a9f5da12-6b0d-434f-87e5-8bd4f163c245@gmail.com \
    --to=nirjhar.roy.lists@gmail.com \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.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