netdev - Re: [PATCH] ipvs: Use pointer to address from sync message

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:	Sat, 6 Sep 2008 14:26:11 +1000
From:	Simon Horman <horms@...ge.net.au>
To:	Julius Volz <juliusv@...gle.com>
Cc:	Sven Wegener <sven.wegener@...aler.net>, netdev@...r.kernel.org,
	lvs-devel@...r.kernel.org, kaber@...sh.net, vbusam@...gle.com
Subject: Re: [PATCH] ipvs: Use pointer to address from sync message

On Fri, Sep 05, 2008 at 02:28:48PM +0200, Julius Volz wrote:
> On Fri, Sep 5, 2008 at 1:46 PM, Sven Wegener <sven.wegener@...aler.net> wrote:
> > We want a pointer to it, not the value casted to a pointer.
> 
> Ouch, right!
> 
> > Signed-off-by: Sven Wegener <sven.wegener@...aler.net>
> > ---
> >  net/ipv4/ipvs/ip_vs_sync.c |    6 +++---
> >  1 files changed, 3 insertions(+), 3 deletions(-)
> >
> > I've been too late with having a look at these patches. I'm going to
> > send follow-up patches for the issues I find.

Sven, as always thanks very much for your patches.

> Thanks! There are probably still lots of these easy-to-miss (but bad)
> bugs in this big new bunch of code...
> 
> > Simon, please apply onto lvs-next-2.6.
> 
> Yes!

Julius, can I take that as an Acked-by for the follwing changes?

[PATCH] ipvs: Use pointer to address from sync message
[PATCH] ipvs: Return negative error values from
[PATCH] ipvs: Mark tcp/udp v4 and v6 debug functions static
[PATCH] ipvs: Reject ipv6 link-local addresses for destinations

--
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