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

[Randy Dunlap]

On 11/27/20 4:32 AM, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    418baf2c Linux 5.10-rc5
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=171555b9500000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=b81aff78c272da44
> dashboard link: https://syzkaller.appspot.com/bug?extid=3fd34060f26e766536ff
> 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+3fd34060f26e766536ff@xxxxxxxxxxxxxxxxxxxxxxxxx
> 
> BFS-fs: bfs_fill_super(): loop5 is unclean, continuing
> BFS-fs: bfs_fill_super(): WARNING: filesystem loop5 was created with 512 inodes, the real maximum is 511, mounting anyway
> BFS-fs: bfs_fill_super(): Last block not available on loop5: 120
> BFS-fs: bfs_fill_super(): loop5 is unclean, continuing
> BFS-fs: bfs_fill_super(): WARNING: filesystem loop5 was created with 512 inodes, the real maximum is 511, mounting anyway
> BFS-fs: bfs_fill_super(): Last block not available on loop5: 120
> 
> 
> ---
> 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 syzkaller@xxxxxxxxxxxxxxxx.
> 
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> 

Hi,
Can you provide the BFS image file that is being mounted?
(./file0 I think.)

-- 
~Randy