netdev - Re: [PATCHv2] ipvs: Cleanup sync daemon code

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:	Mon, 30 Jun 2008 14:51:56 +1000
From:	Simon Horman <horms@...ge.net.au>
To:	Sven Wegener <sven.wegener@...aler.net>
Cc:	wensong@...ux-vs.org, ja@....bg, netdev@...r.kernel.org
Subject: Re: [PATCHv2] ipvs: Cleanup sync daemon code

On Sun, Jun 29, 2008 at 07:32:41PM +0200, Sven Wegener wrote:
> It's been a while since my last post of this patch series, but here we go gain.
> 
> Changes since last post:
> - Dropped the master daemon sleep change for now, that needs some more work.
> - Splitted up the patch into a couple of logical chunks.
> 
> The patches are
> 
> Sven Wegener (5):
>       ipvs: Initialize mcast addr at compile time
>       ipvs: Use ERR_PTR for returning errors from make_receive_sock() and make_send_sock()
>       ipvs: Use kthread_run() instead of doing a double-fork via kernel_thread()
>       ipvs: Put backup thread on mcast socket wait queue
>       ipvs: Use schedule_timeout_interruptible() instead of msleep_interruptible()
> 
> The overall difstat looks like
> 
>  ip_vs_sync.c |  431 +++++++++++++++++++++++------------------------------------
>   1 file changed, 172 insertions(+), 259 deletions(-)
> 
> The patches are based on v2.6.26-rc8. If someone wants to pull them, that can
> be done from
> 
> git://git.stealer.net/linux-2.6.git stealer/ipvs/sync-daemon-cleanup

These patches look good to me.

-- 
Horms

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