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
| ||
|
Message-Id: <20190504.014010.1890791222224399323.davem@davemloft.net> Date: Sat, 04 May 2019 01:40:10 -0400 (EDT) From: David Miller <davem@...emloft.net> To: dsahern@...nel.org Cc: nikolay@...ulusnetworks.com, netdev@...r.kernel.org, dsahern@...il.com Subject: Re: [PATCH net-next] ipmr: Do not define MAXVIFS twice From: David Ahern <dsahern@...nel.org> Date: Thu, 2 May 2019 15:23:26 -0700 > From: David Ahern <dsahern@...il.com> > > b70432f7319eb refactored mroute code to make it common between ipv4 > and ipv6. In the process, MAXVIFS got defined a second time: the > first is in the uapi file linux/mroute.h. A second one was created > presumably for IPv6 but it is not needed. Remove it and have > mroute_base.h include the uapi file directly since it is shared. > > include/linux/mroute.h can not be included in mroute_base.h because > it contains a reference to mr_mfc which is defined in mroute_base.h. > > Signed-off-by: David Ahern <dsahern@...il.com> Applied.
Powered by blists - more mailing lists