From: Carlos Maiolino <cem@kernel.org>
To: Javier Tia <javier@peridio.com>
Cc: "Darrick J . Wong" <djwong@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
Allison Henderson <achender@kernel.org>,
Andrey Albershteyn <aalbersh@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] xfs: fix filesystem shutdown from parent pointer reservation underflow
Date: Thu, 03 Sep 2026 08:06:03 +0200 [thread overview]
Message-ID: <178841556375.1198521.1018671012811358518.b4-ty@kernel.org> (raw)
In-Reply-To: <20260810230611.2859909-8-floss@jetm.me>
On Mon, 10 Aug 2026 17:06:12 -0600, Javier Tia wrote:
> The first parent pointer update that has to grow the attribute fork
> twice in one operation can shut the filesystem down with
>
> XFS (loop0): Corruption of in-memory data (0x8) detected at
> xfs_defer_finish_noroll+0x29a/0x4b0 (fs/xfs/libxfs/xfs_defer.c:721)
>
> The message names in-core corruption, but nothing is corrupt. The
> deferred work that failed is a block allocation that returned a bare
> -ENOSPC on a filesystem with hundreds of gigabytes free, and
> xfs_defer_finish_noroll() treats any non-EAGAIN error as fatal.
>
> [...]
Applied to for-next, thanks!
[1/6] xfs: initialise error in xfs_defer_finish_one()
commit: 08e6a7587c0a89a342f9ebe4b70160b23db9a138
[2/6] xfs: give the deferred barrier op type a name
commit: 6c81238928c19fb83d469ec8aca6b90830b7aad0
[3/6] xfs: report the error that made deferred work shut down the fs
commit: 17783da399db9f363a64a983b37117e736d3aa98
[4/6] xfs: correct the parent pointer space reservation comment
commit: 410822bd69ef47a231c4239712c2ffe1fab7c68f
[5/6] xfs: initialise args->total for parent pointer updates
commit: 47531ec00c81e4b41705c9859ac26c7522efffda
[6/6] xfs: assert the reservation covers each da fork growth
commit: 21a0382da84fc9fc94af0b2b0a868a73c3836f2c
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2026-09-03 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 23:06 Javier Tia
2026-08-10 23:06 ` [PATCH v3 1/6] xfs: initialise error in xfs_defer_finish_one() Javier Tia
2026-08-10 23:06 ` [PATCH v3 2/6] xfs: give the deferred barrier op type a name Javier Tia
2026-08-10 23:06 ` [PATCH v3 3/6] xfs: report the error that made deferred work shut down the fs Javier Tia
2026-08-11 16:27 ` Darrick J. Wong
2026-08-10 23:06 ` [PATCH v3 4/6] xfs: correct the parent pointer space reservation comment Javier Tia
2026-08-10 23:06 ` [PATCH v3 5/6] xfs: initialise args->total for parent pointer updates Javier Tia
2026-08-10 23:06 ` [PATCH v3 6/6] xfs: assert the reservation covers each da fork growth Javier Tia
2026-09-03 6:06 ` 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=178841556375.1198521.1018671012811358518.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=aalbersh@kernel.org \
--cc=achender@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=javier@peridio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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®