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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <000000000000c2f72c05b498f9bd@google.com>
Date:   Fri, 20 Nov 2020 23:33:21 -0800
From:   syzbot <syzbot+ae3ff0bb2a0133596a5b@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: WARNING: filesystem loop2 was created with 512 inodes, the real
 maximum is 511, mounting anyway

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+ae3ff0bb2a0133596a5b@...kaller.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 syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.