[v6.6] kernel BUG in reiserfs_in_journal
0 views
Skip to first unread message
syzbot
Sep 22, 2025, 12:09:28 AM (2 days ago) Sep 22
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: af1544b5d072 Linux 6.6.107
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13030142580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=03afadbb064df0e6e321
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/70417990f48e/disk-af1544b5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1513b6e63f4f/vmlinux-af1544b5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5648a8356789/bzImage-af1544b5.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+03afad...@syzkaller.appspotmail.com
REISERFS (device loop1): checking transaction log (loop1)
REISERFS (device loop1): Using tea hash to sort names
REISERFS (device loop1): Created .reiserfs_priv - reserved for xattr storage.
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:505!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 13594 Comm: syz.1.2237 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:reiserfs_in_journal+0xa4e/0xa50 fs/reiserfs/journal.c:505
Code: 24 30 80 e2 07 80 c2 03 38 ca 0f 8c 73 fe ff ff 48 8b 7c 24 30 48 89 c3 e8 4f e1 b6 ff 48 89 d8 e9 5e fe ff ff e8 a2 95 5f ff <0f> 0b 66 0f 1f 00 55 41 57 41 56 41 55 41 54 53 50 49 89 fc 48 bd
RSP: 0018:ffffc9000b8f7008 EFLAGS: 00010283
RAX: ffffffff822601fe RBX: ffff88807ce30000 RCX: 0000000000080000
RDX: ffffc9000d0eb000 RSI: 0000000000002afd RDI: 0000000000002afe
RBP: ffff88807ce30630 R08: ffffc9000b8f7140 R09: 1ffff11008695208
R10: dffffc0000000000 R11: ffffed1008695209 R12: ffffc9000bce3048
R13: ffffc9000bce3050 R14: dffffc0000000000 R15: 0000000000000213
FS: 00007fc5027b16c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff38f360000 CR3: 0000000065fa2000 CR4: 00000000003506f0
Call Trace:
<TASK>
is_block_in_journal fs/reiserfs/bitmap.c:125 [inline]
scan_bitmap_block+0x48a/0xde0 fs/reiserfs/bitmap.c:203
scan_bitmap fs/reiserfs/bitmap.c:408 [inline]
allocate_without_wrapping_disk fs/reiserfs/bitmap.c:1161 [inline]
blocknrs_and_prealloc_arrays_from_search_start fs/reiserfs/bitmap.c:1274 [inline]
reiserfs_allocate_blocknrs+0x370f/0x53c0 fs/reiserfs/bitmap.c:1375
_allocate_block fs/reiserfs/inode.c:-1 [inline]
reiserfs_get_block+0x2659/0x3ed0 fs/reiserfs/inode.c:756
__block_write_begin_int+0x566/0x1ad0 fs/buffer.c:2124
reiserfs_write_begin+0x20a/0x4c0 fs/reiserfs/inode.c:2771
generic_perform_write+0x2fb/0x5b0 mm/filemap.c:4016
generic_file_write_iter+0xaf/0x2e0 mm/filemap.c:4137
call_write_iter include/linux/fs.h:2018 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x43b/0x940 fs/read_write.c:584
ksys_write+0x147/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc50198ec29
Code: ff ff c3 66 2e 0f 1f 84 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
RSP: 002b:00007fc5027b1038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fc501bd5fa0 RCX: 00007fc50198ec29
RDX: 000000000208e24b RSI: 0000200000000240 RDI: 0000000000000009
RBP: 00007fc501a11e41 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc501bd6038 R14: 00007fc501bd5fa0 R15: 00007fff0427d578
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:reiserfs_in_journal+0xa4e/0xa50 fs/reiserfs/journal.c:505
Code: 24 30 80 e2 07 80 c2 03 38 ca 0f 8c 73 fe ff ff 48 8b 7c 24 30 48 89 c3 e8 4f e1 b6 ff 48 89 d8 e9 5e fe ff ff e8 a2 95 5f ff <0f> 0b 66 0f 1f 00 55 41 57 41 56 41 55 41 54 53 50 49 89 fc 48 bd
RSP: 0018:ffffc9000b8f7008 EFLAGS: 00010283
RAX: ffffffff822601fe RBX: ffff88807ce30000 RCX: 0000000000080000
RDX: ffffc9000d0eb000 RSI: 0000000000002afd RDI: 0000000000002afe
RBP: ffff88807ce30630 R08: ffffc9000b8f7140 R09: 1ffff11008695208
R10: dffffc0000000000 R11: ffffed1008695209 R12: ffffc9000bce3048
R13: ffffc9000bce3050 R14: dffffc0000000000 R15: 0000000000000213
FS: 00007fc5027b16c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff38f360000 CR3: 0000000065fa2000 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: af1544b5d072 Linux 6.6.107
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13030142580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=03afadbb064df0e6e321
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/70417990f48e/disk-af1544b5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1513b6e63f4f/vmlinux-af1544b5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5648a8356789/bzImage-af1544b5.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+03afad...@syzkaller.appspotmail.com
REISERFS (device loop1): checking transaction log (loop1)
REISERFS (device loop1): Using tea hash to sort names
REISERFS (device loop1): Created .reiserfs_priv - reserved for xattr storage.
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:505!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 13594 Comm: syz.1.2237 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:reiserfs_in_journal+0xa4e/0xa50 fs/reiserfs/journal.c:505
Code: 24 30 80 e2 07 80 c2 03 38 ca 0f 8c 73 fe ff ff 48 8b 7c 24 30 48 89 c3 e8 4f e1 b6 ff 48 89 d8 e9 5e fe ff ff e8 a2 95 5f ff <0f> 0b 66 0f 1f 00 55 41 57 41 56 41 55 41 54 53 50 49 89 fc 48 bd
RSP: 0018:ffffc9000b8f7008 EFLAGS: 00010283
RAX: ffffffff822601fe RBX: ffff88807ce30000 RCX: 0000000000080000
RDX: ffffc9000d0eb000 RSI: 0000000000002afd RDI: 0000000000002afe
RBP: ffff88807ce30630 R08: ffffc9000b8f7140 R09: 1ffff11008695208
R10: dffffc0000000000 R11: ffffed1008695209 R12: ffffc9000bce3048
R13: ffffc9000bce3050 R14: dffffc0000000000 R15: 0000000000000213
FS: 00007fc5027b16c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff38f360000 CR3: 0000000065fa2000 CR4: 00000000003506f0
Call Trace:
<TASK>
is_block_in_journal fs/reiserfs/bitmap.c:125 [inline]
scan_bitmap_block+0x48a/0xde0 fs/reiserfs/bitmap.c:203
scan_bitmap fs/reiserfs/bitmap.c:408 [inline]
allocate_without_wrapping_disk fs/reiserfs/bitmap.c:1161 [inline]
blocknrs_and_prealloc_arrays_from_search_start fs/reiserfs/bitmap.c:1274 [inline]
reiserfs_allocate_blocknrs+0x370f/0x53c0 fs/reiserfs/bitmap.c:1375
_allocate_block fs/reiserfs/inode.c:-1 [inline]
reiserfs_get_block+0x2659/0x3ed0 fs/reiserfs/inode.c:756
__block_write_begin_int+0x566/0x1ad0 fs/buffer.c:2124
reiserfs_write_begin+0x20a/0x4c0 fs/reiserfs/inode.c:2771
generic_perform_write+0x2fb/0x5b0 mm/filemap.c:4016
generic_file_write_iter+0xaf/0x2e0 mm/filemap.c:4137
call_write_iter include/linux/fs.h:2018 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x43b/0x940 fs/read_write.c:584
ksys_write+0x147/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc50198ec29
Code: ff ff c3 66 2e 0f 1f 84 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
RSP: 002b:00007fc5027b1038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fc501bd5fa0 RCX: 00007fc50198ec29
RDX: 000000000208e24b RSI: 0000200000000240 RDI: 0000000000000009
RBP: 00007fc501a11e41 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc501bd6038 R14: 00007fc501bd5fa0 R15: 00007fff0427d578
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:reiserfs_in_journal+0xa4e/0xa50 fs/reiserfs/journal.c:505
Code: 24 30 80 e2 07 80 c2 03 38 ca 0f 8c 73 fe ff ff 48 8b 7c 24 30 48 89 c3 e8 4f e1 b6 ff 48 89 d8 e9 5e fe ff ff e8 a2 95 5f ff <0f> 0b 66 0f 1f 00 55 41 57 41 56 41 55 41 54 53 50 49 89 fc 48 bd
RSP: 0018:ffffc9000b8f7008 EFLAGS: 00010283
RAX: ffffffff822601fe RBX: ffff88807ce30000 RCX: 0000000000080000
RDX: ffffc9000d0eb000 RSI: 0000000000002afd RDI: 0000000000002afe
RBP: ffff88807ce30630 R08: ffffc9000b8f7140 R09: 1ffff11008695208
R10: dffffc0000000000 R11: ffffed1008695209 R12: ffffc9000bce3048
R13: ffffc9000bce3050 R14: dffffc0000000000 R15: 0000000000000213
FS: 00007fc5027b16c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff38f360000 CR3: 0000000065fa2000 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
Sep 22, 2025, 1:17:29 AM (2 days ago) Sep 22
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: af1544b5d072 Linux 6.6.107
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11eb0142580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1728d8e2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/70417990f48e/disk-af1544b5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1513b6e63f4f/vmlinux-af1544b5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5648a8356789/bzImage-af1544b5.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/507ab16ece03/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=160a68e2580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+03afad...@syzkaller.appspotmail.com
REISERFS (device loop0): journal params: device loop0, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30
REISERFS (device loop0): checking transaction log (loop0)
REISERFS (device loop0): Using tea hash to sort names
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
RAX: ffffffff822601fe RBX: ffff88802cf14000 RCX: ffff88802c4d9e00
RDX: 0000000000000000 RSI: 0000000000000213 RDI: 0000000000000213
RBP: ffff88802cf14630 R08: ffffc90003237140 R09: 1ffff1100d787e08
R10: dffffc0000000000 R11: ffffed100d787e09 R12: ffffc9000346b048
R13: ffffc9000346b050 R14: dffffc0000000000 R15: 0000000000000213
FS: 0000555579aa5500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
RAX: ffffffffffffffda RBX: 00007efcb8bd5fa0 RCX: 00007efcb898ec29
RDX: 000000000208e24b RSI: 0000200000000240 RDI: 0000000000000004
RBP: 00007efcb8a11e41 R08: 0000000000000000 R09: 0000000000000000
RAX: ffffffff822601fe RBX: ffff88802cf14000 RCX: ffff88802c4d9e00
RDX: 0000000000000000 RSI: 0000000000000213 RDI: 0000000000000213
RBP: ffff88802cf14630 R08: ffffc90003237140 R09: 1ffff1100d787e08
R10: dffffc0000000000 R11: ffffed100d787e09 R12: ffffc9000346b048
R13: ffffc9000346b050 R14: dffffc0000000000 R15: 0000000000000213
FS: 0000555579aa5500(0000) GS:ffff8880b8e00000(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: af1544b5d072 Linux 6.6.107
git tree: linux-6.6.y
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=03afadbb064df0e6e321
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=132028e2580000
dashboard link: https://syzkaller.appspot.com/bug?extid=03afadbb064df0e6e321
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=1728d8e2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/70417990f48e/disk-af1544b5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1513b6e63f4f/vmlinux-af1544b5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5648a8356789/bzImage-af1544b5.xz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=160a68e2580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+03afad...@syzkaller.appspotmail.com
REISERFS (device loop0): checking transaction log (loop0)
REISERFS (device loop0): Using tea hash to sort names
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:505!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5951 Comm: syz.0.17 Not tainted syzkaller #0
kernel BUG at fs/reiserfs/journal.c:505!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:reiserfs_in_journal+0xa4e/0xa50 fs/reiserfs/journal.c:505
Code: 24 30 80 e2 07 80 c2 03 38 ca 0f 8c 73 fe ff ff 48 8b 7c 24 30 48 89 c3 e8 4f e1 b6 ff 48 89 d8 e9 5e fe ff ff e8 a2 95 5f ff <0f> 0b 66 0f 1f 00 55 41 57 41 56 41 55 41 54 53 50 49 89 fc 48 bd
RSP: 0018:ffffc90003237008 EFLAGS: 00010293
RIP: 0010:reiserfs_in_journal+0xa4e/0xa50 fs/reiserfs/journal.c:505
Code: 24 30 80 e2 07 80 c2 03 38 ca 0f 8c 73 fe ff ff 48 8b 7c 24 30 48 89 c3 e8 4f e1 b6 ff 48 89 d8 e9 5e fe ff ff e8 a2 95 5f ff <0f> 0b 66 0f 1f 00 55 41 57 41 56 41 55 41 54 53 50 49 89 fc 48 bd
RAX: ffffffff822601fe RBX: ffff88802cf14000 RCX: ffff88802c4d9e00
RDX: 0000000000000000 RSI: 0000000000000213 RDI: 0000000000000213
RBP: ffff88802cf14630 R08: ffffc90003237140 R09: 1ffff1100d787e08
R10: dffffc0000000000 R11: ffffed100d787e09 R12: ffffc9000346b048
R13: ffffc9000346b050 R14: dffffc0000000000 R15: 0000000000000213
FS: 0000555579aa5500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2d963fff CR3: 000000002597d000 CR4: 00000000003506e0
Call Trace:
<TASK>
is_block_in_journal fs/reiserfs/bitmap.c:125 [inline]
scan_bitmap_block+0x48a/0xde0 fs/reiserfs/bitmap.c:203
scan_bitmap fs/reiserfs/bitmap.c:408 [inline]
allocate_without_wrapping_disk fs/reiserfs/bitmap.c:1161 [inline]
blocknrs_and_prealloc_arrays_from_search_start fs/reiserfs/bitmap.c:1274 [inline]
reiserfs_allocate_blocknrs+0x370f/0x53c0 fs/reiserfs/bitmap.c:1375
_allocate_block fs/reiserfs/inode.c:-1 [inline]
reiserfs_get_block+0x2659/0x3ed0 fs/reiserfs/inode.c:756
__block_write_begin_int+0x566/0x1ad0 fs/buffer.c:2124
reiserfs_write_begin+0x20a/0x4c0 fs/reiserfs/inode.c:2771
generic_perform_write+0x2fb/0x5b0 mm/filemap.c:4016
generic_file_write_iter+0xaf/0x2e0 mm/filemap.c:4137
call_write_iter include/linux/fs.h:2018 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x43b/0x940 fs/read_write.c:584
ksys_write+0x147/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7efcb898ec29
<TASK>
is_block_in_journal fs/reiserfs/bitmap.c:125 [inline]
scan_bitmap_block+0x48a/0xde0 fs/reiserfs/bitmap.c:203
scan_bitmap fs/reiserfs/bitmap.c:408 [inline]
allocate_without_wrapping_disk fs/reiserfs/bitmap.c:1161 [inline]
blocknrs_and_prealloc_arrays_from_search_start fs/reiserfs/bitmap.c:1274 [inline]
reiserfs_allocate_blocknrs+0x370f/0x53c0 fs/reiserfs/bitmap.c:1375
_allocate_block fs/reiserfs/inode.c:-1 [inline]
reiserfs_get_block+0x2659/0x3ed0 fs/reiserfs/inode.c:756
__block_write_begin_int+0x566/0x1ad0 fs/buffer.c:2124
reiserfs_write_begin+0x20a/0x4c0 fs/reiserfs/inode.c:2771
generic_perform_write+0x2fb/0x5b0 mm/filemap.c:4016
generic_file_write_iter+0xaf/0x2e0 mm/filemap.c:4137
call_write_iter include/linux/fs.h:2018 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x43b/0x940 fs/read_write.c:584
ksys_write+0x147/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Code: ff ff c3 66 2e 0f 1f 84 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
RSP: 002b:00007ffca68577f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007efcb8bd5fa0 RCX: 00007efcb898ec29
RDX: 000000000208e24b RSI: 0000200000000240 RDI: 0000000000000004
RBP: 00007efcb8a11e41 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007efcb8bd5fa0 R14: 00007efcb8bd5fa0 R15: 0000000000000003
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:reiserfs_in_journal+0xa4e/0xa50 fs/reiserfs/journal.c:505
Code: 24 30 80 e2 07 80 c2 03 38 ca 0f 8c 73 fe ff ff 48 8b 7c 24 30 48 89 c3 e8 4f e1 b6 ff 48 89 d8 e9 5e fe ff ff e8 a2 95 5f ff <0f> 0b 66 0f 1f 00 55 41 57 41 56 41 55 41 54 53 50 49 89 fc 48 bd
RSP: 0018:ffffc90003237008 EFLAGS: 00010293
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:reiserfs_in_journal+0xa4e/0xa50 fs/reiserfs/journal.c:505
Code: 24 30 80 e2 07 80 c2 03 38 ca 0f 8c 73 fe ff ff 48 8b 7c 24 30 48 89 c3 e8 4f e1 b6 ff 48 89 d8 e9 5e fe ff ff e8 a2 95 5f ff <0f> 0b 66 0f 1f 00 55 41 57 41 56 41 55 41 54 53 50 49 89 fc 48 bd
RAX: ffffffff822601fe RBX: ffff88802cf14000 RCX: ffff88802c4d9e00
RDX: 0000000000000000 RSI: 0000000000000213 RDI: 0000000000000213
RBP: ffff88802cf14630 R08: ffffc90003237140 R09: 1ffff1100d787e08
R10: dffffc0000000000 R11: ffffed100d787e09 R12: ffffc9000346b048
R13: ffffc9000346b050 R14: dffffc0000000000 R15: 0000000000000213
FS: 0000555579aa5500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd1e5e36000 CR3: 000000002597d000 CR4: 00000000003506f0
---
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