From: syzbot <syzbot+bb3d7a24f705078b1286@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
fw@strlen.de, harshit.m.mogalapalli@oracle.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, marcelo.leitner@gmail.com,
mige07@migeof.com, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, yajun.deng@linux.dev
Subject: Re: [syzbot] WARNING in ipvlan_l3s_unregister
Date: Fri, 31 Dec 2021 18:18:11 -0800 [thread overview]
Message-ID: <0000000000002cbe9205d47be6d0@google.com> (raw)
In-Reply-To: <000000000000debe1c05a9c39c93@google.com>
syzbot suspects this issue was fixed by commit:
commit f123cffdd8fe8ea6c7fded4b88516a42798797d0
Author: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Date: Mon Nov 29 17:53:27 2021 +0000
net: netlink: af_netlink: Prevent empty skb by adding a check on len.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11e95e2bb00000
start commit: 6ba1b005ffc3 Merge tag 'asm-generic-fixes-5.8' of git://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=812bbfcb6ae2cd60
dashboard link: https://syzkaller.appspot.com/bug?extid=bb3d7a24f705078b1286
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103edc82900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net: netlink: af_netlink: Prevent empty skb by adding a check on len.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-01-01 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 10:48 WARNING in ipvlan_l3s_unregister syzbot
2020-07-26 7:11 ` syzbot
2022-01-01 2:18 ` syzbot [this message]
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=0000000000002cbe9205d47be6d0@google.com \
--to=syzbot+bb3d7a24f705078b1286@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=mige07@migeof.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yajun.deng@linux.dev \
/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).