From: syzbot <syzbot+f2aca089e6f77e5acd46@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk, haoxu@linux.alibaba.com,
hdanton@sina.com, io-uring@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] WARNING in io_poll_double_wake
Date: Mon, 30 Aug 2021 04:34:12 -0700 [thread overview]
Message-ID: <00000000000053c98205cac53625@google.com> (raw)
In-Reply-To: <00000000000022acbf05c06d9f0d@google.com>
syzbot suspects this issue was fixed by commit:
commit a890d01e4ee016978776e45340e521b3bbbdf41f
Author: Hao Xu <haoxu@linux.alibaba.com>
Date: Wed Jul 28 03:03:22 2021 +0000
io_uring: fix poll requests leaking second poll entries
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15d8819d300000
start commit: 98f7fdced2e0 Merge tag 'irq-urgent-2021-07-11' of git://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=139b08f9b7481d26
dashboard link: https://syzkaller.appspot.com/bug?extid=f2aca089e6f77e5acd46
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11650180300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1510c6b0300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: io_uring: fix poll requests leaking second poll entries
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-08-30 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 20:52 [syzbot] WARNING in io_poll_double_wake syzbot
2021-08-30 11:34 ` syzbot [this message]
2021-09-20 8:16 ` Dmitry Vyukov
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=00000000000053c98205cac53625@google.com \
--to=syzbot+f2aca089e6f77e5acd46@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=haoxu@linux.alibaba.com \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.