netdev - Re: [RFC] ipvs: Keep track of backlog connections

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.58.1009020249090.14356@u.domain.uli>
Date:	Thu, 2 Sep 2010 03:16:40 +0300 (EEST)
From:	Julian Anastasov <ja@....bg>
To:	Simon Horman <horms@...ge.net.au>
cc:	Sven Wegener <sven.wegener@...aler.net>, lvs-devel@...r.kernel.org,
	netdev@...r.kernel.org, Wensong Zhang <wensong@...ux-vs.org>
Subject: Re: [RFC] ipvs: Keep track of backlog connections


	Hello,

On Wed, 1 Sep 2010, Simon Horman wrote:

> On the kernel-side of things, internally it should be easy
> enough to either expand flags or add a new element to the structure.
> So it seems to me that the problem is the kernel/user-space interface.
> And if that is the case, I think the best idea is to just use
> the netlink interface for all new configuration options and have
> new features unsupported through the old, legacy, ioctl interface.

	No, there should be no problem with the interface,
it already uses 32 bits. We should change only cp->flags
to 32 bits and new flags should go after bit 16 if they
are not needed for sync. Some flags can be changed safely,
for example, IP_VS_CONN_F_SYNC: it is not used by ipvsadm,
it is set only in backup, so it can be moved after bit 16.
May be another idea is to create 2nd version for the
struct ip_vs_sync_conn to support more features.

Regards

--
Julian Anastasov <ja@....bg>
--
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