Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp5848466ybl; Tue, 10 Dec 2019 12:30:18 -0800 (PST) X-Google-Smtp-Source: APXvYqxSGOi1kSgRuqxDH01KO2ehl5KUPQn6amEvhNdWYplYHnsXcDcIV1Vp0ngtJI7mUTIOxqZ0 X-Received: by 2002:a9d:7dc9:: with SMTP id k9mr27499605otn.117.1576009818347; Tue, 10 Dec 2019 12:30:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576009818; cv=none; d=google.com; s=arc-20160816; b=uBSL5xcnVaU8vDUlTp/WR8mUFTqknC2+TV+ujRbuXRHTadtmWk446uqBu4sROJPVCz ew/PqnJnUg/J3cy2B/lpflQaFnrU0ULNJj4JhIU+ObtId9j0RJqqXRG7aA4xSh+bXtFV iGcFmAmLu6kp1CeSjrYPIAsq0pqsurMoQXaIwk63+u0Km+ba7+9voEe3espOJthrv/4u +PQ13wprJ5qr7X2sYSC3LGcOy5eViJPlJNdOQzOEehmiZlwsjni9qJ4F4XX587yeUzl6 MGzfXsLDX9v/9KrQBf+A9jsfDbIvj3bd68NZ4ygpli69I/pAKkZP9PdimpGnalpukQgd QW0g== 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:cc:to:from:subject :message-id; bh=xP5jRmBOcRlZSHvoomYlMZXKtVXwykBD6kWtwdTFkeA=; b=Ns0J5D1Xrdu53aq2LFiGf0R+5tBncaF+H4Ug9Su3TmkdEbvQ/CzXe12tCtyN2QsZ+L wM5nYMWFTsZq/nLBKLgIo9M6k2z2jYJyVofscTkz3HUjNw9mlxVP6/Gy1EtfvIOoHVAZ +cTQXj1W02MxLhIg4ykagL7KV+BtTbXDOjAueJSLYZwE8MlbRZV3ln/vh/RmXRdZJ7Rt xRMTKp2MplSbX1b7OUjFKDMTNVoVmDWK2+lHT0XxSLJ/gAvnBMJ/gX4QXKSjZdcvYsRV JwZlYE4VxgYNpWIVboTNzqCDCed2HfKeV80Y5TUJW83C3xyNyy44W1WQq+2OxET0aVTE FH+g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l12si2577208otj.30.2019.12.10.12.30.05; Tue, 10 Dec 2019 12:30:18 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727030AbfLJU3X (ORCPT + 99 others); Tue, 10 Dec 2019 15:29:23 -0500 Received: from s3.sipsolutions.net ([144.76.43.62]:53582 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725999AbfLJU3X (ORCPT ); Tue, 10 Dec 2019 15:29:23 -0500 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.92.3) (envelope-from ) id 1iem89-0020Fc-TP; Tue, 10 Dec 2019 21:29:14 +0100 Message-ID: <1172ea9c3f70ec0ea527926b2daa6e94c80ee807.camel@sipsolutions.net> Subject: Re: [PATCH net-next v2 1/5] rtnetlink: provide permanent hardware address in RTM_NEWLINK From: Johannes Berg To: David Ahern , Jakub Kicinski , Jiri Pirko Cc: Michal Kubecek , David Miller , netdev@vger.kernel.org, Andrew Lunn , Florian Fainelli , John Linville , Stephen Hemminger , linux-kernel@vger.kernel.org Date: Tue, 10 Dec 2019 21:29:11 +0100 In-Reply-To: <513ce8a1-f3ee-bd5f-a27c-86729e0536fd@gmail.com> (sfid-20191210_212718_256450_DC91B1DA) References: <7c28b1aa87436515de39e04206db36f6f374dc2f.1575982069.git.mkubecek@suse.cz> <20191210095105.1f0008f5@cakuba.netronome.com> <0c9148be76615b3b77a3e730df75f311b1001b9f.camel@sipsolutions.net> <513ce8a1-f3ee-bd5f-a27c-86729e0536fd@gmail.com> (sfid-20191210_212718_256450_DC91B1DA) Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.2 (3.34.2-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2019-12-10 at 13:27 -0700, David Ahern wrote: > On 12/10/19 1:23 PM, Johannes Berg wrote: > > On Tue, 2019-12-10 at 21:22 +0100, Johannes Berg wrote: > > > On Tue, 2019-12-10 at 09:51 -0800, Jakub Kicinski wrote: > > > > On Tue, 10 Dec 2019 14:07:53 +0100 (CET), Michal Kubecek wrote: > > > > > @@ -1822,6 +1826,7 @@ static const struct nla_policy ifla_policy[IFLA_MAX+1] = { > > > > > [IFLA_PROP_LIST] = { .type = NLA_NESTED }, > > > > > [IFLA_ALT_IFNAME] = { .type = NLA_STRING, > > > > > .len = ALTIFNAMSIZ - 1 }, > > > > > + [IFLA_PERM_ADDRESS] = { .type = NLA_REJECT }, > > > > > }; > > > > > > > > > > static const struct nla_policy ifla_info_policy[IFLA_INFO_MAX+1] = { > > > > > > > > Jiri, I just noticed ifla_policy didn't get strict_start_type set when > > > > ALT_IFNAME was added, should we add it in net? ???? > > > > > > Does it need one? It shouldn't be used with > > > nla_parse_nested_deprecated(), and if it's used with nla_parse_nested() > > > then it doesn't matter? > > > > No, wait. I misread, you said "when ALT_IFNAME was added" but somehow I > > managed to read "when it was added"... > > > > So yeah, it should have one. Dunno about net, your call. I'd probably > > not bother for an NLA_REJECT attribute, there's little use including it > > anyway. > > > > It's new in net, so it has to be there not net-next. Oh, ok. Well, I was actually thinking to just add it on the next attribute or so, but I guess now that we're discussing it there's a higher chance of it actually happening :) johannes