[v6.6] kernel BUG in txLock
1 view
Skip to first unread message
syzbot
Dec 24, 2025, 3:44:20 PM12/24/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 5fa4793a2d2d Linux 6.6.119
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1243a022580000
kernel config: https://syzkaller.appspot.com/x/.config?x=691a6769a86ac817
dashboard link: https://syzkaller.appspot.com/bug?extid=be3c412c65c3d627c752
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63699875f1dd/disk-5fa4793a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8506652fcb6f/vmlinux-5fa4793a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b30ceed1710/bzImage-5fa4793a.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+be3c41...@syzkaller.appspotmail.com
BUG at fs/jfs/jfs_txnmgr.c:662 assert(last)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:662!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5926 Comm: syz.3.15 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:txLock+0x1cc1/0x2090 fs/jfs/jfs_txnmgr.c:662
Code: fe e9 29 f8 ff ff e8 ae 78 84 fe 48 c7 c7 00 10 e4 8a 48 c7 c6 f9 0b e4 8a ba 96 02 00 00 48 c7 c1 00 11 e4 8a e8 2f 13 5b 07 <0f> 0b e8 88 78 84 fe 48 c7 c7 c0 11 e4 8a e8 1c 13 5b 07 48 c7 c7
RSP: 0000:ffffc90003526880 EFLAGS: 00010246
RAX: 000000000000002b RBX: ffffc9000287a000 RCX: 7325ba7d8753d700
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900035269c8 R08: ffffc90003526587 R09: 1ffff920006a4cb0
R10: dffffc0000000000 R11: fffff520006a4cb1 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 1ffff9200050f400
FS: 00007fa14faaf6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffe70 CR3: 000000002f346000 CR4: 00000000003506f0
Call Trace:
<TASK>
diWrite+0x43f/0x1f20 fs/jfs/jfs_imap.c:654
txCommit+0x84c/0x5250 fs/jfs/jfs_txnmgr.c:1256
jfs_commit_inode+0x2f0/0x520 fs/jfs/inode.c:114
extAlloc+0xb9b/0xf30 fs/jfs/jfs_extent.c:172
jfs_get_block+0x347/0xab0 fs/jfs/inode.c:254
__block_write_begin_int+0x566/0x1ad0 fs/buffer.c:2124
__block_write_begin fs/buffer.c:2173 [inline]
block_write_begin+0x9a/0x1e0 fs/buffer.c:2234
jfs_write_begin+0x35/0x70 fs/jfs/inode.c:305
generic_perform_write+0x2fb/0x5b0 mm/filemap.c:4031
generic_file_write_iter+0xaf/0x2e0 mm/filemap.c:4152
__kernel_write_iter+0x274/0x670 fs/read_write.c:517
dump_emit_page fs/coredump.c:957 [inline]
dump_user_range+0x3f6/0x800 fs/coredump.c:984
elf_core_dump+0x3114/0x36e0 fs/binfmt_elf.c:2184
do_coredump+0x1755/0x2480 fs/coredump.c:833
get_signal+0x1133/0x1400 kernel/signal.c:2888
arch_do_signal_or_restart+0x9c/0x7b0 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:315
exc_page_fault+0x8f/0x110 arch/x86/mm/fault.c:1524
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7fa14eb8f751
Code: 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f
RSP: 002b:fffffffffffffe70 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007fa14ede6090 RCX: 00007fa14eb8f749
RDX: 0000000000000000 RSI: fffffffffffffe70 RDI: 0000000000008000
RBP: 00007fa14ec13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 00007fa14ede6128 R14: 00007fa14ede6090 R15: 00007ffccb92b858
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txLock+0x1cc1/0x2090 fs/jfs/jfs_txnmgr.c:662
Code: fe e9 29 f8 ff ff e8 ae 78 84 fe 48 c7 c7 00 10 e4 8a 48 c7 c6 f9 0b e4 8a ba 96 02 00 00 48 c7 c1 00 11 e4 8a e8 2f 13 5b 07 <0f> 0b e8 88 78 84 fe 48 c7 c7 c0 11 e4 8a e8 1c 13 5b 07 48 c7 c7
RSP: 0000:ffffc90003526880 EFLAGS: 00010246
RAX: 000000000000002b RBX: ffffc9000287a000 RCX: 7325ba7d8753d700
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900035269c8 R08: ffffc90003526587 R09: 1ffff920006a4cb0
R10: dffffc0000000000 R11: fffff520006a4cb1 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 1ffff9200050f400
FS: 00007fa14faaf6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa14ede7dac CR3: 000000002f346000 CR4: 00000000003506f0
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: 5fa4793a2d2d Linux 6.6.119
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1243a022580000
kernel config: https://syzkaller.appspot.com/x/.config?x=691a6769a86ac817
dashboard link: https://syzkaller.appspot.com/bug?extid=be3c412c65c3d627c752
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63699875f1dd/disk-5fa4793a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8506652fcb6f/vmlinux-5fa4793a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b30ceed1710/bzImage-5fa4793a.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+be3c41...@syzkaller.appspotmail.com
BUG at fs/jfs/jfs_txnmgr.c:662 assert(last)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:662!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5926 Comm: syz.3.15 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:txLock+0x1cc1/0x2090 fs/jfs/jfs_txnmgr.c:662
Code: fe e9 29 f8 ff ff e8 ae 78 84 fe 48 c7 c7 00 10 e4 8a 48 c7 c6 f9 0b e4 8a ba 96 02 00 00 48 c7 c1 00 11 e4 8a e8 2f 13 5b 07 <0f> 0b e8 88 78 84 fe 48 c7 c7 c0 11 e4 8a e8 1c 13 5b 07 48 c7 c7
RSP: 0000:ffffc90003526880 EFLAGS: 00010246
RAX: 000000000000002b RBX: ffffc9000287a000 RCX: 7325ba7d8753d700
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900035269c8 R08: ffffc90003526587 R09: 1ffff920006a4cb0
R10: dffffc0000000000 R11: fffff520006a4cb1 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 1ffff9200050f400
FS: 00007fa14faaf6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffe70 CR3: 000000002f346000 CR4: 00000000003506f0
Call Trace:
<TASK>
diWrite+0x43f/0x1f20 fs/jfs/jfs_imap.c:654
txCommit+0x84c/0x5250 fs/jfs/jfs_txnmgr.c:1256
jfs_commit_inode+0x2f0/0x520 fs/jfs/inode.c:114
extAlloc+0xb9b/0xf30 fs/jfs/jfs_extent.c:172
jfs_get_block+0x347/0xab0 fs/jfs/inode.c:254
__block_write_begin_int+0x566/0x1ad0 fs/buffer.c:2124
__block_write_begin fs/buffer.c:2173 [inline]
block_write_begin+0x9a/0x1e0 fs/buffer.c:2234
jfs_write_begin+0x35/0x70 fs/jfs/inode.c:305
generic_perform_write+0x2fb/0x5b0 mm/filemap.c:4031
generic_file_write_iter+0xaf/0x2e0 mm/filemap.c:4152
__kernel_write_iter+0x274/0x670 fs/read_write.c:517
dump_emit_page fs/coredump.c:957 [inline]
dump_user_range+0x3f6/0x800 fs/coredump.c:984
elf_core_dump+0x3114/0x36e0 fs/binfmt_elf.c:2184
do_coredump+0x1755/0x2480 fs/coredump.c:833
get_signal+0x1133/0x1400 kernel/signal.c:2888
arch_do_signal_or_restart+0x9c/0x7b0 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:315
exc_page_fault+0x8f/0x110 arch/x86/mm/fault.c:1524
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7fa14eb8f751
Code: 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f
RSP: 002b:fffffffffffffe70 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007fa14ede6090 RCX: 00007fa14eb8f749
RDX: 0000000000000000 RSI: fffffffffffffe70 RDI: 0000000000008000
RBP: 00007fa14ec13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 00007fa14ede6128 R14: 00007fa14ede6090 R15: 00007ffccb92b858
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txLock+0x1cc1/0x2090 fs/jfs/jfs_txnmgr.c:662
Code: fe e9 29 f8 ff ff e8 ae 78 84 fe 48 c7 c7 00 10 e4 8a 48 c7 c6 f9 0b e4 8a ba 96 02 00 00 48 c7 c1 00 11 e4 8a e8 2f 13 5b 07 <0f> 0b e8 88 78 84 fe 48 c7 c7 c0 11 e4 8a e8 1c 13 5b 07 48 c7 c7
RSP: 0000:ffffc90003526880 EFLAGS: 00010246
RAX: 000000000000002b RBX: ffffc9000287a000 RCX: 7325ba7d8753d700
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900035269c8 R08: ffffc90003526587 R09: 1ffff920006a4cb0
R10: dffffc0000000000 R11: fffff520006a4cb1 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 1ffff9200050f400
FS: 00007fa14faaf6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa14ede7dac CR3: 000000002f346000 CR4: 00000000003506f0
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Dec 24, 2025, 5:23:21 PM12/24/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 5fa4793a2d2d Linux 6.6.119
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11202bb4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c7cb92580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63699875f1dd/disk-5fa4793a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8506652fcb6f/vmlinux-5fa4793a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b30ceed1710/bzImage-5fa4793a.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/1ecfb34aece6/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=16202bb4580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+be3c41...@syzkaller.appspotmail.com
BUG at fs/jfs/jfs_txnmgr.c:662 assert(last)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:662!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 6052 Comm: syz.1.18 Not tainted syzkaller #0
RAX: 000000000000002b RBX: ffffc9000282a000 RCX: 08cd9b7b3ed83d00
R10: dffffc0000000000 R11: fffff52000706cb1 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 1ffff92000505400
FS: 000055557ba77500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
RIP: 0033:0x7f2a4238f751
RAX: 000000000000002b RBX: ffffc9000282a000 RCX: 08cd9b7b3ed83d00
R10: dffffc0000000000 R11: fffff52000706cb1 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 1ffff92000505400
FS: 000055557ba77500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
HEAD commit: 5fa4793a2d2d Linux 6.6.119
git tree: linux-6.6.y
kernel config: https://syzkaller.appspot.com/x/.config?x=691a6769a86ac817
dashboard link: https://syzkaller.appspot.com/bug?extid=be3c412c65c3d627c752
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1467a022580000
dashboard link: https://syzkaller.appspot.com/bug?extid=be3c412c65c3d627c752
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c7cb92580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63699875f1dd/disk-5fa4793a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8506652fcb6f/vmlinux-5fa4793a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b30ceed1710/bzImage-5fa4793a.xz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=16202bb4580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+be3c41...@syzkaller.appspotmail.com
BUG at fs/jfs/jfs_txnmgr.c:662 assert(last)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:662!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:txLock+0x1cc1/0x2090 fs/jfs/jfs_txnmgr.c:662
Code: fe e9 29 f8 ff ff e8 ae 78 84 fe 48 c7 c7 00 10 e4 8a 48 c7 c6 f9 0b e4 8a ba 96 02 00 00 48 c7 c1 00 11 e4 8a e8 2f 13 5b 07 <0f> 0b e8 88 78 84 fe 48 c7 c7 c0 11 e4 8a e8 1c 13 5b 07 48 c7 c7
RSP: 0018:ffffc90003836880 EFLAGS: 00010246
RIP: 0010:txLock+0x1cc1/0x2090 fs/jfs/jfs_txnmgr.c:662
Code: fe e9 29 f8 ff ff e8 ae 78 84 fe 48 c7 c7 00 10 e4 8a 48 c7 c6 f9 0b e4 8a ba 96 02 00 00 48 c7 c1 00 11 e4 8a e8 2f 13 5b 07 <0f> 0b e8 88 78 84 fe 48 c7 c7 c0 11 e4 8a e8 1c 13 5b 07 48 c7 c7
RAX: 000000000000002b RBX: ffffc9000282a000 RCX: 08cd9b7b3ed83d00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900038369c8 R08: ffffc90003836587 R09: 1ffff92000706cb0
R10: dffffc0000000000 R11: fffff52000706cb1 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 1ffff92000505400
FS: 000055557ba77500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007effac3d0000 CR3: 000000002e1e5000 CR4: 00000000003506f0
Code: 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f
RSP: 002b:fffffffffffffe70 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007f2a425e5fa0 RCX: 00007f2a4238f749
RSP: 002b:fffffffffffffe70 EFLAGS: 00010217
RDX: 0000000000000000 RSI: fffffffffffffe70 RDI: 0000000000008000
RBP: 00007f2a42413f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 00007f2a425e5fa0 R14: 00007f2a425e5fa0 R15: 0000000000000006
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txLock+0x1cc1/0x2090 fs/jfs/jfs_txnmgr.c:662
Code: fe e9 29 f8 ff ff e8 ae 78 84 fe 48 c7 c7 00 10 e4 8a 48 c7 c6 f9 0b e4 8a ba 96 02 00 00 48 c7 c1 00 11 e4 8a e8 2f 13 5b 07 <0f> 0b e8 88 78 84 fe 48 c7 c7 c0 11 e4 8a e8 1c 13 5b 07 48 c7 c7
RSP: 0018:ffffc90003836880 EFLAGS: 00010246
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txLock+0x1cc1/0x2090 fs/jfs/jfs_txnmgr.c:662
Code: fe e9 29 f8 ff ff e8 ae 78 84 fe 48 c7 c7 00 10 e4 8a 48 c7 c6 f9 0b e4 8a ba 96 02 00 00 48 c7 c1 00 11 e4 8a e8 2f 13 5b 07 <0f> 0b e8 88 78 84 fe 48 c7 c7 c0 11 e4 8a e8 1c 13 5b 07 48 c7 c7
RAX: 000000000000002b RBX: ffffc9000282a000 RCX: 08cd9b7b3ed83d00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900038369c8 R08: ffffc90003836587 R09: 1ffff92000706cb0
R10: dffffc0000000000 R11: fffff52000706cb1 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 1ffff92000505400
FS: 000055557ba77500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007effac3e7000 CR3: 000000002e1e5000 CR4: 00000000003506e0
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages