linux-kernel - Re: Re: WARNING in ep_poll

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <00000000000073a5740583d42c1e@google.com>
Date:   Mon, 11 Mar 2019 09:36:25 -0700
From:   syzbot <syzbot+@...kaller.appspotmail.com>
To:     "'Dmitry Vyukov' via syzkaller-bugs" 
        <syzkaller-bugs@...glegroups.com>
Cc:     akpm@...ux-foundation.org, dbueso@...e.de, jbaron@...mai.com,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        paulmck@...ux.vnet.ibm.com, rpenyaev@...e.de, sfr@...b.auug.org.au,
        syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk
Subject: Re: Re: WARNING in ep_poll_callback

> On Mon, Mar 11, 2019 at 2:53 PM Roman Penyaev <rpenyaev@...e.de> wrote:

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

> 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@...kaller.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@...glegroups.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.