Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date:   Mon, 11 Mar 2019 18:22:14 +0100
From:   Roman Penyaev <rpenyaev@suse.de>
To:     Dmitry Vyukov <dvyukov@google.com>
Cc:     syzbot <syzbot+aea82bf9ee6ffd9a79d9@syzkaller.appspotmail.com>,
        'Dmitry Vyukov' via syzkaller-bugs 
        <syzkaller-bugs@googlegroups.com>,
        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>,
        Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: WARNING in ep_poll_callback
In-Reply-To: <CACT4Y+aHBMnOHQaTphgGwW8mZbDeHCu+Ce8zXki1ntdEbTPJqQ@mail.gmail.com>
References: <CACT4Y+YLZYJ21Bao5HVAvXhvb9PQ41J-4RvtkZZEMF38qtkxHg@mail.gmail.com>
 <00000000000073a5740583d42c1e@google.com>
 <CACT4Y+aHBMnOHQaTphgGwW8mZbDeHCu+Ce8zXki1ntdEbTPJqQ@mail.gmail.com>
Message-ID: <340d29d33c1adfd55fe8b1ad48674708@suse.de>
User-Agent: Roundcube Webmail
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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