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: Wed, 11 Jun 2008 21:05:57 +0200 From: "Julius Volz" <juliusv@...gle.com> To: "Patrick McHardy" <kaber@...sh.net> Cc: lvs-devel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [PATCH 00/26] IPVS: Add first IPv6 support to IPVS. On Wed, Jun 11, 2008 at 8:42 PM, Patrick McHardy <kaber@...sh.net> wrote: > Julius Volz wrote: >> Another question I was unsure about: is the breaking of the >> userspace-to-kernel interface even acceptable at all? I think the code >> would get ugly (and have even more duplication) if you wanted to keep >> the backwards compatibility. And you have to compile ipvsadm for your >> kernel version anyways. > > Usually its not acceptable. Why do you have compile ipvsadm > for specific kernel versions? ipvsadm uses get/set-sockopts on a raw socket to pass commands and structs (as defined in include/net/ip_vs.h) to the kernel. So the passed structs have to match exactly between userspace and kernel. The kernel ip_vs.h also includes a version number that is used to verify that ipvsadm matches your kernel version. Julius -- Google Switzerland GmbH -- 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