[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANp29Y4cg6HB0dw_4mO05ibiAv2GkdnMksQozSGiBrwan9JvYA@mail.gmail.com>
Date: Tue, 2 May 2023 22:08:44 +0200
From: Aleksandr Nogikh <nogikh@...gle.com>
To: "Theodore Ts'o" <tytso@....edu>
Cc: syzbot <syzbot+e6dab35a08df7f7aa260@...kaller.appspotmail.com>,
brauner@...nel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
viro@...iv.linux.org.uk
Subject: Re: [syzbot] [fs?] INFO: task hung in eventpoll_release_file
Hi Ted,
On Sun, Apr 30, 2023 at 8:34 AM Theodore Ts'o <tytso@....edu> wrote:
>
> #syz set subsystem: fs
>
> This somehow got tagged with the ext4 label, and not the fs label.
> (And this is not the first one I've noticed). I'm beginning to
> suspect there may have been some syzbot database hiccup? Anyway,
> fixing...
FWIW one of this bug's crashes was attributed to ext4 [1] and syzbot's
logic in this case was to prefer a more specific subsystem (ext4) to a
more generic one (fs), even if it's not mentioned in the majority of
crashes.
[1] https://syzkaller.appspot.com/text?tag=CrashReport&x=171abfaac80000
--
Aleksandr
>
> - Ted
>
> --
Powered by blists - more mailing lists