From: Pavel Begunkov <asml.silence@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+d6218cb2fae0b2411e9d@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, coreteam@netfilter.org, davem@davemloft.net,
dsahern@kernel.org, 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 14:17:46 +0100 [thread overview]
Message-ID: <0ddad8d7-03c2-4432-64a4-b717bbc90fb4@gmail.com> (raw)
In-Reply-To: <CACT4Y+avszKiyXYBTRus9DqeSUoGrWC8d2uEiJN3z=oYQSdz0g@mail.gmail.com>
On 9/16/21 8:59 AM, Dmitry Vyukov wrote:
> On Mon, 13 Sept 2021 at 11:22, syzbot
> <syzbot+d6218cb2fae0b2411e9d@syzkaller.appspotmail.com> wrote:
>>
>> syzbot suspects this issue was fixed by commit:
>>
>> commit 43016d02cf6e46edfc4696452251d34bba0c0435
>> Author: Florian Westphal <fw@strlen.de>
>> Date: Mon May 3 11:51:15 2021 +0000
>>
>> netfilter: arptables: use pernet ops struct during unregister
>>
>> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10acd273300000
>> start commit: c98ff1d013d2 Merge tag 'scsi-fixes' of git://git.kernel.or..
>> git tree: upstream
>> kernel config: https://syzkaller.appspot.com/x/.config?x=1c70e618af4c2e92
>> dashboard link: https://syzkaller.appspot.com/bug?extid=d6218cb2fae0b2411e9d
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=145cb2b6d00000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=157b72b1d00000
>>
>> If the result looks correct, please mark the issue as fixed by replying with:
>>
>> #syz fix: netfilter: arptables: use pernet ops struct during unregister
>>
>> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
> I guess this is a wrong commit and it was fixed by something in io_uring.
> Searching for refcount fixes I see
> a298232ee6b9a1d5d732aa497ff8be0d45b5bd82 "io_uring: fix link timeout
> refs".
> Pavel, does it look right to you?
I don't remember to be honest, if the dates fit, it can pretty well be it.
Let's test one thing to be sure it hasn't been shut just by coincidence.
#syz test: https://github.com/isilence/linux.git syz_test_quiesce_files
--
Pavel Begunkov
next prev parent reply other threads:[~2021-09-16 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 11:58 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
2021-09-13 9:22 ` syzbot
2021-09-16 7:59 ` Dmitry Vyukov
2021-09-16 13:17 ` Pavel Begunkov [this message]
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=0ddad8d7-03c2-4432-64a4-b717bbc90fb4@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=dvyukov@google.com \
--cc=fw@strlen.de \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzbot+d6218cb2fae0b2411e9d@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yoshfuji@linux-ipv6.org \
/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
Powered by JetHome