io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+6338dcebf269a590b668@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
	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: INFO: task hung in io_uring_flush
Date: Wed, 16 Sep 2020 18:42:08 -0700	[thread overview]
Message-ID: <00000000000004632a05af787ebf@google.com> (raw)
In-Reply-To: <000000000000391eaf05ac87b74d@google.com>

syzbot suspects this issue was fixed by commit:

commit b7ddce3cbf010edbfac6c6d8cc708560a7bcd7a4
Author: Pavel Begunkov <asml.silence@gmail.com>
Date:   Sat Sep 5 21:45:14 2020 +0000

    io_uring: fix cancel of deferred reqs with ->files

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=173d9b0d900000
start commit:   9123e3a7 Linux 5.9-rc1
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=3d400a47d1416652
dashboard link: https://syzkaller.appspot.com/bug?extid=6338dcebf269a590b668
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1573f116900000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=144d3072900000

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

#syz fix: io_uring: fix cancel of deferred reqs with ->files

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

  parent reply	other threads:[~2020-09-17  1:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 15:36 INFO: task hung in io_uring_flush syzbot
2020-08-10 16:04 ` syzbot
2020-08-10 16:08   ` Pavel Begunkov
2020-08-10 18:11     ` Jens Axboe
2020-09-17  1:42 ` syzbot [this message]
2020-11-11 11:21   ` 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=00000000000004632a05af787ebf@google.com \
    --to=syzbot+6338dcebf269a590b668@syzkaller.appspotmail.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).