All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+81af6e9b3c4b8bc874f8@syzkaller.appspotmail.com>
To: John.Linn@xilinx.com, a@unstable.cc, anant.thazhemadam@gmail.com,
	andriin@fb.com, anirudh@xilinx.com, ast@kernel.org,
	b.a.t.m.a.n@lists.open-mesh.org, bpf@vger.kernel.org,
	daniel@iogearbox.net, davem@davemloft.net, dsahern@gmail.com,
	hancock@sedsystems.ca, john.fastabend@gmail.com, kafai@fb.com,
	kpsingh@chromium.org, kuba@kernel.org, kuznet@ms2.inr.ac.ru,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, mareklindner@neomailbox.ch,
	michal.simek@xilinx.com, netdev@vger.kernel.org,
	nikolay@cumulusnetworks.com, songliubraving@fb.com,
	sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
	yhs@fb.com, yoshfuji@linux-ipv6.org
Subject: Re: general protection fault in rt6_fill_node
Date: Thu, 01 Oct 2020 11:46:04 -0700	[thread overview]
Message-ID: <000000000000abcd5505b0a06d96@google.com> (raw)
In-Reply-To: <0000000000008fddd805adc8c56f@google.com>

syzbot suspects this issue was fixed by commit:

commit eeaac3634ee0e3f35548be35275efeca888e9b23
Author: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Date:   Sat Aug 22 12:06:36 2020 +0000

    net: nexthop: don't allow empty NHA_GROUP

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12beed5b900000
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=a0437fdd630bee11
dashboard link: https://syzkaller.appspot.com/bug?extid=81af6e9b3c4b8bc874f8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13ff8539900000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=143f3a96900000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: net: nexthop: don't allow empty NHA_GROUP

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+81af6e9b3c4b8bc874f8@syzkaller.appspotmail.com>
To: John.Linn@xilinx.com, a@unstable.cc, anant.thazhemadam@gmail.com,
	 andriin@fb.com, anirudh@xilinx.com, ast@kernel.org,
	 b.a.t.m.a.n@lists.open-mesh.org, bpf@vger.kernel.org,
	daniel@iogearbox.net,  davem@davemloft.net, dsahern@gmail.com,
	hancock@sedsystems.ca,  john.fastabend@gmail.com, kafai@fb.com,
	kpsingh@chromium.org, kuba@kernel.org,  kuznet@ms2.inr.ac.ru,
	linux-arm-kernel@lists.infradead.org,
	 linux-kernel@vger.kernel.org, mareklindner@neomailbox.ch,
	 michal.simek@xilinx.com, netdev@vger.kernel.org,
	nikolay@cumulusnetworks.com,  songliubraving@fb.com,
	sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
	 yhs@fb.com, yoshfuji@linux-ipv6.org
Subject: Re: general protection fault in rt6_fill_node
Date: Thu, 01 Oct 2020 11:46:04 -0700	[thread overview]
Message-ID: <000000000000abcd5505b0a06d96@google.com> (raw)
In-Reply-To: <0000000000008fddd805adc8c56f@google.com>

syzbot suspects this issue was fixed by commit:

commit eeaac3634ee0e3f35548be35275efeca888e9b23
Author: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Date:   Sat Aug 22 12:06:36 2020 +0000

    net: nexthop: don't allow empty NHA_GROUP

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12beed5b900000
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=a0437fdd630bee11
dashboard link: https://syzkaller.appspot.com/bug?extid=81af6e9b3c4b8bc874f8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13ff8539900000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=143f3a96900000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: net: nexthop: don't allow empty NHA_GROUP

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-10-01 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 14:38 general protection fault in rt6_fill_node syzbot
2020-08-26 14:38 ` syzbot
2020-10-01 18:46 ` syzbot [this message]
2020-10-01 18:46   ` syzbot
2020-11-11 11:19   ` Dmitry Vyukov
2020-11-11 11:19     ` Dmitry Vyukov
2020-11-11 11:19     ` 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=000000000000abcd5505b0a06d96@google.com \
    --to=syzbot+81af6e9b3c4b8bc874f8@syzkaller.appspotmail.com \
    --cc=John.Linn@xilinx.com \
    --cc=a@unstable.cc \
    --cc=anant.thazhemadam@gmail.com \
    --cc=andriin@fb.com \
    --cc=anirudh@xilinx.com \
    --cc=ast@kernel.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=hancock@sedsystems.ca \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=kuba@kernel.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mareklindner@neomailbox.ch \
    --cc=michal.simek@xilinx.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=songliubraving@fb.com \
    --cc=sw@simonwunderlich.de \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.