From: Weiming Shi <bestswngs@gmail.com>
To: linux-xfs@vger.kernel.org
Cc: Carlos Maiolino <cem@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Brian Foster <bfoster@redhat.com>, Xiang Mei <xmei5@asu.edu>,
Weiming Shi <bestswngs@gmail.com>
Subject: [PATCH] xfs: fail recovery on a committed log item with no regions
Date: Mon, 29 Jun 2026 09:24:53 -0700 [thread overview]
Message-ID: <20260629162452.2566242-2-bestswngs@gmail.com> (raw)
xlog_recover_add_to_trans() turns the first op of a transaction into a
recovery item. If that op is a bare transaction header
(len == sizeof(struct xfs_trans_header)), xlog_recover_add_item() adds
an item but attaches no region, so it sits on r_itemq with ri_cnt == 0
and ri_buf == NULL.
When the following op is a commit, xlog_recover_reorder_trans() runs
ITEM_TYPE() on each item to look up its ops vector. ITEM_TYPE() reads
*(unsigned short *)item->ri_buf[0].iov_base, which faults on the
NULL ri_buf. The commit handlers dereference ri_buf[0] too, so reorder
is the first place that trips over it.
This is reachable at mount time from a crafted image whose log holds the
op sequence START_TRANS / bare-header / COMMIT_TRANS:
Oops: general protection fault, probably for non-canonical address
0xdffffc0000000000
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
RIP: 0010:xlog_recover_reorder_trans (fs/xfs/xfs_log_recover.c:1836)
Call Trace:
xlog_recover_reorder_trans (fs/xfs/xfs_log_recover.c:1836)
xlog_recover_commit_trans (fs/xfs/xfs_log_recover.c:2043)
xlog_recovery_process_trans (fs/xfs/xfs_log_recover.c:2308)
xlog_recover_process_ophdr (fs/xfs/xfs_log_recover.c:2454)
xlog_recover_process_data (fs/xfs/xfs_log_recover.c:2501)
xlog_do_recovery_pass (fs/xfs/xfs_log_recover.c:3244)
xlog_recover (fs/xfs/xfs_log_recover.c:3493)
xfs_log_mount (fs/xfs/xfs_log.c:618)
xfs_mountfs (fs/xfs/xfs_mount.c:1034)
xfs_fs_fill_super (fs/xfs/xfs_super.c:1938)
get_tree_bdev_flags (fs/super.c:1635)
vfs_get_tree (fs/super.c:1695)
path_mount (fs/namespace.c:4161)
__x64_sys_mount (fs/namespace.c:4367)
xfs_log_recover.c:1836 is the ITEM_TYPE() dereference inside
xlog_find_item_ops().
A committed item always has at least its format descriptor in ri_buf[0],
so an item with no regions means the log is corrupt. Reject it with
-EFSCORRUPTED, like the unrecognised item type just below.
Fixes: 89cebc847729 ("xfs: validate transaction header length on log recovery")
Reported-by: Xiang Mei <xmei5@asu.edu>
Assisted-by: Claude:claude-opus-4-8
Signed-off-by: Weiming Shi <bestswngs@gmail.com>
---
fs/xfs/xfs_log_recover.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
index 09e6678ca487..ccff436612ee 100644
--- a/fs/xfs/xfs_log_recover.c
+++ b/fs/xfs/xfs_log_recover.c
@@ -1906,6 +1906,18 @@ xlog_recover_reorder_trans(
list_for_each_entry_safe(item, n, &sort_list, ri_list) {
enum xlog_recover_reorder fate = XLOG_REORDER_ITEM_LIST;
+ /* corrupt log: an item with no regions has a NULL ri_buf */
+ if (!item->ri_cnt || !item->ri_buf) {
+ xfs_warn(log->l_mp,
+ "%s: committed log item has no regions",
+ __func__);
+ ASSERT(0);
+ if (!list_empty(&sort_list))
+ list_splice_init(&sort_list, &trans->r_itemq);
+ error = -EFSCORRUPTED;
+ break;
+ }
+
item->ri_ops = xlog_find_item_ops(item);
if (!item->ri_ops) {
xfs_warn(log->l_mp,
--
2.43.0
next reply other threads:[~2026-06-29 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 16:24 Weiming Shi [this message]
2026-07-01 11:01 ` [PATCH] xfs: fail recovery on a committed log item with no regions Christoph Hellwig
2026-07-01 11:14 ` Christoph Hellwig
2026-07-01 15:43 ` Weiming Shi
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=20260629162452.2566242-2-bestswngs@gmail.com \
--to=bestswngs@gmail.com \
--cc=bfoster@redhat.com \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=xmei5@asu.edu \
/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