linux-kernel - Re: WARNING in ep_poll

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 11 Mar 2019 17:36:12 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Roman Penyaev <rpenyaev@...e.de>
Cc:     Andrew Morton <akpm@...ux-foundation.org>, dbueso@...e.de,
        Jason Baron <jbaron@...mai.com>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Paul McKenney <paulmck@...ux.vnet.ibm.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Al Viro <viro@...iv.linux.org.uk>
Subject: Re: WARNING in ep_poll_callback

On Mon, Mar 11, 2019 at 2:53 PM Roman Penyaev <rpenyaev@...e.de> wrote:
>
> On 2019-03-11 14:45, Dmitry Vyukov wrote:
> > On Mon, Mar 11, 2019 at 2:37 PM Roman Penyaev <rpenyaev@...e.de> wrote:
> >>
> >> Hi Andrew,
> >>
> >> I thought "epoll: loosen irq safety in ep_poll_callback()" patch was
> >> removed from your tree, at least I got a notification on 9th of
> >> january,
> >> also I do not see it in the linux-next tree.
> >>
> >> Should I ignore this syzbot message?
> >
> > If this was resolved we need to communicate it to syzbot one way or the
> > other.
> > Since it was in linux-next, it won't even be able to do fix bisection.
> > So the bug will be open forever otherwise.
>
> Bug was fixed (commit was simply dropped).  How can I tell syzbot to
> shut up
> and to resolve the issue?

Hi Roman,

The docs are at:

> See https://goo.gl/tpsmEJ for more information about syzbot.

There is no official support for bugs fixed not by commit merges.
Linux-next creates various interesting corner-cases for the process.
Let's go with this option for now:

#syz invalid