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

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <000000000000fbb4f505b5df4eea@google.com>
Date:   Mon, 07 Dec 2020 04:53:10 -0800
From:   syzbot <syzbot+02c44c7f92e70a73730a@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: WARNING: filesystem loop0 was created with 512 inodes, the real
 maximum is 511, mounting anywa

Hello,

syzbot found the following issue on:

HEAD commit:    34816d20 Merge tag 'gfs2-v5.10-rc5-fixes' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=157dad07500000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b3a044ccf5b03ac4
dashboard link: https://syzkaller.appspot.com/bug?extid=02c44c7f92e70a73730a
compiler:       gcc (GCC) 10.1.0-syz 20200507
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=152b05ab500000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14fc3fad500000

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

BFS-fs: bfs_fill_super(): WARNING: filesystem loop0 was created with 512 inodes, the real maximum is 511, mounting anywa

---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches