[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <531016fbc6fee2f1a1c386b0daeba867@suse.de>
Date: Mon, 11 Mar 2019 14:53:13 +0100
From: Roman Penyaev <rpenyaev@...e.de>
To: Dmitry Vyukov <dvyukov@...gle.com>
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 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?
--
Roman
Powered by blists - more mailing lists