From: CJ <firefly0158@163.com>
To: shaggy@kernel.org, yun.zhou@windriver.com, mjguzik@gmail.com,
brauner@kernel.org, ssrane_b23@ee.vjti.ac.in
Cc: jfs-discussion@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [BUG] jfs: kernel BUG in txEnd at fs/jfs/jfs_txnmgr.c
Date: Tue, 15 Sep 2026 14:35:54 +0800 (CST) [thread overview]
Message-ID: <443ec676.55de.1a0a3c7799d.Coremail.firefly0158@163.com> (raw)
Hi,
I am reporting a kernel BUG in the JFS transaction manager, triggered by a
syzkaller reproducer that mounts a crafted JFS image. The issue is reproducible
with HEAD commit cee9395acd8043be0644b25c34bfa86623f2b935 (v7.3-rc1, Linux
7.3.0-rc1).
The reproducer mounts a crafted JFS filesystem image on a loop device and then
truncates a file, which makes JFS walk a corrupt extent tree.
The console shows the truncate path reporting a corrupt xtree page and remounting
the filesystem read-only, and then "kernel BUG at fs/jfs/jfs_txnmgr.c:530!" with
an invalid-opcode Oops and RIP in txEnd. The assertion at that site is
assert(tblk->next == 0), so the transaction block being ended is still linked.
One possible cause is that the error path taken after the corrupt xtree page is
detected ends the transaction twice, or leaves a transaction block linked when
txEnd expects it to be detached, so the linked-list invariant the assertion
checks is violated. This looks like state management of the transaction block
list on an error path rather than a bounds problem. I am reporting the
assertion and the path as observed.
This appears to be a recurrence of the syzbot issue whose external id is
914c3cb75ef219729a2e. It remains reproducible on v7.3-rc1.
Reproducer:
syz reproducer: https://pastebin.com/raw/V4Mc0vrp
console output: https://pastebin.com/raw/8K3r0xpr
kernel config: https://pastebin.com/raw/zRz2p0BE
Kernel:
HEAD commit: cee9395acd8043be0644b25c34bfa86623f2b935
git tree: upstream (linux.git), tested through the v7.3-rc1 annotated tag object
e5e04726cdd043e309677071ab1b65a4b18f422b
kernel version: 7.3.0-rc1 #1 PREEMPT(full)
tested tag: v7.3-rc1 (Linux 7.3-rc1, 2026-08-30)
Let me know if you need more details or testing.
Best regards,
Changjian
reply other threads:[~2026-09-15 6:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=443ec676.55de.1a0a3c7799d.Coremail.firefly0158@163.com \
--to=firefly0158@163.com \
--cc=brauner@kernel.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=shaggy@kernel.org \
--cc=ssrane_b23@ee.vjti.ac.in \
--cc=yun.zhou@windriver.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®