From: Eric Dumazet <erdnetdev@gmail.com>
To: syzbot <syzbot+a7c030a05218db921de5@syzkaller.appspotmail.com>,
davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org
Subject: Re: [syzbot] WARNING in mroute_clean_tables
Date: Thu, 10 Feb 2022 08:39:40 -0800 [thread overview]
Message-ID: <9bb39c37-0fc9-f4a7-dd4b-897f0a8fae18@gmail.com> (raw)
In-Reply-To: <000000000000ad4e9c05d7aa7064@google.com>
On 2/10/22 06:05, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: e5313968c41b Merge branch 'Split bpf_sk_lookup remote_port..
> git tree: bpf-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=141c859a700000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c40b67275bfe2a58
> dashboard link: https://syzkaller.appspot.com/bug?extid=a7c030a05218db921de5
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=130486f8700000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d9f758700000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+a7c030a05218db921de5@syzkaller.appspotmail.com
#syz fix: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table()
on failure path
next prev parent reply other threads:[~2022-02-10 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 9:37 [syzbot] WARNING in mroute_clean_tables syzbot
2022-02-10 14:05 ` syzbot
2022-02-10 16:39 ` Eric Dumazet [this message]
2022-05-11 16:40 ` syzbot
2022-05-11 19:16 ` Eric Dumazet
2022-05-25 19:16 ` syzbot
2022-06-08 19:16 ` syzbot
2022-06-08 20:05 ` Jakub Kicinski
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=9bb39c37-0fc9-f4a7-dd4b-897f0a8fae18@gmail.com \
--to=erdnetdev@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+a7c030a05218db921de5@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;
as well as URLs for NNTP newsgroup(s).