> 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
