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

6 views
Skip to first unread message

syzbot

unread,
Nov 21, 2020, 2:33:22 AM11/21/20
to linux-...@vger.kernel.org, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 09162bc3 Linux 5.10-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16e9a486500000
kernel config: https://syzkaller.appspot.com/x/.config?x=e93bbe4ce29223b
dashboard link: https://syzkaller.appspot.com/bug?extid=ae3ff0bb2a0133596a5b
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project.git ca2dcbd030eadbf0aa9b660efe864ff08af6e18b)

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

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

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


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

Dmitry Vyukov

unread,
Dec 7, 2020, 8:12:12 AM12/7/20
to syzbot, LKML, syzkaller-bugs
#syz fix: bfs: don't use WARNING: string when it's just info.
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/000000000000c2f72c05b498f9bd%40google.com.
Reply all
Reply to author
Forward
0 new messages