From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org, Daejun Park <daejun7.park@samsung.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Dave Chinner <dgc@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] xfs: discard every free extent in a whole-AG FITRIM
Date: Tue, 03 Nov 2026 11:02:30 +0100 [thread overview]
Message-ID: <179370015013.413123.5201894669879295169.b4-ty@kernel.org> (raw)
In-Reply-To: <20261026-xfs-fitrim-skip-v1-0-cddd8414f99c@samsung.com>
On Mon, 26 Oct 2026 10:54:04 +0900, Daejun Park wrote:
> A whole-device fstrim walks each AG but the last by length. Two bugs
> in that walk leave free extents undiscarded, while fstrim reports the
> whole range as trimmed. Patch 2 depends on patch 1.
>
> The new fstests case xfs/842, sent separately, fails without this
> series and passes with it. ./check -g trim shows no regressions
> (generic/038 and 500 were not run).
>
> [...]
Applied to for-next, thanks!
[1/2] xfs: don't skip free extents in later batches of a whole-AG FITRIM
commit: 595e67d7261673d03c96950ffbb2e545c00376ed
[2/2] xfs: don't skip free extents of the longest length in a whole-AG FITRIM
commit: 5745f4f10a1a16aa5bb020acc38afa33f2d5ff99
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2026-11-03 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 1:54 Daejun Park via B4 Relay
2026-10-26 1:54 ` [PATCH 1/2] xfs: don't skip free extents in later batches of " Daejun Park via B4 Relay
2026-10-28 15:03 ` Christoph Hellwig
2026-10-26 1:54 ` [PATCH 2/2] xfs: don't skip free extents of the longest length in " Daejun Park via B4 Relay
2026-10-28 15:04 ` Christoph Hellwig
2026-11-03 10:02 ` Carlos Maiolino [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=179370015013.413123.5201894669879295169.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=dgc@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®