syzbot


BUG: unable to handle kernel paging request in cleanup_bitmap_list

Status: upstream: reported C repro on 2022/10/30 13:58
Reported-by: syzbot+c4851b76249bddda4427@syzkaller.appspotmail.com
First crash: 515d, last: 402d
Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 BUG: unable to handle kernel paging request in cleanup_bitmap_list reiserfs C error 2 434d 517d 0/1 upstream: reported C repro on 2022/10/28 06:50
upstream BUG: unable to handle kernel paging request in cleanup_bitmap_list reiserfs C done error 5 1176d 2187d 0/26 closed as invalid on 2023/08/03 09:58
linux-6.1 KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list origin:upstream C 2 7h35m 310d 0/3 upstream: reported C repro on 2023/05/22 16:15
upstream KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list reiserfs C error done 100 85d 516d 26/26 fixed on 2024/02/16 19:40
linux-5.15 KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list (2) origin:upstream C 1 21d 59d 0/3 upstream: reported C repro on 2024/01/28 16:33
linux-5.15 KASAN: vmalloc-out-of-bounds Read in cleanup_bitmap_list 3 264d 340d 0/3 auto-obsoleted due to no activity on 2023/10/16 09:07
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2023/02/20 04:45 28m bisect fix linux-4.14.y job log (0) log
2023/01/21 03:54 21m bisect fix linux-4.14.y job log (0) log

Sample crash report:
REISERFS (device loop0): Using rupasov hash to sort names
REISERFS warning: reiserfs-5090 is_tree_node: node level 48 does not match to the expected one -1
REISERFS error (device loop0): vs-5150 search_by_key: invalid format found in block 0. Fsck?
REISERFS (device loop0): Remounting filesystem read-only
REISERFS error (device loop0): zam-7001 reiserfs_find_entry: io error
BUG: unable to handle kernel paging request at ffffc90005bc3000
IP: cleanup_bitmap_list.part.0+0x28f/0x5b0 fs/reiserfs/journal.c:233
PGD b60bc067 P4D b60bc067 PUD 23f832067 PMD 2358ae067 PTE 0
Oops: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 8028 Comm: syz-executor116 Not tainted 4.14.296-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
task: ffff888094c02540 task.stack: ffff8880b2908000
RIP: 0010:cleanup_bitmap_list.part.0+0x28f/0x5b0 fs/reiserfs/journal.c:233
RSP: 0018:ffff8880b290fa28 EFLAGS: 00010246
RAX: 1ffff92000b78600 RBX: dffffc0000000000 RCX: 0000000000008000
RDX: 0000000000000000 RSI: 0000000000001000 RDI: ffff88809d29f748
RBP: 0000000000001000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000200
R13: ffffc90005bc3000 R14: ffff8880b0b34240 R15: ffff88809d29f740
FS:  00007f29caa46700(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90005bc3000 CR3: 00000000ab355000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 cleanup_bitmap_list fs/reiserfs/journal.c:229 [inline]
 free_list_bitmaps fs/reiserfs/journal.c:251 [inline]
 free_journal_ram+0x162/0x5c0 fs/reiserfs/journal.c:1894
 do_journal_release fs/reiserfs/journal.c:1969 [inline]
 journal_release_error+0x72/0x90 fs/reiserfs/journal.c:1987
 reiserfs_fill_super+0xefe/0x2990 fs/reiserfs/super.c:2236
 mount_bdev+0x2b3/0x360 fs/super.c:1134
 mount_fs+0x92/0x2a0 fs/super.c:1237
 vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
 vfs_kern_mount fs/namespace.c:1036 [inline]
 do_new_mount fs/namespace.c:2572 [inline]
 do_mount+0xe65/0x2a30 fs/namespace.c:2905
 SYSC_mount fs/namespace.c:3121 [inline]
 SyS_mount+0xa8/0x120 fs/namespace.c:3098
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f29caa9b3ca
RSP: 002b:00007f29caa460e8 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f29caa9b3ca
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f29caa46100
RBP: 0000000000000004 R08: 00007f29caa46140 R09: 00007f29caa466b8
R10: 000000000020040a R11: 0000000000000286 R12: 00007f29caa46140
R13: 0000000000000008 R14: 00007f29caa46100 R15: 0000000020000600
Code: 38 00 0f 85 a2 01 00 00 48 8b 04 24 49 63 ec 48 c1 e5 03 4c 8b 68 08 49 01 ed 4c 89 e8 48 c1 e8 03 80 3c 18 00 0f 85 d2 01 00 00 <4d> 8b 6d 00 4d 85 ed 0f 84 06 ff ff ff e8 bf 63 a3 ff 49 8d 7f 
RIP: cleanup_bitmap_list.part.0+0x28f/0x5b0 fs/reiserfs/journal.c:233 RSP: ffff8880b290fa28
CR2: ffffc90005bc3000
---[ end trace 0aa2b7653cb42e73 ]---
----------------
Code disassembly (best guess):
   0:	38 00                	cmp    %al,(%rax)
   2:	0f 85 a2 01 00 00    	jne    0x1aa
   8:	48 8b 04 24          	mov    (%rsp),%rax
   c:	49 63 ec             	movslq %r12d,%rbp
   f:	48 c1 e5 03          	shl    $0x3,%rbp
  13:	4c 8b 68 08          	mov    0x8(%rax),%r13
  17:	49 01 ed             	add    %rbp,%r13
  1a:	4c 89 e8             	mov    %r13,%rax
  1d:	48 c1 e8 03          	shr    $0x3,%rax
  21:	80 3c 18 00          	cmpb   $0x0,(%rax,%rbx,1)
  25:	0f 85 d2 01 00 00    	jne    0x1fd
* 2b:	4d 8b 6d 00          	mov    0x0(%r13),%r13 <-- trapping instruction
  2f:	4d 85 ed             	test   %r13,%r13
  32:	0f 84 06 ff ff ff    	je     0xffffff3e
  38:	e8 bf 63 a3 ff       	callq  0xffa363fc
  3d:	49                   	rex.WB
  3e:	8d                   	.byte 0x8d
  3f:	7f                   	.byte 0x7f

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/10/30 13:57 linux-4.14.y 41f36d7859a7 2a71366b .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-4-14 BUG: unable to handle kernel paging request in cleanup_bitmap_list
* Struck through repros no longer work on HEAD.