Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <000000000000c6dc0305f75b4d74@google.com> <ZE4L+x5SjT3+elhh@mit.edu>
In-Reply-To: <ZE4L+x5SjT3+elhh@mit.edu>
From:   Aleksandr Nogikh <nogikh@google.com>
Date:   Tue, 2 May 2023 22:08:44 +0200
Message-ID: <CANp29Y4cg6HB0dw_4mO05ibiAv2GkdnMksQozSGiBrwan9JvYA@mail.gmail.com>
Subject: Re: [syzbot] [fs?] INFO: task hung in eventpoll_release_file
To:     "Theodore Ts'o" <tytso@mit.edu>
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
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi Ted,

On Sun, Apr 30, 2023 at 8:34=E2=80=AFAM 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=3DCrashReport&x=3D171abfaac80000

--=20
Aleksandr
>
>                                                 - Ted
>
> --