From: "Theodore Ts'o" <tytso@mit.edu>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+e6dab35a08df7f7aa260@syzkaller.appspotmail.com>,
brauner@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] INFO: task hung in eventpoll_release_file
Date: Wed, 3 May 2023 01:04:44 -0400 [thread overview]
Message-ID: <20230503050444.GB674745@mit.edu> (raw)
In-Reply-To: <CANp29Y4cg6HB0dw_4mO05ibiAv2GkdnMksQozSGiBrwan9JvYA@mail.gmail.com>
On Tue, May 02, 2023 at 10:08:44PM +0200, Aleksandr Nogikh wrote:
> Hi Ted,
>
> On Sun, Apr 30, 2023 at 8:34 AM Theodore Ts'o <tytso@mit.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
One of the challenges is that the attribution is not necessasrily
accurate. One of the CPU's was running an ext4 workqueue task (which
was apparntly making forward progress) at the time of the crash.
It should also be noted that apparently there is a potential patch
which seems to fix the problem, and it's solely in the fs/eventpoll.c.
Unfortunately, it was not in the lore.kernel.org archives, since
apparently it wasn't cc'ed there. It's in the syzkaller-bugs Google
Groups archive, though, since Pauolo Abeni cc'ed the
syzkaller-bugs@googlegroups.com, but not the lore archive, on his
test:
https://groups.google.com/g/syzkaller-bugs/c/oiBUmGsqz_Q/m/Xi5iOeJNAgAJ
- Ted
next prev parent reply other threads:[~2023-05-03 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 21:06 [syzbot] [fs?] INFO: task hung in eventpoll_release_file syzbot
2023-04-30 6:34 ` Theodore Ts'o
2023-04-30 6:34 ` syzbot
2023-04-30 16:11 ` Theodore Ts'o
2023-05-02 20:08 ` Aleksandr Nogikh
2023-05-03 5:04 ` Theodore Ts'o [this message]
[not found] <20230321061905.2368-1-hdanton@sina.com>
2023-03-21 6:42 ` syzbot
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=20230503050444.GB674745@mit.edu \
--to=tytso@mit.edu \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzbot+e6dab35a08df7f7aa260@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--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