[v6.6] kernel BUG in do_journal_release
2 views
Skip to first unread message
syzbot
Jul 27, 2025, 1:48:36 PM7/27/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16e674f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=2e74a8aa09597f00683c
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2e74a8...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:1916!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5782 Comm: syz-executor Not tainted 6.6.100-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:do_journal_release+0x53a/0x550 fs/reiserfs/journal.c:1916
Code: b6 ff e9 49 fc ff ff 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c b9 fc ff ff 4c 89 ff e8 d0 c6 b6 ff e9 ac fc ff ff e8 e6 80 5f ff <0f> 0b e8 df 80 5f ff 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00
RSP: 0018:ffffc9000474fb00 EFLAGS: 00010293
RAX: ffffffff8226149a RBX: ffff888059874000 RCX: ffff888029c51e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000474fbf8 R08: ffffc9000474fb77 R09: 0000000000000000
R10: ffffc9000474fb40 R11: fffff520008e9f6f R12: ffffc90005219000
R13: 1ffff920008e9f64 R14: ffff888059874630 R15: 0000000000000000
FS: 0000555556391500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555563ac5c8 CR3: 000000006113a000 CR4: 00000000003506f0
Call Trace:
<TASK>
journal_release+0x1f/0x30 fs/reiserfs/journal.c:1971
reiserfs_put_super+0x222/0x480 fs/reiserfs/super.c:616
generic_shutdown_super+0x134/0x2b0 fs/super.c:693
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa1d0f8fcd7
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffc45bb0ee8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007fa1d1010b55 RCX: 00007fa1d0f8fcd7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc45bb0fa0
RBP: 00007ffc45bb0fa0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc45bb2030
R13: 00007fa1d1010b55 R14: 0000000000086e5a R15: 00007ffc45bb2070
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:do_journal_release+0x53a/0x550 fs/reiserfs/journal.c:1916
Code: b6 ff e9 49 fc ff ff 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c b9 fc ff ff 4c 89 ff e8 d0 c6 b6 ff e9 ac fc ff ff e8 e6 80 5f ff <0f> 0b e8 df 80 5f ff 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00
RSP: 0018:ffffc9000474fb00 EFLAGS: 00010293
RAX: ffffffff8226149a RBX: ffff888059874000 RCX: ffff888029c51e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000474fbf8 R08: ffffc9000474fb77 R09: 0000000000000000
R10: ffffc9000474fb40 R11: fffff520008e9f6f R12: ffffc90005219000
R13: 1ffff920008e9f64 R14: ffff888059874630 R15: 0000000000000000
FS: 0000555556391500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f33c45ffd58 CR3: 000000006113a000 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: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16e674f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=2e74a8aa09597f00683c
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2e74a8...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:1916!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5782 Comm: syz-executor Not tainted 6.6.100-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:do_journal_release+0x53a/0x550 fs/reiserfs/journal.c:1916
Code: b6 ff e9 49 fc ff ff 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c b9 fc ff ff 4c 89 ff e8 d0 c6 b6 ff e9 ac fc ff ff e8 e6 80 5f ff <0f> 0b e8 df 80 5f ff 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00
RSP: 0018:ffffc9000474fb00 EFLAGS: 00010293
RAX: ffffffff8226149a RBX: ffff888059874000 RCX: ffff888029c51e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000474fbf8 R08: ffffc9000474fb77 R09: 0000000000000000
R10: ffffc9000474fb40 R11: fffff520008e9f6f R12: ffffc90005219000
R13: 1ffff920008e9f64 R14: ffff888059874630 R15: 0000000000000000
FS: 0000555556391500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555563ac5c8 CR3: 000000006113a000 CR4: 00000000003506f0
Call Trace:
<TASK>
journal_release+0x1f/0x30 fs/reiserfs/journal.c:1971
reiserfs_put_super+0x222/0x480 fs/reiserfs/super.c:616
generic_shutdown_super+0x134/0x2b0 fs/super.c:693
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa1d0f8fcd7
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffc45bb0ee8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007fa1d1010b55 RCX: 00007fa1d0f8fcd7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc45bb0fa0
RBP: 00007ffc45bb0fa0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc45bb2030
R13: 00007fa1d1010b55 R14: 0000000000086e5a R15: 00007ffc45bb2070
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:do_journal_release+0x53a/0x550 fs/reiserfs/journal.c:1916
Code: b6 ff e9 49 fc ff ff 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c b9 fc ff ff 4c 89 ff e8 d0 c6 b6 ff e9 ac fc ff ff e8 e6 80 5f ff <0f> 0b e8 df 80 5f ff 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00
RSP: 0018:ffffc9000474fb00 EFLAGS: 00010293
RAX: ffffffff8226149a RBX: ffff888059874000 RCX: ffff888029c51e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000474fbf8 R08: ffffc9000474fb77 R09: 0000000000000000
R10: ffffc9000474fb40 R11: fffff520008e9f6f R12: ffffc90005219000
R13: 1ffff920008e9f64 R14: ffff888059874630 R15: 0000000000000000
FS: 0000555556391500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f33c45ffd58 CR3: 000000006113a000 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
Jul 27, 2025, 2:39:39 PM7/27/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14cdd8a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12cdd8a2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/46186646feba/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=142a98a2580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2e74a8...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:1916!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5894 Comm: syz-executor Not tainted 6.6.100-syzkaller #0
RAX: ffffffff8226149a RBX: ffff888025224000 RCX: ffff88802a7d9e00
R10: ffffc90003057b40 R11: fffff5200060af6f R12: ffffc900033f9000
R13: 1ffff9200060af64 R14: ffff888025224630 R15: 0000000000000000
FS: 0000555569728500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
RAX: 0000000000000000 RBX: 00007f506f610b55 RCX: 00007f506f58fcd7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffcdb81dd00
RBP: 00007ffcdb81dd00 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffcdb81ed90
R13: 00007f506f610b55 R14: 0000000000013db0 R15: 00007ffcdb81edd0
RAX: ffffffff8226149a RBX: ffff888025224000 RCX: ffff88802a7d9e00
R10: ffffc90003057b40 R11: fffff5200060af6f R12: ffffc900033f9000
R13: 1ffff9200060af64 R14: ffff888025224630 R15: 0000000000000000
FS: 0000555569728500(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: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=2e74a8aa09597f00683c
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143e74f0580000
dashboard link: https://syzkaller.appspot.com/bug?extid=2e74a8aa09597f00683c
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12cdd8a2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=142a98a2580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2e74a8...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:1916!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:do_journal_release+0x53a/0x550 fs/reiserfs/journal.c:1916
Code: b6 ff e9 49 fc ff ff 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c b9 fc ff ff 4c 89 ff e8 d0 c6 b6 ff e9 ac fc ff ff e8 e6 80 5f ff <0f> 0b e8 df 80 5f ff 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00
RSP: 0018:ffffc90003057b00 EFLAGS: 00010293
RIP: 0010:do_journal_release+0x53a/0x550 fs/reiserfs/journal.c:1916
Code: b6 ff e9 49 fc ff ff 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c b9 fc ff ff 4c 89 ff e8 d0 c6 b6 ff e9 ac fc ff ff e8 e6 80 5f ff <0f> 0b e8 df 80 5f ff 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00
RAX: ffffffff8226149a RBX: ffff888025224000 RCX: ffff88802a7d9e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003057bf8 R08: ffffc90003057b77 R09: 0000000000000000
R10: ffffc90003057b40 R11: fffff5200060af6f R12: ffffc900033f9000
R13: 1ffff9200060af64 R14: ffff888025224630 R15: 0000000000000000
FS: 0000555569728500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2c15ffff CR3: 00000000615d6000 CR4: 00000000003506e0
Call Trace:
<TASK>
journal_release+0x1f/0x30 fs/reiserfs/journal.c:1971
reiserfs_put_super+0x222/0x480 fs/reiserfs/super.c:616
generic_shutdown_super+0x134/0x2b0 fs/super.c:693
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f506f58fcd7
<TASK>
journal_release+0x1f/0x30 fs/reiserfs/journal.c:1971
reiserfs_put_super+0x222/0x480 fs/reiserfs/super.c:616
generic_shutdown_super+0x134/0x2b0 fs/super.c:693
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffcdb81dc48 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f506f610b55 RCX: 00007f506f58fcd7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffcdb81dd00
RBP: 00007ffcdb81dd00 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffcdb81ed90
R13: 00007f506f610b55 R14: 0000000000013db0 R15: 00007ffcdb81edd0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:do_journal_release+0x53a/0x550 fs/reiserfs/journal.c:1916
Code: b6 ff e9 49 fc ff ff 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c b9 fc ff ff 4c 89 ff e8 d0 c6 b6 ff e9 ac fc ff ff e8 e6 80 5f ff <0f> 0b e8 df 80 5f ff 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00
RSP: 0018:ffffc90003057b00 EFLAGS: 00010293
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:do_journal_release+0x53a/0x550 fs/reiserfs/journal.c:1916
Code: b6 ff e9 49 fc ff ff 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c b9 fc ff ff 4c 89 ff e8 d0 c6 b6 ff e9 ac fc ff ff e8 e6 80 5f ff <0f> 0b e8 df 80 5f ff 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00
RAX: ffffffff8226149a RBX: ffff888025224000 RCX: ffff88802a7d9e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003057bf8 R08: ffffc90003057b77 R09: 0000000000000000
R10: ffffc90003057b40 R11: fffff5200060af6f R12: ffffc900033f9000
R13: 1ffff9200060af64 R14: ffff888025224630 R15: 0000000000000000
FS: 0000555569728500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2c15ffff CR3: 00000000615d6000 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