[v6.1] kernel BUG in reiserfs_in_journal

0 vistas
Ir al primer mensaje no leído

syzbot

no leída,
12 abr 2023, 3:31:03 p.m.12/4/23
para syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 543aff194ab6 Linux 6.1.23
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=172dec47c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=9ccbc3d5467efd1
dashboard link: https://syzkaller.appspot.com/bug?extid=4f14a27a1c6ce094fbcd
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7fe538fc87bf/disk-543aff19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8df93997601a/vmlinux-543aff19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/03ad7e3bf859/Image-543aff19.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4f14a2...@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:505!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 16327 Comm: syz-executor.2 Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : reiserfs_in_journal+0x9a4/0x9a8 fs/reiserfs/journal.c:505
lr : reiserfs_in_journal+0x9a4/0x9a8 fs/reiserfs/journal.c:505
sp : ffff800021b86b90
x29: ffff800021b86bc0 x28: ffff800021b89000 x27: 1fffe0001b3b54cf
x26: dfff800000000000 x25: ffff800021ba9318 x24: 0000000000080000
x23: ffff8000209fb048 x22: ffff8000209fb050 x21: 0000000000000213
x20: ffff0000d9daa678 x19: ffff0000d9daa000 x18: 1ffff00004371205
x17: ffff80001557d000 x16: ffff8000082ffed8 x15: 0000000000000000
x14: 0000000000000002 x13: 0000000000000002 x12: 0000000000040000
x11: 00000000000219c8 x10: ffff800027668000 x9 : ffff800008d9a2b4
x8 : 00000000000219c9 x7 : ffff800008dbbe7c x6 : 0000000000000000
x5 : 0000000000000001 x4 : ffff800021b86ce0 x3 : 0000000000000001
x2 : 0000000000000213 x1 : 0000000000000213 x0 : 0000000000000213
Call trace:
reiserfs_in_journal+0x9a4/0x9a8 fs/reiserfs/journal.c:505
is_block_in_journal fs/reiserfs/bitmap.c:125 [inline]
scan_bitmap_block+0x3b0/0xdc8 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+0x21b8/0x4260 fs/reiserfs/bitmap.c:1375
reiserfs_get_block+0x2804/0x45d8 fs/reiserfs/inode.c:756
__block_write_begin_int+0x340/0x13b4 fs/buffer.c:1991
__block_write_begin+0x7c/0xa0 fs/buffer.c:2041
reiserfs_write_begin+0x328/0x71c fs/reiserfs/inode.c:2775
generic_perform_write+0x278/0x55c mm/filemap.c:3754
__generic_file_write_iter+0x168/0x388 mm/filemap.c:3882
generic_file_write_iter+0xb8/0x2b4 mm/filemap.c:3914
call_write_iter include/linux/fs.h:2205 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x610/0x914 fs/read_write.c:584
ksys_write+0x15c/0x26c fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
Code: aa1503e0 97ef2c92 17ffff95 97dd6793 (d4210000)
---[ end trace 0000000000000000 ]---


---
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.

syzbot

no leída,
25 jun 2023, 6:08:47 a.m.25/6/23
para syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: e84a4e368abe Linux 6.1.35
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15c681af280000
kernel config: https://syzkaller.appspot.com/x/.config?x=f77b603a569f81a7
dashboard link: https://syzkaller.appspot.com/bug?extid=4f14a27a1c6ce094fbcd
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=134b6277280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14a73723280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/30886a06f234/disk-e84a4e36.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/84ab10f3c74b/vmlinux-e84a4e36.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ea73248cc405/Image-e84a4e36.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f999830bf572/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4f14a2...@syzkaller.appspotmail.com

REISERFS (device loop0): Using r5 hash to sort names
REISERFS (device loop0): using 3.5.x disk format
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:505!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4222 Comm: syz-executor196 Not tainted 6.1.35-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : reiserfs_in_journal+0x9a4/0x9a8 fs/reiserfs/journal.c:505
lr : reiserfs_in_journal+0x9a4/0x9a8 fs/reiserfs/journal.c:505
sp : ffff80001d956b90
x29: ffff80001d956bc0 x28: ffff80001d979000 x27: 1fffe0001bbf8ccf
x26: dfff800000000000 x25: ffff80001d999318 x24: 0000000000080000
x23: ffff80001d9b9048 x22: ffff80001d9b9050 x21: 0000000000000213
x20: ffff0000ddfc6678 x19: ffff0000ddfc6000 x18: 1ffff00003b2f205
x17: 0000000000000000 x16: ffff800008303574 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000002 x12: 0000000000000001
x11: ff80800008da3bc8 x10: 0000000000000000 x9 : ffff800008da3bc8
x8 : ffff0000d2e20000 x7 : ffff800008dc5790 x6 : 0000000000000000
x5 : 0000000000000001 x4 : ffff80001d956cf0 x3 : 0000000000000001
x2 : 0000000000000213 x1 : 0000000000000213 x0 : 0000000000000213
Call trace:
reiserfs_in_journal+0x9a4/0x9a8 fs/reiserfs/journal.c:505
is_block_in_journal fs/reiserfs/bitmap.c:125 [inline]
scan_bitmap_block+0x268/0xdc8 fs/reiserfs/bitmap.c:188
Code: aa1503e0 97ef2185 17ffff95 97dd5a0f (d4210000)
---[ end trace 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.
Responder a todos
Responder al autor
Reenviar
0 mensajes nuevos