All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e654d4e15e6b3b9deb53@syzkaller.appspotmail.com>
To: alaaemadhossney.ae@gmail.com, asml.silence@gmail.com,
	axboe@kernel.dk, dvyukov@google.com, hdanton@sina.com,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in io_poll_double_wake (3)
Date: Fri, 11 Feb 2022 01:13:07 -0800	[thread overview]
Message-ID: <00000000000098f75305d7ba7942@google.com> (raw)
In-Reply-To: <000000000000d5358b05bfe10354@google.com>

syzbot suspects this issue was fixed by commit:

commit aa43477b040251f451db0d844073ac00a8ab66ee
Author: Pavel Begunkov <asml.silence@gmail.com>
Date:   Wed Dec 15 22:08:48 2021 +0000

    io_uring: poll rework

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=110d0baa700000
start commit:   c9e6606c7fe9 Linux 5.16-rc8
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=4772459294eb89cc
dashboard link: https://syzkaller.appspot.com/bug?extid=e654d4e15e6b3b9deb53
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10f87335b00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15ac8a73b00000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: io_uring: poll rework

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2022-02-11  9:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 21:07 [syzbot] possible deadlock in io_poll_double_wake (3) syzbot
     [not found] ` <20210415072313.629-1-hdanton@sina.com>
2021-04-15  7:39   ` Dmitry Vyukov
2022-02-11  9:13 ` syzbot [this message]
2022-02-11 13:24   ` Jens Axboe

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=00000000000098f75305d7ba7942@google.com \
    --to=syzbot+e654d4e15e6b3b9deb53@syzkaller.appspotmail.com \
    --cc=alaaemadhossney.ae@gmail.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=dvyukov@google.com \
    --cc=hdanton@sina.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.