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: Sat, 5 Oct 2013 22:25:11 -0700 From: Olof Johansson <olof@...om.net> To: David Miller <davem@...emloft.net> Cc: Fabio Estevam <festevam@...il.com>, edumazet@...gle.com, hannes@...ressinduktion.org, Network Development <netdev@...r.kernel.org>, Fabio Estevam <fabio.estevam@...escale.com> Subject: Re: [PATCH] net: secure_seq: Move net_secret_init() definition into CONFIG_IPV6 if block On Sat, Oct 5, 2013 at 1:27 PM, David Miller <davem@...emloft.net> wrote: > From: Fabio Estevam <festevam@...il.com> > Date: Sat, 5 Oct 2013 17:09:50 -0300 > >> From: Fabio Estevam <fabio.estevam@...escale.com> >> >> Commit 9a3bab6b05 (net: net_secret should not depend on TCP) introduced >> the following build warning when CONFIG_IPV6 is not selected: >> >> net/core/secure_seq.c:17:13: warning: 'net_secret_init' defined but not used [-Wunused-function] >> >> Fix it by moving net_secret_init(void) inside the '#if IS_ENABLED(CONFIG_IPV6)' >> block. >> >> Reported-by: Olof Johansson <olof@...om.net> >> Signed-off-by: Fabio Estevam <fabio.estevam@...escale.com> > > seq_scale is used by secure_tcp_sequence_number, which is only protected > by CONFIG_INET. I have no idea how you can get this build problem. > > And I cannot reproduce it here: You get it if you have CONFIG_NET enabled, but CONFIG_INET off. We seem to have a few defconfigs on arm that has that setting, likely because they lack native network interfaces but need local unix sockets. Or whatever. But that's how you hit it. Steps to reproduce, even with ARCH=sparc: make allnoconfig edit .config, set CONFIG_NET=y yes "" | make oldconfig make -Olof -- 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