All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+@syzkaller.appspotmail.com>
To: "'Dmitry Vyukov' via syzkaller-bugs"  <syzkaller-bugs@googlegroups.com>
Cc: akpm@linux-foundation.org, dbueso@suse.de, jbaron@akamai.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	paulmck@linux.vnet.ibm.com, rpenyaev@suse.de,
	sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: Re: WARNING in ep_poll_callback
Date: Mon, 11 Mar 2019 09:36:25 -0700	[thread overview]
Message-ID: <00000000000073a5740583d42c1e@google.com> (raw)
In-Reply-To: <CACT4Y+YLZYJ21Bao5HVAvXhvb9PQ41J-4RvtkZZEMF38qtkxHg@mail.gmail.com>

> 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.

> 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).


> --
> You received this message because you are subscribed to the Google  
> Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit  
> https://groups.google.com/d/msgid/syzkaller-bugs/CACT4Y%2BYLZYJ21Bao5HVAvXhvb9PQ41J-4RvtkZZEMF38qtkxHg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2019-03-11 16:36 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
2019-03-11 16:36         ` Dmitry Vyukov
2019-03-11 16:36           ` syzbot [this message]
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=00000000000073a5740583d42c1e@google.com \
    --to=syzbot+@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dbueso@suse.de \
    --cc=jbaron@akamai.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rpenyaev@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.