From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+293714df4fe354fae488@syzkaller.appspotmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: WARNING: filesystem loop3 was created with 512 inodes, the real maximum is 511, mounting anyway
Date: Mon, 7 Dec 2020 14:11:49 +0100 [thread overview]
Message-ID: <CACT4Y+aU2T7CCx_EmGG6aL_7WMiHy01cSScZu4gM2C3gvcoROg@mail.gmail.com> (raw)
In-Reply-To: <00000000000028201305b00bfdba@google.com>
#syz fix: bfs: don't use WARNING: string when it's just info.
On Thu, Sep 24, 2020 at 11:40 AM syzbot
<syzbot+293714df4fe354fae488@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 98477740 Merge branch 'rcu/urgent' of git://git.kernel.org..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15964ec3900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=6f192552d75898a1
> dashboard link: https://syzkaller.appspot.com/bug?extid=293714df4fe354fae488
> compiler: gcc (GCC) 10.1.0-syz 20200507
>
> 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+293714df4fe354fae488@syzkaller.appspotmail.com
>
> BFS-fs: bfs_fill_super(): WARNING: filesystem loop3 was created with 512 inodes, the real maximum is 511, mounting anyway
> BFS-fs: bfs_fill_super(): Inode 0x00000002 corrupted on loop3
>
>
> ---
> 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/00000000000028201305b00bfdba%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-09-24 9:40 WARNING: filesystem loop3 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+aU2T7CCx_EmGG6aL_7WMiHy01cSScZu4gM2C3gvcoROg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+293714df4fe354fae488@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).