| 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: <1320858706.2531.45.camel@pro6455b.example.com> Date: Wed, 09 Nov 2011 12:11:46 -0500 From: Dilip Daya <dilip.daya@...com> To: linux-kernel@...r.kernel.org Cc: ebiederm@...ssion.com, jmorris@...ei.org Subject: ip_local_deliver_finish: proto 108 (IPComp) isn't netns-ready Hi All, LTP-network tests produced: "ip_local_deliver_finish: proto 108 (IPComp) isn't netns-ready" Question: Is the above a bug or feature (IPComp, mode: transport) not netns enabled? Environment: * v3.1-stable kernel. * Configured two network-namespaces via "ip netns add ...". on a single system: netns0 (assigned as server) and netns1 (assigned as client). - assigned multiple physical NICs to netns0 and netns1. * Entered netns1 (ip netns exec netns1 bash) to execute ltp-network suite of tests between netns1 and netns0. * The following LTP tests produced messages: "kernel: ip_local_deliver_finish: proto 108 isn't netns-ready" - /usr/lib/ltp/testcases/bin/icmp4-multi-diffip06 - /usr/lib/ltp/testcases/bin/tcp4-multi-diffip13 - /usr/lib/ltp/testcases/bin/udp4-multi-diffip06 - /usr/lib/ltp/testcases/bin/udp4-multi-diffnic06 - /usr/lib/ltp/testcases/bin/udp4-multi-diffport06 * I also noticed missing ".netns_ok = 1" in: - http://lxr.linux.no/linux+v3.1/net/ipv4/ipcomp.c#L150 -DilipD. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists