Hi Ted, On Sun, Apr 30, 2023 at 8:40 AM Theodore Ts'o <tytso@xxxxxxx> wrote: > > 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 > > 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. In this particular case, there were two ext4-related crashes as well: https://syzkaller.appspot.com/text?tag=CrashReport&x=14c7dd1b480000 https://syzkaller.appspot.com/text?tag=CrashReport&x=1153a07f480000 I think syzbot picked a too generic frame as a bug title and it just got confused by crashes belonging to different filesystems. Maybe we need to display subsystems for individual crashes as well, so that it's easier for a human to understand what's going on.. -- Aleksandr > > - Ted > > -- > You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@xxxxxxxxxxxxxxxx. > To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/ZE4NVo6rTOeGQdK%2B%40mit.edu.
