From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: syzbot <syzbot+a61aa19b0c14c8770bd9@syzkaller.appspotmail.com>,
davem@davemloft.net, dsahern@gmail.com, kuba@kernel.org,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
yoshfuji@linux-ipv6.org
Subject: Re: general protection fault in fib_dump_info (2)
Date: Fri, 21 Aug 2020 19:00:18 +0300 [thread overview]
Message-ID: <47e92c2b-c9c5-4c74-70c4-103e70e91630@cumulusnetworks.com> (raw)
In-Reply-To: <00000000000039b10005ad64df20@google.com>
On 8/21/20 6:27 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: da2968ff Merge tag 'pci-v5.9-fixes-1' of git://git.kernel...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=137316ca900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a0437fdd630bee11
> dashboard link: https://syzkaller.appspot.com/bug?extid=a61aa19b0c14c8770bd9
> compiler: gcc (GCC) 10.1.0-syz 20200507
> userspace arch: i386
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12707051900000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1150a046900000
>
> The issue was bisected to:
>
> commit 0b5e2e39739e861fa5fc84ab27a35dbe62a15330
> Author: David Ahern <dsahern@gmail.com>
> Date: Tue May 26 18:56:16 2020 +0000
>
> nexthop: Expand nexthop_is_multipath in a few places
>
This seems like a much older bug to me, the code allows to pass 0 groups and
thus we end up without any nh_grp_entry pointers. I reproduced it with a
modified iproute2 that sends an empty NHA_GROUP and then just uses the new
nexthop in any way (e.g. add a route with it). This is the same bug as the
earlier report for: "general protection fault in fib_check_nexthop"
I have a patch but I'll be able to send it tomorrow.
Cheers,
Nik
next prev parent reply other threads:[~2020-08-21 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 15:27 syzbot
2020-08-21 16:00 ` Nikolay Aleksandrov [this message]
2020-08-21 16:05 ` David Ahern
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=47e92c2b-c9c5-4c74-70c4-103e70e91630@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+a61aa19b0c14c8770bd9@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
all inboxes | Powered by JetHome®