From: sanan.hasanou@gmail.com
To: shaggy@kernel.org, mjguzik@gmail.com, ssrane_b23@ee.vjti.ac.in,
brauner@kernel.org, jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Cc: syzkaller@googlegroups.com, contact@pgazz.com
Subject: invalid opcode in txEnd
Date: Fri, 26 Jun 2026 14:26:24 -0700 (PDT) [thread overview]
Message-ID: <6a3eee80.1dc473f3.8edd6.e736@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=1pN21FuDB9QSbn_3jaZGO1S5v7x7Qe-yl>
Unfortunately, we don't have any reproducer for this bug yet.
Thank you!
Best regards,
Sanan Hasanov
ERROR: (device loop2): xtSearch: xt_getpage: xtree page corrupt
ERROR: (device loop2): 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: 1 UID: 0 PID: 40842 Comm: syz.2.3616 Tainted: G L 7.0.0-rc1 #1 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
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+0x51f/0x530 fs/jfs/jfs_txnmgr.c:529
Code: e9 cc fe ff ff e8 b1 a5 82 fe 48 c7 c7 a0 9f 43 a7 48 c7 c6 99 9b 43 a7 ba 11 02 00 00 48 c7 c1 e0 9f 43 a7 e8 42 39 eb fd 90 <0f> 0b 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 55
RSP: 0018:ffffc9000418f3a0 EFLAGS: 00010246
RAX: 0000000000000036 RBX: ffff88803781c000 RCX: 41e5ad7fd48dbb00
RDX: ffffc90011c06000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: ffffc90000c12982 R08: ffff88806af2c8d3 R09: 1ffff1100d5e591a
R10: dffffc0000000000 R11: ffffed100d5e591b R12: 1ffff92000182535
R13: dffffc0000000000 R14: ffffc90000c129a8 R15: 0000000000000002
FS: 00007fc7348b16c0(0000) GS:ffff8880be5b6000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0d2e1ff000 CR3: 000000001ea67000 CR4: 00000000000006f0
Call Trace:
<TASK>
jfs_truncate_nolock+0x2b6/0x340 fs/jfs/inode.c:399
jfs_truncate+0xce/0x140 fs/jfs/inode.c:420
jfs_direct_IO+0x1ef/0x220 fs/jfs/inode.c:350
generic_file_direct_write+0x1d5/0x3e0 mm/filemap.c:4248
__generic_file_write_iter+0x118/0x230 mm/filemap.c:4417
generic_file_write_iter+0x117/0x540 mm/filemap.c:4457
iter_file_splice_write+0x9c2/0x1090 fs/splice.c:736
do_splice_from fs/splice.c:936 [inline]
direct_splice_actor+0xfb/0x150 fs/splice.c:1159
splice_direct_to_actor+0x52d/0xbd0 fs/splice.c:1103
do_splice_direct_actor fs/splice.c:1202 [inline]
do_splice_direct+0x181/0x270 fs/splice.c:1228
do_sendfile+0x4bb/0x7b0 fs/read_write.c:1372
__do_sys_sendfile64 fs/read_write.c:1433 [inline]
__se_sys_sendfile64+0x13e/0x190 fs/read_write.c:1419
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x11c/0x800 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x4b/0x53
RIP: 0033:0x7fc7339a3b6d
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:00007fc7348b1018 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fc733c16090 RCX: 00007fc7339a3b6d
RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000004
RBP: 00007fc733a47c3e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020fffe85 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc733c16128 R14: 00007fc733c16090 R15: 00007ffebd1495c0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txEnd+0x51f/0x530 fs/jfs/jfs_txnmgr.c:529
Code: e9 cc fe ff ff e8 b1 a5 82 fe 48 c7 c7 a0 9f 43 a7 48 c7 c6 99 9b 43 a7 ba 11 02 00 00 48 c7 c1 e0 9f 43 a7 e8 42 39 eb fd 90 <0f> 0b 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 55
RSP: 0018:ffffc9000418f3a0 EFLAGS: 00010246
RAX: 0000000000000036 RBX: ffff88803781c000 RCX: 41e5ad7fd48dbb00
RDX: ffffc90011c06000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: ffffc90000c12982 R08: ffff88806af2c8d3 R09: 1ffff1100d5e591a
R10: dffffc0000000000 R11: ffffed100d5e591b R12: 1ffff92000182535
R13: dffffc0000000000 R14: ffffc90000c129a8 R15: 0000000000000002
FS: 00007fc7348b16c0(0000) GS:ffff8880be5b6000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0d2e1ff000 CR3: 000000001ea67000 CR4: 00000000000006f0
<<<<<<<<<<<<<<< tail report >>>>>>>>>>>>>>>
next reply other threads:[~2026-06-26 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 21:26 sanan.hasanou [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-18 22:24 invalid opcode in txEnd sanan.hasanou
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=6a3eee80.1dc473f3.8edd6.e736@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 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.