From: Tigran Aivazian <aivazian.tigran@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+54b10a5da9e59f1ed979@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: WARNING: filesystem loop0 was created with 512 inodes, the real maximum is 511, mounting anyway
Date: Mon, 28 Sep 2020 09:23:40 +0100 [thread overview]
Message-ID: <CAK+_RLmGVr=ngG+Tqum==sDLEeEEz11su92EnoQVG6Zgm2gxzg@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+Zc5W9kGUqjVkkuUTBEsLk-1k3eKF5F78-LioWF6XTR0w@mail.gmail.com>
Hello Dmitry,
On Mon, 28 Sep 2020 at 08:51, Dmitry Vyukov <dvyukov@google.com> wrote:
> On Mon, Sep 28, 2020 at 9:48 AM syzbot
> <syzbot+54b10a5da9e59f1ed979@syzkaller.appspotmail.com> wrote:
> > BFS-fs: bfs_fill_super(): WARNING: filesystem loop0 was created with 512 inodes, the real maximum is 511, mounting anyway
>
> This looks like a BFS issue. +BFS maintainers.
No, this is not an issue. In the latest change to BFS I added the
following comment to the header fs/bfs/bfs.h, which explains it:
/* In theory BFS supports up to 512 inodes, numbered from 2 (for /) up
to 513 inclusive.
In actual fact, attempting to create the 512th inode (i.e. inode
No. 513 or file No. 511)
will fail with ENOSPC in bfs_add_entry(): the root directory cannot
contain so many entries, counting '..'.
So, mkfs.bfs(8) should really limit its -N option to 511 and not
512. For now, we just print a warning
if a filesystem is mounted with such "impossible to fill up" number
of inodes */
Kind regards,
Tigran
next prev parent reply other threads:[~2020-09-28 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 7:48 WARNING: filesystem loop0 was created with 512 inodes, the real maximum is 511, mounting anyway syzbot
2020-09-28 7:51 ` Dmitry Vyukov
2020-09-28 8:23 ` Tigran Aivazian [this message]
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='CAK+_RLmGVr=ngG+Tqum==sDLEeEEz11su92EnoQVG6Zgm2gxzg@mail.gmail.com' \
--to=aivazian.tigran@gmail.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+54b10a5da9e59f1ed979@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).