Messages in this thread | | | Date | Mon, 11 Mar 2019 18:22:14 +0100 | From | Roman Penyaev <> | Subject | Re: WARNING in ep_poll_callback |
| |
On 2019-03-11 17:37, Dmitry Vyukov wrote: > On Mon, Mar 11, 2019 at 5:36 PM syzbot > <syzbot+@syzkaller.appspotmail.com> wrote: >> >> > On Mon, Mar 11, 2019 at 2:53 PM Roman Penyaev <rpenyaev@suse.de> wrote: >> >> >> 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? >> >> > Hi Roman, >> >> > The docs are at: >> >> >> See https://goo.gl/tpsmEJ for more information about syzbot.
Thanks! Will read.
>> >> > 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 >> >> I see the command but can't find the corresponding bug. >> Please resend the email to syzbot+HASH@syzkaller.appspotmail.com >> address >> that is the sender of the bug report (also present in the Reported-by >> tag). > > +syzbot email > > Please don't drop bug reporter email from CC.
Did not know. Thanks for your help!
-- Roman
| |