From: syzbot <syzbot+9743a41f74f00e50fc77@syzkaller.appspotmail.com>
To: tytso@mit.edu
Cc: hch@infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [sysv?] [vfs?] WARNING in invalidate_bh_lru
Date: Sat, 29 Apr 2023 23:40:42 -0700 [thread overview]
Message-ID: <00000000000031682b05fa87fcbe@google.com> (raw)
In-Reply-To: <ZE4NVo6rTOeGQdK+@mit.edu>
> On Wed, Dec 21, 2022 at 06:57:38PM -0800, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: a5541c0811a0 Merge branch 'for-next/core' into for-kernelci
>> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
>> console output: https://syzkaller.appspot.com/x/log.txt?x=1560b830480000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=cbd4e584773e9397
>> dashboard link: https://syzkaller.appspot.com/bug?extid=9743a41f74f00e50fc77
>> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
>> userspace arch: arm64
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e320b3880000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=147c0577880000
>
> #syz set subsystems: sysv, udf
The specified label value is incorrect.
"sysv" is not among the allowed values.
Please use one of the supported label values.
The following labels are suported:
no-reminders, prio: {low, normal, high}, subsystems: {.. see below ..}
The list of subsystems: https://syzkaller.appspot.com/upstream/subsystems?all=true
>
> There are two reproducers, one that mounts a sysv file system, and the
> other which mounts a udf file system. There is no mention of ext4 in
> the stack trace, and yet syzbot has assigned this to the ext4
> subsystem for some unknown reason.
>
> - Ted
next prev parent reply other threads:[~2023-04-30 6:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 2:57 [syzbot] [sysv?] [vfs?] WARNING in invalidate_bh_lru syzbot
2023-04-30 6:40 ` Theodore Ts'o
2023-04-30 6:40 ` syzbot [this message]
2023-04-30 16:12 ` Theodore Ts'o
2023-05-01 9:18 ` Aleksandr Nogikh
2023-05-03 4:31 ` Theodore Ts'o
2023-06-03 17:35 ` [syzbot] [udf] " syzbot
2024-03-02 12:14 ` syzbot
2024-03-11 9:32 ` Jan Kara
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=00000000000031682b05fa87fcbe@google.com \
--to=syzbot+9743a41f74f00e50fc77@syzkaller.appspotmail.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).