#syz fix: bfs: don't use WARNING: string when it's just info.
On Mon, Sep 28, 2020 at 8:10 PM syzbot <syzbot+2435de7315366e15f...@syzkaller.appspotmail.com> wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit: c9c9e6a4 Merge tag 'trace-v5.9-rc5-2' of git://git.kernel... > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=138b09d9900000 > kernel config: https://syzkaller.appspot.com/x/.config?x=5f4c828c9e3cef97 > dashboard link: https://syzkaller.appspot.com/bug?extid=2435de7315366e15f0ca > compiler: gcc (GCC) 10.1.0-syz 20200507 > > 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+2435de7315366e15f...@syzkaller.appspotmail.com > > BFS-fs: bfs_fill_super(): WARNING: filesystem loop1 was created with 512 > inodes, the real maximum is 511, mounting anyway > BFS-fs: bfs_fill_super(): Inode 0x00000002 corrupted on loop1 > BFS-fs: bfs_fill_super(): WARNING: filesystem loop1 was created with 512 > inodes, the real maximum is 511, mounting anyway > BFS-fs: bfs_fill_super(): Inode 0x00000002 corrupted on loop1 > > > --- > 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 syzkal...@googlegroups.com. > > syzbot will keep track of this issue. See: > https://goo.gl/tpsmEJ#status for how to communicate with syzbot. > > -- > 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-bugs+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/syzkaller-bugs/0000000000006f1f5d05b06394d0%40google.com.
