io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+d6218cb2fae0b2411e9d@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk, hdanton@sina.com,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
	ming.lei@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in __percpu_ref_exit (2)
Date: Mon, 19 Apr 2021 08:02:04 -0700	[thread overview]
Message-ID: <000000000000dc7eb305c0549c1a@google.com> (raw)
In-Reply-To: <c12b0100-50be-907b-503d-3aa00223194c@gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+d6218cb2fae0b2411e9d@syzkaller.appspotmail.com

Tested on:

commit:         75c4021a io_uring: check register restriction afore quiesce
git tree:       git://git.kernel.dk/linux-block for-5.13/io_uring
kernel config:  https://syzkaller.appspot.com/x/.config?x=1dfd9a1e63100694
dashboard link: https://syzkaller.appspot.com/bug?extid=d6218cb2fae0b2411e9d
compiler:       

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2021-04-19 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 11:58 [syzbot] WARNING in __percpu_ref_exit (2) syzbot
2021-03-15 12:18 ` Pavel Begunkov
     [not found] ` <20210318083340.1900-1-hdanton@sina.com>
2021-03-18 14:28   ` Pavel Begunkov
2021-04-18 19:30 ` syzbot
2021-04-19 12:07   ` Pavel Begunkov
2021-04-19 15:02     ` syzbot [this message]
2021-09-13  9:22 ` syzbot
2021-09-16  7:59   ` Dmitry Vyukov
2021-09-16 13:17     ` Pavel Begunkov
2021-09-16 14:01       ` syzbot
2021-09-20  8:15         ` 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=000000000000dc7eb305c0549c1a@google.com \
    --to=syzbot+d6218cb2fae0b2411e9d@syzkaller.appspotmail.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=hdanton@sina.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --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 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).