From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Carlos Maiolino <cem@kernel.org>,
Nirjhar Roy <nirjhar.roy.lists@gmail.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/2] xfs: pass back updated nb from xfs_growfs_compute_deltas
Date: Tue, 2 Jun 2026 07:34:51 +0200 [thread overview]
Message-ID: <20260602053451.GA32429@lst.de> (raw)
In-Reply-To: <20260602043640.GM6078@frogsfrogsfrogs>
On Mon, Jun 01, 2026 at 09:36:40PM -0700, Darrick J. Wong wrote:
> On Mon, Jun 01, 2026 at 01:07:52PM +0200, Christoph Hellwig wrote:
> > xfs_growfs_compute_deltas can update nb for corner cases like a number
> > of blocks that would create a less the minimal sized AG, or running
> > past the max AG limit. Pass back the calculated value to the caller,
> > as it relies on that for a few things.
>
> A few things, like getting the fs size right after the grow?
Heh, yes. I gues I'll have to reword this a bit to not sound silly.
next prev parent reply other threads:[~2026-06-02 5:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 11:07 fix dblocks adjustment in growfs Christoph Hellwig
2026-06-01 11:07 ` [PATCH 1/2] xfs: pass back updated nb from xfs_growfs_compute_deltas Christoph Hellwig
2026-06-02 4:36 ` Darrick J. Wong
2026-06-02 5:34 ` Christoph Hellwig [this message]
2026-06-01 11:07 ` [PATCH 2/2] xfs: cleanup xfs_growfs_compute_deltas Christoph Hellwig
2026-06-02 4:42 ` Darrick J. Wong
2026-06-02 5:37 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2026-06-08 5:01 fix dblocks adjustment in growfs v2 Christoph Hellwig
2026-06-08 5:01 ` [PATCH 1/2] xfs: pass back updated nb from xfs_growfs_compute_deltas Christoph Hellwig
2026-06-09 7:52 fix dblocks adjustment in growfs v3 Christoph Hellwig
2026-06-09 7:52 ` [PATCH 1/2] xfs: pass back updated nb from xfs_growfs_compute_deltas 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=20260602053451.GA32429@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nirjhar.roy.lists@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 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.