From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: WARNING in wiphy_register Date: Mon, 15 Jan 2018 09:22:41 +0100 Message-ID: <1516004561.410.3.camel@sipsolutions.net> References: <94eb2c05e11e2f85150562b007ef@google.com> (sfid-20180113_233740_281154_0AEBEE6F) Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit To: syzbot , davem@davemloft.net, linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com Return-path: In-Reply-To: <94eb2c05e11e2f85150562b007ef@google.com> (sfid-20180113_233740_281154_0AEBEE6F) Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hi syzbot maintainers, Thanks for the report. > hwsim_new_radio_nl+0x5b7/0x7c0 drivers/net/wireless/mac80211_hwsim.c:3152 > genl_family_rcv_msg+0x7b7/0xfb0 net/netlink/genetlink.c:599 > genl_rcv_msg+0xb2/0x140 net/netlink/genetlink.c:624 You're getting into the kernel via generic netlink receive, so just as an FYI - the generic netlink numbers aren't stable across systems, so your reproducer has a quite good chance of not working without your kernel .config and (virt) hardware environment. I'll take a look at this and the rfkill one, I assume that there are some sanity checks missing in hwsim generic netlink when it builds a radio struct. However, I can't really promise that I'll be able to validate the changes against your reproducer. johannes