All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+1a219abc12077a390bc9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: WARNING: filesystem loop4 was created with 512 inodes, the real maximum is 511, mounting anyway
Date: Fri, 20 Nov 2020 23:33:21 -0800	[thread overview]
Message-ID: <000000000000bf566005b498f95f@google.com> (raw)

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=103f4fbe500000
kernel config:  https://syzkaller.appspot.com/x/.config?x=75292221eb79ace2
dashboard link: https://syzkaller.appspot.com/bug?extid=1a219abc12077a390bc9
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+1a219abc12077a390bc9@syzkaller.appspotmail.com

BFS-fs: bfs_fill_super(): WARNING: filesystem loop4 was created with 512 inodes, the real maximum is 511, mounting anyway
BFS-fs: bfs_fill_super(): Last block not available on loop4: 1507328
BFS-fs: bfs_fill_super(): WARNING: filesystem loop4 was created with 512 inodes, the real maximum is 511, mounting anyway
BFS-fs: bfs_fill_super(): Last block not available on loop4: 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.

             reply	other threads:[~2020-11-21  7:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21  7:33 syzbot [this message]
2020-12-07 13:12 ` WARNING: filesystem loop4 was created with 512 inodes, the real maximum is 511, mounting anyway 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=000000000000bf566005b498f95f@google.com \
    --to=syzbot+1a219abc12077a390bc9@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.