syzbot


WARNING: filesystem loop3 was created with 512 inodes, the real maximum is 511, mounting anyway

Status: fixed on 2021/03/10 01:48
Reported-by: syzbot+293714df4fe354fae488@syzkaller.appspotmail.com
Fix commit: dc889b8d4a81 bfs: don't use WARNING: string when it's just info.
First crash: 1303d, last: 1232d
Discussions (1)
Title Replies (including bot) Last reply
WARNING: filesystem loop3 was created with 512 inodes, the real maximum is 511, mounting anyway 1 (2) 2020/12/07 13:11

Sample crash report:
BFS-fs: bfs_fill_super(): loop3 is unclean, continuing
BFS-fs: bfs_fill_super(): WARNING: filesystem loop3 was created with 512 inodes, the real maximum is 511, mounting anyway
BFS-fs: bfs_fill_super(): Last block not available on loop3: 1507328
BFS-fs: bfs_fill_super(): loop3 is unclean, continuing
BFS-fs: bfs_fill_super(): WARNING: filesystem loop3 was created with 512 inodes, the real maximum is 511, mounting anyway
BFS-fs: bfs_fill_super(): Last block not available on loop3: 1507328

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/12/01 04:32 upstream b65054597872 b3a34598 .config console log report info ci-upstream-kasan-gce-smack-root
2020/11/16 22:45 upstream 09162bc32c88 1bf9a662 .config console log report info ci-upstream-kasan-gce-root
2020/09/21 21:44 upstream 98477740630f 9e1fa68e .config console log report info ci-qemu-upstream
* Struck through repros no longer work on HEAD.