From: Carlos Maiolino <cem@kernel.org>
To: Ravi Singh <ravising@redhat.com>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Dave Chinner <dgc@kernel.org>
Subject: Re: [PATCH] xfs: mark i_mode=0 and shut down on attr fork inactivation failure
Date: Tue, 03 Nov 2026 11:02:27 +0100 [thread overview]
Message-ID: <179370014741.413123.16126716252675791304.b4-ty@kernel.org> (raw)
In-Reply-To: <20261021063329.2853484-1-ravising@redhat.com>
On Wed, 21 Oct 2026 08:33:29 +0200, Ravi Singh wrote:
> xfs_attr_inactive() can fail on an I/O error reading the attribute
> fork's btree blocks, for example from fault injection such as the
> dm-flakey errors used by xfstests generic/475. On failure,
> xfs_ifork_zap_attr() zeros af_nextents without freeing the attribute
> blocks or decrementing i_nblocks, leaving the inode in an
> inconsistent in-memory state.
>
> [...]
Applied to for-next, thanks!
[1/1] xfs: mark i_mode=0 and shut down on attr fork inactivation failure
commit: bde0010631a207511308dc8407f34595dac13ad5
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2026-11-03 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 6:33 Ravi Singh
2026-10-27 15:44 ` 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=179370014741.413123.16126716252675791304.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=dgc@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ravising@redhat.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
all inboxes | Powered by JetHome®