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: <54D4512A.5080809@redhat.com> Date: Fri, 06 Feb 2015 00:29:14 -0500 From: "Carlos O'Donell" <carlos@...hat.com> To: David Miller <davem@...emloft.net>, xiyou.wangcong@...il.com CC: netdev@...r.kernel.org, vlee@...pensource.com Subject: Re: [Patch net-next] ipv6: fix redefinition of in6_pktinfo and ip6_mtuinfo On 01/08/2015 10:38 PM, David Miller wrote: > From: Cong Wang <xiyou.wangcong@...il.com> > Date: Tue, 6 Jan 2015 15:45:31 -0800 > >> Both netinet/in.h and linux/ipv6.h define these two structs, >> if we include both of them, we got: >> >> /usr/include/linux/ipv6.h:19:8: error: redefinition of ‘struct in6_pktinfo’ >> struct in6_pktinfo { >> ^ >> In file included from /usr/include/arpa/inet.h:22:0, >> from txtimestamp.c:33: >> /usr/include/netinet/in.h:524:8: note: originally defined here >> struct in6_pktinfo >> ^ >> In file included from txtimestamp.c:40:0: >> /usr/include/linux/ipv6.h:24:8: error: redefinition of ‘struct ip6_mtuinfo’ >> struct ip6_mtuinfo { >> ^ >> In file included from /usr/include/arpa/inet.h:22:0, >> from txtimestamp.c:33: >> /usr/include/netinet/in.h:531:8: note: originally defined here >> struct ip6_mtuinfo >> ^ >> So similarly to what we did for in6_addr, we need to sync with >> libc header on their definitions. >> >> Signed-off-by: Cong Wang <xiyou.wangcong@...il.com> > > Applied. > When does this hit mainline? I've got Cong's patch ready for glibc, but the usual procedure is to commit after mainline has the matching patch. Not that it really matters, but it's just a useful thing to be able to say the trickle down is linux->glibc. Cheers, Carlos. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists