From: syzbot <syzbot+b3b5c64f4880403edd36@syzkaller.appspotmail.com>
To: andriin@fb.com, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, edumazet@google.com,
fw@strlen.de, harshit.m.mogalapalli@oracle.com, hawk@kernel.org,
jiri@mellanox.com, john.fastabend@gmail.com, kafai@fb.com,
kpsingh@chromium.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
roopa@cumulusnetworks.com, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yajun.deng@linux.dev,
yhs@fb.com
Subject: Re: [syzbot] WARNING in rtnl_dellink
Date: Fri, 11 Feb 2022 19:24:15 -0800 [thread overview]
Message-ID: <000000000000c7d07705d7c9b7a4@google.com> (raw)
In-Reply-To: <000000000000c560bd05ad3c5187@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=107b5472700000
start commit: cd02217a5d81 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a0437fdd630bee11
dashboard link: https://syzkaller.appspot.com/bug?extid=b3b5c64f4880403edd36
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116f8172900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1145d1b1900000
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
next prev parent reply other threads:[~2022-02-12 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 15:04 WARNING in rtnl_dellink syzbot
2022-02-12 3:24 ` syzbot [this message]
2022-05-12 13:13 ` [syzbot] " 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=000000000000c7d07705d7c9b7a4@google.com \
--to=syzbot+b3b5c64f4880403edd36@syzkaller.appspotmail.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=hawk@kernel.org \
--cc=jiri@mellanox.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yajun.deng@linux.dev \
--cc=yhs@fb.com \
/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