public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: Carlos Maiolino <cem@kernel.org>
Cc: linux-xfs@vger.kernel.org, ritesh.list@gmail.com,
	ojaswin@linux.ibm.com, djwong@kernel.org
Subject: Re: [PATCH v3] xfs: Fix the return value of xfs_rtcopy_summary()
Date: Mon, 12 Jan 2026 11:43:53 +0530	[thread overview]
Message-ID: <d9cc2f24-6c06-41ab-835e-453a4856fd0b@gmail.com> (raw)
In-Reply-To: <aUONoL924Sw_su9J@infradead.org>


On 12/18/25 10:44, Christoph Hellwig wrote:
> On Wed, Dec 17, 2025 at 10:04:32PM +0530, Nirjhar Roy (IBM) wrote:
>> xfs_rtcopy_summary() should return the appropriate error code
>> instead of always returning 0. The caller of this function which is
>> xfs_growfs_rt_bmblock() is already handling the error.
>>
>> Fixes: e94b53ff699c ("xfs: cache last bitmap block in realtime allocator")
>> Signed-off-by: Nirjhar Roy (IBM) <nirjhar.roy.lists@gmail.com>
>> Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
>> Cc: <stable@vger.kernel.org> # v6.7
> Looks good:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>

Hi Carlos,

Are this and [1] getting picked up?

[1] https://lore.kernel.org/all/aTFWJrOYXEeFX1kY@infradead.org/

--NR

>
-- 
Nirjhar Roy
Linux Kernel Developer
IBM, Bangalore


  reply	other threads:[~2026-01-12  6:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 16:34 [PATCH v3] xfs: Fix the return value of xfs_rtcopy_summary() Nirjhar Roy (IBM)
2025-12-18  5:14 ` Christoph Hellwig
2026-01-12  6:13   ` Nirjhar Roy (IBM) [this message]
2026-01-12  8:10     ` Carlos Maiolino
2026-01-12  8:40       ` Nirjhar Roy (IBM)
2026-01-12  9:56         ` Carlos Maiolino
2026-01-12 10:08           ` Nirjhar Roy (IBM)

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=d9cc2f24-6c06-41ab-835e-453a4856fd0b@gmail.com \
    --to=nirjhar.roy.lists@gmail.com \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.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