netdev - Re: [PATCH 00/26] IPVS: Add first IPv6 support to IPVS.

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]

Date:	Wed, 18 Jun 2008 16:27:28 +0200
From:	"Julius Volz" <juliusv@...gle.com>
To:	"Patrick McHardy" <kaber@...sh.net>
Cc:	"Simon Horman" <horms@...ge.net.au>,
	"Vince Busam" <vbusam@...gle.com>,
	"Ben Greear" <greearb@...delatech.com>, lvs-devel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH 00/26] IPVS: Add first IPv6 support to IPVS.

On Wed, Jun 18, 2008 at 4:19 PM, Patrick McHardy <kaber@...sh.net> wrote:
>> 2) for the service flags, only one bit is set from userspace
>> (persistent/nonpersistent service). So this might be not too bad to
>> have as a single Netlink flag attribute.
>
> And this bit can't be unset (or if it currently can't be,
> it also wouldn't make sense to be able to unset it)?

It can get unset when editing a persistent service to be
non-persistent, so you would still have to include it in a change
request that doesn't want to unset it. Since it's only one flag
though, it didn't seem too bad to me.

An alternative (also, in case of more flags in the future) would be to
put flags into a nested attribute and if this is not supplied from
userspace during an edit operation, the flags will be left untouched.

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