All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+3fd34060f26e766536ff@syzkaller.appspotmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	syzkaller <syzkaller@googlegroups.com>
Subject: Re: WARNING: filesystem loop5 was created with 512 inodes, the real maximum is 511, mounting anyway
Date: Mon, 30 Nov 2020 17:03:05 -0800	[thread overview]
Message-ID: <8d5ec04c-4646-3b70-6f6c-ea989e6c2c59@infradead.org> (raw)
In-Reply-To: <CACT4Y+YkH042G=+ErWY+dRLs5H0i1ao1xnSeHvGx8x=dn5KH1A@mail.gmail.com>

On 11/30/20 12:43 AM, Dmitry Vyukov wrote:
> On Mon, Nov 30, 2020 at 5:29 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> On 11/27/20 4:32 AM, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following issue on:
>>>
>>> HEAD commit:    418baf2c Linux 5.10-rc5
>>> git tree:       upstream
>>> console output: https://syzkaller.appspot.com/x/log.txt?x=171555b9500000
>>> kernel config:  https://syzkaller.appspot.com/x/.config?x=b81aff78c272da44
>>> dashboard link: https://syzkaller.appspot.com/bug?extid=3fd34060f26e766536ff
>>> 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+3fd34060f26e766536ff@syzkaller.appspotmail.com
>>>
>>> BFS-fs: bfs_fill_super(): loop5 is unclean, continuing
>>> BFS-fs: bfs_fill_super(): WARNING: filesystem loop5 was created with 512 inodes, the real maximum is 511, mounting anyway
>>> BFS-fs: bfs_fill_super(): Last block not available on loop5: 120
>>> BFS-fs: bfs_fill_super(): loop5 is unclean, continuing
>>> BFS-fs: bfs_fill_super(): WARNING: filesystem loop5 was created with 512 inodes, the real maximum is 511, mounting anyway
>>> BFS-fs: bfs_fill_super(): Last block not available on loop5: 120
>>>
>>>
>>> ---
>>> 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.
>>>
>>
>> Hi,
>> Can you provide the BFS image file that is being mounted?
>> (./file0 I think.)
>>
>> --
>> ~Randy
> 
> 
> Hi Randy,
> 
> I see this bug was reported with a reproducer:
> https://syzkaller.appspot.com/bug?id=a32ebd5db2f7c957b82cf54b97bdecf367bf0421
> I assume it's a dup of this one.

Sure, looks the same.

> If you need the image itself, you can dump it to a file in the C
> reproducer inside of syz_mount_image before mount call.

Yes, got that.

What outcome or result are you looking for here?
Or what do you see as the problem?


thanks.
-- 
~Randy


  reply	other threads:[~2020-12-01  1:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 12:32 WARNING: filesystem loop5 was created with 512 inodes, the real maximum is 511, mounting anyway syzbot
2020-11-30  4:29 ` Randy Dunlap
2020-11-30  8:43   ` Dmitry Vyukov
2020-12-01  1:03     ` Randy Dunlap [this message]
2020-12-01  7:47       ` Dmitry Vyukov
2020-12-01 21:17         ` Randy Dunlap
2020-12-02  7:59           ` Dmitry Vyukov
2020-12-03  4:15           ` Randy Dunlap
2020-12-03 12:55             ` Dmitry Vyukov
2020-12-03 12:56               ` 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=8d5ec04c-4646-3b70-6f6c-ea989e6c2c59@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+3fd34060f26e766536ff@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=syzkaller@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.