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: Fri, 20 Dec 2019 21:19:05 -0800 (PST) From: David Miller <davem@...emloft.net> To: john.rutherford@...tech.com.au Cc: netdev@...r.kernel.org, tipc-discussion@...ts.sourceforge.net Subject: Re: [net-next] tipc: make legacy address flag readable over netlink From: john.rutherford@...tech.com.au Date: Thu, 19 Dec 2019 16:03:57 +1100 > From: John Rutherford <john.rutherford@...tech.com.au> > > To enable iproute2/tipc to generate backwards compatible > printouts and validate command parameters for nodes using a > <z.c.n> node address, it needs to be able to read the legacy > address flag from the kernel. The legacy address flag records > the way in which the node identity was originally specified. > > The legacy address flag is requested by the netlink message > TIPC_NL_ADDR_LEGACY_GET. If the flag is set the attribute > TIPC_NLA_NET_ADDR_LEGACY is set in the return message. > > Signed-off-by: John Rutherford <john.rutherford@...tech.com.au> > Acked-by: Jon Maloy <jon.maloy@...csson.com> Applied.
Powered by blists - more mailing lists