From: syzbot <syzbot+bc2d90f602545761f287@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk, fgheet255t@gmail.com,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in io_wq_submit_work (2)
Date: Mon, 11 Oct 2021 13:32:07 -0700 [thread overview]
Message-ID: <00000000000061c94a05ce199f2a@google.com> (raw)
In-Reply-To: <0000000000004bda3905cb84cfc0@google.com>
syzbot suspects this issue was fixed by commit:
commit c57a91fb1ccfa203ba3e31e5a389cb04de5b0561
Author: Pavel Begunkov <asml.silence@gmail.com>
Date: Wed Sep 8 19:49:17 2021 +0000
io_uring: fix missing mb() before waitqueue_active
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=143b46bf300000
start commit: 926de8c4326c Merge tag 'acpi-5.15-rc1-3' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=37df9ef5660a8387
dashboard link: https://syzkaller.appspot.com/bug?extid=bc2d90f602545761f287
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e4357d300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1173a663300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: io_uring: fix missing mb() before waitqueue_active
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-10-11 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 0:09 [syzbot] WARNING in io_wq_submit_work (2) syzbot
2021-09-09 0:18 ` Pavel Begunkov
2021-09-09 0:56 ` syzbot
2021-09-11 13:53 ` syzbot
2021-10-11 20:32 ` syzbot [this message]
2021-10-12 10:42 ` Pavel Begunkov
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=00000000000061c94a05ce199f2a@google.com \
--to=syzbot+bc2d90f602545761f287@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=fgheet255t@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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.