syzbot


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

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

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

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/11/16 23:22 upstream 09162bc32c88 1bf9a662 .config console log report info ci-upstream-kasan-gce-root
2020/11/16 22:56 upstream 09162bc32c88 1bf9a662 .config console log report info ci-upstream-kasan-gce-selinux-root
2020/11/16 22:47 upstream 09162bc32c88 1bf9a662 .config console log report info ci-upstream-kasan-gce-smack-root
* Struck through repros no longer work on HEAD.