From: syzbot <syzbot+54b10a5da9e59f1ed979@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: WARNING: filesystem loop0 was created with 512 inodes, the real maximum is 511, mounting anyway
Date: Mon, 28 Sep 2020 00:48:17 -0700 [thread overview]
Message-ID: <000000000000b7551005b05ae3b8@google.com> (raw)
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=12e98c8d900000
kernel config: https://syzkaller.appspot.com/x/.config?x=5f4c828c9e3cef97
dashboard link: https://syzkaller.appspot.com/bug?extid=54b10a5da9e59f1ed979
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150881c3900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1605b927900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+54b10a5da9e59f1ed979@syzkaller.appspotmail.com
BFS-fs: bfs_fill_super(): WARNING: filesystem loop0 was created with 512 inodes, the real maximum is 511, mounting anyway
---
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@googlegroups.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
next reply other threads:[~2020-09-28 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 7:48 syzbot [this message]
2020-09-28 7:51 ` WARNING: filesystem loop0 was created with 512 inodes, the real maximum is 511, mounting anyway Dmitry Vyukov
2020-09-28 8:23 ` Tigran Aivazian
2020-09-28 8:29 ` Dmitry Vyukov
2020-09-28 9:08 ` Tigran Aivazian
2020-12-07 13:13 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000b7551005b05ae3b8@google.com \
--to=syzbot+54b10a5da9e59f1ed979@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).