From: syzbot <syzbot+8c4a14856e657b43487c@syzkaller.appspotmail.com>
To: axboe@kernel.dk, ebiggers@kernel.org, hdanton@sina.com,
io-uring@vger.kernel.org, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
paulmck@kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: WARNING in percpu_ref_exit (2)
Date: Tue, 10 Nov 2020 19:09:05 -0800 [thread overview]
Message-ID: <00000000000036d7e005b3cc1e79@google.com> (raw)
In-Reply-To: <000000000000b09d8c059a3240be@google.com>
syzbot suspects this issue was fixed by commit:
commit c1e2148f8ecb26863b899d402a823dab8e26efd1
Author: Jens Axboe <axboe@kernel.dk>
Date: Wed Mar 4 14:25:50 2020 +0000
io_uring: free fixed_file_data after RCU grace period
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=161ea46e500000
start commit: 63849c8f Merge tag 'linux-kselftest-5.6-rc5' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4527d1e2fb19fd5c
dashboard link: https://syzkaller.appspot.com/bug?extid=8c4a14856e657b43487c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c30061e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1251b731e00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: io_uring: free fixed_file_data after RCU grace period
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-11-11 3:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 8:05 WARNING in percpu_ref_exit (2) syzbot
2019-12-21 8:43 ` syzbot
2020-11-11 3:09 ` syzbot [this message]
2020-11-11 13:30 ` Dmitry Vyukov
[not found] <20191221134330.7376-1-hdanton@sina.com>
2019-12-21 14:02 ` Jens Axboe
2020-06-28 15:48 ` Eric Biggers
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=00000000000036d7e005b3cc1e79@google.com \
--to=syzbot+8c4a14856e657b43487c@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=ebiggers@kernel.org \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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.