From: syzbot <syzbot+35e70efb794757d7e175@syzkaller.appspotmail.com>
To: coreteam@netfilter.org, davem@davemloft.net, dsahern@kernel.org,
fw@strlen.de, johan.hedberg@gmail.com, johannes.berg@intel.com,
johannes@sipsolutions.net, kadlec@netfilter.org, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, luciano.coelho@intel.com,
marcel@holtmann.org, 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 cancel_delayed_work
Date: Tue, 08 Jun 2021 13:17:05 -0700 [thread overview]
Message-ID: <000000000000761c0e05c446d750@google.com> (raw)
In-Reply-To: <000000000000f6d80505abb42b60@google.com>
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=140478ffd00000
start commit: c3d8f220 Merge tag 'kbuild-fixes-v5.9' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=bb68b9e8a8cc842f
dashboard link: https://syzkaller.appspot.com/bug?extid=35e70efb794757d7e175
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f6602e900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1203cc61900000
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
parent reply other threads:[~2021-06-08 20:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000f6d80505abb42b60@google.com>]
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=000000000000761c0e05c446d750@google.com \
--to=syzbot+35e70efb794757d7e175@syzkaller.appspotmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=fw@strlen.de \
--cc=johan.hedberg@gmail.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--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;
as well as URLs for NNTP newsgroup(s).