From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@redhat.com>
Cc: xfs <linux-xfs@vger.kernel.org>,
hch@infradead.org, ravising@redhat.com, leo.lilong@huawei.com
Subject: [PATCH v2] xfs_repair: don't fail on INCOMPLETE attrs in leaf blocks
Date: Tue, 17 Mar 2026 13:50:18 -0700 [thread overview]
Message-ID: <20260317205018.GJ1770774@frogsfrogsfrogs> (raw)
In-Reply-To: <20260316225033.GP6069@frogsfrogsfrogs>
From: Darrick J. Wong <djwong@kernel.org>
While trying to fix problems in generic/753, I noticed test failures on
account of xfs_repair:
attribute entry #4 in attr block 0, inode 131 is INCOMPLETE
problem with attribute contents in inode 131
would clear attr fork
bad nblocks 4 for inode 131, would reset to 0
bad anextents 1 for inode 131, would reset to 0
Looking at the dumped filesystem, inode 131 is a linked file, and the
"incomplete" xattr was clearly part of an xfs_attr_set operation that
failed midway through because the induced log shutdown prevented xfs
from finishing the creation of a remote xattr. This kind of thing is
expected, but instead xfs_repair deletes the entire attr fork!
It's far too drastic to delete every xattr because doing that destroys
things like security labels. The kernel won't show incomplete attrs so
it's not a big deal to leave them attached to the file. Note that
xfs_scrub can fix such things.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
v2: improve commit message to explain how we got to this acceptable
place
---
repair/attr_repair.c | 22 +++++++++++++++++-----
1 file changed, 17 insertions(+), 5 deletions(-)
diff --git a/repair/attr_repair.c b/repair/attr_repair.c
index 50159b9a533875..fe4089026cae74 100644
--- a/repair/attr_repair.c
+++ b/repair/attr_repair.c
@@ -571,7 +571,13 @@ process_leaf_attr_remote(
!libxfs_attr_namecheck(entry->flags, remotep->name,
remotep->namelen) ||
be32_to_cpu(entry->hashval) != computed ||
- be32_to_cpu(entry->hashval) < last_hashval ||
+ be32_to_cpu(entry->hashval) < last_hashval) {
+ do_warn(
+ _("inconsistent remote attribute entry %d in attr block %u, ino %" PRIu64 "\n"), i, da_bno, ino);
+ return -1;
+ }
+
+ if (!(entry->flags & XFS_ATTR_INCOMPLETE) &&
be32_to_cpu(remotep->valueblk) == 0) {
do_warn(
_("inconsistent remote attribute entry %d in attr block %u, ino %" PRIu64 "\n"), i, da_bno, ino);
@@ -592,6 +598,9 @@ process_leaf_attr_remote(
return -1;
}
+ if (entry->flags & XFS_ATTR_INCOMPLETE)
+ goto out;
+
value = malloc(be32_to_cpu(remotep->valuelen));
if (value == NULL) {
do_warn(
@@ -708,12 +717,15 @@ process_leaf_attr_block(
}
if (entry->flags & XFS_ATTR_INCOMPLETE) {
- /* we are inconsistent state. get rid of us */
- do_warn(
+ /*
+ * Warn about incomplete xattrs but don't zap the
+ * entire attr fork because that causes loss of
+ * security labels. The kernel can handle stray
+ * incomplete attr entries.
+ */
+ do_log(
_("attribute entry #%d in attr block %u, inode %" PRIu64 " is INCOMPLETE\n"),
i, da_bno, ino);
- clearit = 1;
- break;
}
/* mark the entry used */
next prev parent reply other threads:[~2026-03-17 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 22:50 [PATCH] xfs_repair: don't fail on INCOMPLETE attrs in leaf blocks Darrick J. Wong
2026-03-17 9:14 ` Christoph Hellwig
2026-03-17 20:15 ` Darrick J. Wong
2026-03-17 20:50 ` Darrick J. Wong [this message]
2026-03-18 5:56 ` [PATCH v2] " 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=20260317205018.GJ1770774@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@redhat.com \
--cc=hch@infradead.org \
--cc=leo.lilong@huawei.com \
--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 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.