From: syzbot <[email protected]>
To: [email protected], [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: Re: [syzbot] WARNING in __percpu_ref_exit (2)
Date: Mon, 13 Sep 2021 02:22:18 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
syzbot suspects this issue was fixed by commit:
commit 43016d02cf6e46edfc4696452251d34bba0c0435
Author: Florian Westphal <[email protected]>
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
next prev parent reply other threads:[~2021-09-13 9:23 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] ` <[email protected]>
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 [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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