From: syzbot <syzbot+aea82bf9ee6ffd9a79d9@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dbueso@suse.de, dvyukov@google.com,
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: WARNING in ep_poll_callback
Date: Mon, 11 Mar 2019 06:14:00 -0700 [thread overview]
Message-ID: <0000000000008f34570583d15823@google.com> (raw)
In-Reply-To: <000000000000d8bec0057eec0a92@google.com>
syzbot has bisected this bug to:
commit f92cacf118171208f62519d92502a8dd0341286d
Author: Roman Penyaev <rpenyaev@suse.de>
Date: Tue Jan 8 01:15:44 2019 +0000
epoll: loosen irq safety in ep_poll_callback()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=107ae15f200000
start commit: f92cacf1 epoll: loosen irq safety in ep_poll_callback()
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=127ae15f200000
console output: https://syzkaller.appspot.com/x/log.txt?x=147ae15f200000
kernel config: https://syzkaller.appspot.com/x/.config?x=1521b074ff5a5bdf
dashboard link: https://syzkaller.appspot.com/bug?extid=aea82bf9ee6ffd9a79d9
userspace arch: amd64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1776034b400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c2e580c00000
Reported-by: syzbot+aea82bf9ee6ffd9a79d9@syzkaller.appspotmail.com
Fixes: f92cacf1 ("epoll: loosen irq safety in ep_poll_callback()")
next prev parent reply other threads:[~2019-03-11 13:14 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 [this message]
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
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=0000000000008f34570583d15823@google.com \
--to=syzbot+aea82bf9ee6ffd9a79d9@syzkaller.appspotmail.com \
--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=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.