From: syzbot <syzbot+d6218cb2fae0b2411e9d@syzkaller•appspotmail.com>
To: asml.silence@gmail•com, axboe@kernel•dk, coreteam@netfilter•org,
davem@davemloft•net, dsahern@kernel•org, dvyukov@google•com,
fw@strlen•de, hdanton@sina•com, io-uring@vger•kernel.org,
kadlec@netfilter•org, kuba@kernel•org,
linux-kernel@vger•kernel.org, ming.lei@redhat•com,
netdev@vger•kernel.org, netfilter-devel@vger•kernel.org,
pablo@netfilter•org, syzkaller-bugs@googlegroups•com,
yoshfuji@linux-ipv6•org
Subject: Re: [syzbot] WARNING in __percpu_ref_exit (2)
Date: Thu, 16 Sep 2021 07:01:12 -0700 [thread overview]
Message-ID: <000000000000526fb105cc1d3f5b@google.com> (raw)
In-Reply-To: <0ddad8d7-03c2-4432-64a4-b717bbc90fb4@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: 5318e5b9 io_uring: quiesce files reg
git tree: https://github.com/isilence/linux.git syz_test_quiesce_files
kernel config: https://syzkaller.appspot.com/x/.config?x=f7d9f99709463d21
dashboard link: https://syzkaller.appspot.com/bug?extid=d6218cb2fae0b2411e9d
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2021-09-16 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000006e9e0705bd91f762@google.com>
2021-09-13 9:22 ` [syzbot] WARNING in __percpu_ref_exit (2) syzbot
2021-09-16 7:59 ` Dmitry Vyukov
2021-09-16 13:17 ` Pavel Begunkov
2021-09-16 14:01 ` syzbot [this message]
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=000000000000526fb105cc1d3f5b@google.com \
--to=syzbot+d6218cb2fae0b2411e9d@syzkaller$(echo .)appspotmail.com \
--cc=asml.silence@gmail$(echo .)com \
--cc=axboe@kernel$(echo .)dk \
--cc=coreteam@netfilter$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=dvyukov@google$(echo .)com \
--cc=fw@strlen$(echo .)de \
--cc=hdanton@sina$(echo .)com \
--cc=io-uring@vger$(echo .)kernel.org \
--cc=kadlec@netfilter$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=ming.lei@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=pablo@netfilter$(echo .)org \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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