From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+ae3ff0bb2a0133596a5b@syzkaller.appspotmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: WARNING: filesystem loop2 was created with 512 inodes, the real maximum is 511, mounting anyway
Date: Mon, 7 Dec 2020 14:11:57 +0100 [thread overview]
Message-ID: <CACT4Y+Z0NYJ7tk1Xx+b8ox_9k_ZXSimeMcPsJawn3QFpN1-SCQ@mail.gmail.com> (raw)
In-Reply-To: <000000000000c2f72c05b498f9bd@google.com>
#syz fix: bfs: don't use WARNING: string when it's just info.
On Sat, Nov 21, 2020 at 8:33 AM syzbot
<syzbot+ae3ff0bb2a0133596a5b@syzkaller.appspotmail.com> wrote:
>
> 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@syzkaller.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@googlegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/000000000000c2f72c05b498f9bd%40google.com.
prev parent reply other threads:[~2020-12-07 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 7:33 WARNING: filesystem loop2 was created with 512 inodes, the real maximum is 511, mounting anyway syzbot
2020-12-07 13:11 ` Dmitry Vyukov [this message]
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=CACT4Y+Z0NYJ7tk1Xx+b8ox_9k_ZXSimeMcPsJawn3QFpN1-SCQ@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+ae3ff0bb2a0133596a5b@syzkaller.appspotmail.com \
--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).