From: syzbot <syzbot+02c44c7f92e70a73730a@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 anywa
Date: Mon, 07 Dec 2020 04:53:10 -0800 [thread overview]
Message-ID: <000000000000fbb4f505b5df4eea@google.com> (raw)
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@syzkaller.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@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-12-07 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 12:53 syzbot [this message]
2020-12-07 13:09 ` WARNING: filesystem loop0 was created with 512 inodes, the real maximum is 511, mounting anywa 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=000000000000fbb4f505b5df4eea@google.com \
--to=syzbot+02c44c7f92e70a73730a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.