From: Roman Penyaev <rpenyaev@suse.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
dbueso@suse.de, Jason Baron <jbaron@akamai.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: WARNING in ep_poll_callback
Date: Mon, 11 Mar 2019 14:53:13 +0100 [thread overview]
Message-ID: <531016fbc6fee2f1a1c386b0daeba867@suse.de> (raw)
In-Reply-To: <CACT4Y+ZXBhNamhTYVW_9y_yUWRE+=rO8vdBF=m40kjqJQGY-gQ@mail.gmail.com>
On 2019-03-11 14:45, Dmitry Vyukov wrote:
> On Mon, Mar 11, 2019 at 2:37 PM Roman Penyaev <rpenyaev@suse.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
next prev parent reply other threads:[~2019-03-11 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 5:59 WARNING in ep_poll_callback syzbot
2019-01-08 6:00 ` Dmitry Vyukov
2019-01-08 10:05 ` Roman Penyaev
2019-01-08 6:21 ` syzbot
2019-03-11 13:14 ` syzbot
2019-03-11 13:37 ` Roman Penyaev
2019-03-11 13:45 ` Dmitry Vyukov
2019-03-11 13:53 ` Roman Penyaev [this message]
2019-03-11 16:36 ` Dmitry Vyukov
2019-03-11 16:36 ` syzbot
2019-03-11 16:37 ` Dmitry Vyukov
2019-03-11 17:22 ` Roman Penyaev
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=531016fbc6fee2f1a1c386b0daeba867@suse.de \
--to=rpenyaev@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dbueso@suse.de \
--cc=dvyukov@google.com \
--cc=jbaron@akamai.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--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