From: sanan.hasanou@gmail.com
To: shaggy@kernel.org, ssrane_b23@ee.vjti.ac.in, brauner@kernel.org,
mjguzik@gmail.com, jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Cc: syzkaller@googlegroups.com, contact@pgazz.com
Subject: invalid opcode in txEnd
Date: Thu, 18 Jun 2026 15:24:18 -0700 (PDT) [thread overview]
Message-ID: <6a347012.1dc473f3.15328a.f0cf@mx.google.com> (raw)
Good day, dear maintainers,
We found a bug using a modified version of syzkaller.
Kernel Branch: 7.0-rc1
Kernel Config: <https://drive.google.com/open?id=1RsqMUgdFUMq9-iREK8DZCvDfjq0RWm5X>
Unfortunately, we don't have any reproducer for this bug yet.
Thank you!
Best regards,
Sanan Hasanov
ERROR: (device loop6): xtSearch: xt_getpage: xtree page corrupt
ERROR: (device loop6): xtTruncate: xt_getpage: xtree page corrupt
BUG at fs/jfs/jfs_txnmgr.c:529 assert(tblk->next == 0)
Oops: invalid opcode: 0000 [#1] SMP KASAN
CPU: 0 UID: 0 PID: 27056 Comm: syz.6.1685 Not tainted 7.0.0-rc1 #1 PREEMPT(full)
Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:txEnd+0x359/0x360 fs/jfs/jfs_txnmgr.c:529
Code: e9 39 fe ff ff e8 07 f3 87 fe 48 c7 c7 a0 68 e8 8a 48 c7 c6 79 65 e8 8a ba 11 02 00 00 48 c7 c1 00 69 e8 8a e8 88 63 18 fe 90 <0f> 0b 0f 1f 44 00 00 f3 0f 1e fa 0f 1f 44 00 00 55 48 89 e5 41 57
RSP: 0018:ffffc9000411f3a0 EFLAGS: 00010246
RAX: 0000000000000036 RBX: ffff88806d6ee800 RCX: f475f6793eddb000
RDX: ffffc9001289f000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: ffffc9000411f3d0 R08: ffff88802c62d9d3 R09: 1ffff110058c5b3a
R10: dffffc0000000000 R11: ffffed10058c5b3b R12: 00000000000000aa
R13: dffffc0000000000 R14: 1ffff9200034aaa7 R15: ffffc90001a55538
FS: 00007f11434056c0(0000) GS:ffff88809d305000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7fd4c5fe70 CR3: 00000000138ae000 CR4: 00000000000006f0
Call Trace:
<TASK>
jfs_truncate_nolock+0x2b6/0x320 fs/jfs/inode.c:399
jfs_truncate fs/jfs/inode.c:420 [inline]
jfs_write_failed+0xf7/0x120 fs/jfs/inode.c:295
jfs_direct_IO+0x1fe/0x230 fs/jfs/inode.c:350
generic_file_direct_write+0x1d1/0x3d0 mm/filemap.c:4248
__generic_file_write_iter+0xe1/0x180 mm/filemap.c:4417
generic_file_write_iter+0x11c/0x550 mm/filemap.c:4457
iter_file_splice_write+0xa2a/0x11b0 fs/splice.c:736
do_splice_from fs/splice.c:936 [inline]
direct_splice_actor+0x119/0x300 fs/splice.c:1159
splice_direct_to_actor+0x4a8/0xaf0 fs/splice.c:1103
do_splice_direct_actor fs/splice.c:1202 [inline]
do_splice_direct+0x186/0x270 fs/splice.c:1228
do_sendfile+0x4c0/0x7b0 fs/read_write.c:1372
__do_sys_sendfile64 fs/read_write.c:1433 [inline]
__se_sys_sendfile64 fs/read_write.c:1419 [inline]
__x64_sys_sendfile64+0x1b0/0x200 fs/read_write.c:1419
x64_sys_call+0x278e/0x2900 arch/x86/include/generated/asm/syscalls_64.h:41
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x110/0x8a0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x4b/0x53
RIP: 0033:0x7f11451d3b6d
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f1143405018 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f1145446090 RCX: 00007f11451d3b6d
RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000004
RBP: 00007f1145277c3e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020fffe85 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1145446128 R14: 00007f1145446090 R15: 00007ffe757238b0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txEnd+0x359/0x360 fs/jfs/jfs_txnmgr.c:529
Code: e9 39 fe ff ff e8 07 f3 87 fe 48 c7 c7 a0 68 e8 8a 48 c7 c6 79 65 e8 8a ba 11 02 00 00 48 c7 c1 00 69 e8 8a e8 88 63 18 fe 90 <0f> 0b 0f 1f 44 00 00 f3 0f 1e fa 0f 1f 44 00 00 55 48 89 e5 41 57
RSP: 0018:ffffc9000411f3a0 EFLAGS: 00010246
RAX: 0000000000000036 RBX: ffff88806d6ee800 RCX: f475f6793eddb000
RDX: ffffc9001289f000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: ffffc9000411f3d0 R08: ffff88802c62d9d3 R09: 1ffff110058c5b3a
R10: dffffc0000000000 R11: ffffed10058c5b3b R12: 00000000000000aa
R13: dffffc0000000000 R14: 1ffff9200034aaa7 R15: ffffc90001a55538
FS: 00007f11434056c0(0000) GS:ffff88809d305000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7fd4c5fe70 CR3: 00000000138ae000 CR4: 00000000000006f0
<<<<<<<<<<<<<<< tail report >>>>>>>>>>>>>>>
reply other threads:[~2026-06-18 22:24 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=6a347012.1dc473f3.15328a.f0cf@mx.google.com \
--to=sanan.hasanou@gmail.com \
--cc=brauner@kernel.org \
--cc=contact@pgazz.com \
--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=syzkaller@googlegroups.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