lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Dec 2019 19:43:43 +0100 From: Jiri Pirko <jiri@...nulli.us> To: Jakub Kicinski <jakub.kicinski@...ronome.com> Cc: Michal Kubecek <mkubecek@...e.cz>, David Miller <davem@...emloft.net>, netdev@...r.kernel.org, Andrew Lunn <andrew@...n.ch>, Florian Fainelli <f.fainelli@...il.com>, John Linville <linville@...driver.com>, Stephen Hemminger <stephen@...workplumber.org>, Johannes Berg <johannes@...solutions.net>, linux-kernel@...r.kernel.org Subject: Re: [PATCH net-next v2 1/5] rtnetlink: provide permanent hardware address in RTM_NEWLINK Tue, Dec 10, 2019 at 06:51:05PM CET, jakub.kicinski@...ronome.com 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? 🤔 Hmm, I guess that is a good idea.
Powered by blists - more mailing lists