Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp575593ybz; Wed, 15 Apr 2020 14:21:45 -0700 (PDT) X-Google-Smtp-Source: APiQypJYliHMTtrV50kIf2yjSf9KHgzX47IWLEF7uZA55VjSftBULNyAlzh+NzhU/dFVWF77zBhi X-Received: by 2002:a17:906:6444:: with SMTP id l4mr6589020ejn.313.1586985704916; Wed, 15 Apr 2020 14:21:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586985704; cv=none; d=google.com; s=arc-20160816; b=FCqCq9nVgT6D5nc0fLri4bCg1xTyyMBJq2JG98swtVxPvEtXIYnU4rflSdwG/4uU76 vsJANvS+jiusbLfmmaFIqx3x2j3CCVCwCYwRRtddLlh5y0pkZI3dvpmziyiESvd/BRp9 QHARHwNbk+hgtQD/ZMIp9XIrDs0ri06UbPbU/pV4EFbu/jBteR+S5n92zJyXZVB0eYBW qGV6s7NDKk8DL4lH3TpTMCv6YGZrKYspADttM0K0ImVzAzOlOJdEgfOXXhTI4amwNG8w gG1Kf+TZrk1l2HPe5WC2nKNrGLrpsw+v26JCanN8/rwEMUxKkf/3NMzieDuaRi2ahzl2 asLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:to:from:subject:message-id; bh=uzZJttC43+slueKPHNX/hGpvimBSkwFglbzr8PJBYPE=; b=TEZgX30dIaPUg4UHtTz/39UaA/TRUd2OC/AOopS6EkyCrsD65lt7XiEnqjBsNVX8Lj 4WxbJUqzrt2Kehso+VMq67xiO8UhFcUxH3BGzdSRltJJnkhdR91C1uYy8RTcsZMrP6B5 TA2mM0A2G/3JYZQF4hIPaH907Q4WyF66O6aCQDGJ+cidLrAyaIkw2hUGEOzD2tL7Wiyc Im7yDG9rnRBobGGkIDHZbfNnw6Gdh2EZgfm+/tIa28Ca1fZWi0N4yoCPdQT8in7Xl4ym AtZhyXQ54cd4TiXRBZk9q3fM5LBrctZrOGgdXS0efQk5glTmHDMaZ7o5LMOiSgNtMNTf Xd9Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f3si5097073edn.165.2020.04.15.14.21.21; Wed, 15 Apr 2020 14:21:44 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390816AbgDNLM1 (ORCPT + 99 others); Tue, 14 Apr 2020 07:12:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36006 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1728734AbgDNLMS (ORCPT ); Tue, 14 Apr 2020 07:12:18 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B1A42C061A0C; Tue, 14 Apr 2020 04:12:17 -0700 (PDT) Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.93) (envelope-from ) id 1jOIxX-00Gpsu-6e; Tue, 14 Apr 2020 12:38:27 +0200 Message-ID: Subject: Re: WARNING in hwsim_new_radio_nl From: Johannes Berg To: syzbot , davem@davemloft.net, kvalo@codeaurora.org, linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, mathew.j.martineau@linux.intel.com, matthieu.baerts@tessares.net, netdev@vger.kernel.org, pabeni@redhat.com, syzkaller-bugs@googlegroups.com Date: Tue, 14 Apr 2020 12:38:22 +0200 In-Reply-To: <000000000000cb517b05a32c917b@google.com> (sfid-20200413_160506_506947_12BA215F) References: <000000000000cb517b05a32c917b@google.com> (sfid-20200413_160506_506947_12BA215F) Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi syzbot keepers, On Mon, 2020-04-13 at 07:05 -0700, syzbot wrote: > syzbot has bisected this bug to: > > commit 01cacb00b35cb62b139f07d5f84bcf0eeda8eff6 > Author: Paolo Abeni > Date: Fri Mar 27 21:48:51 2020 +0000 > > mptcp: add netlink-based PM > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10225bb3e00000 This is, fairly obviously, incorrect. Same with the bisection for 6693adf1698864d21734, which is really the same underlying problem as this one (though at a different code site). However, it stands out that this was bisected to a commit that adds a new generic netlink family in both cases. This makes sense - the reproducer identifies the family by *number*, but that number isn't stable, generic netlink families should be identified by *name*. Perhaps somehow syzbot could be taught that, so that the bisection is stable across kernels with different generic netlink families registered? Alternatively, we _could_ add some kind of stable ID mode, but I'm not sure we really want to ... since that would mean people start hardcoding IDs? johannes