netdev - Re: [PATCHv2 net-next 0/3] Small IPsec fix

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: <20131108115459.GT31491@secunet.com>
Date:	Fri, 8 Nov 2013 12:54:59 +0100
From:	Steffen Klassert <steffen.klassert@...unet.com>
To:	Fan Du <fan.du@...driver.com>
Cc:	herbert@...dor.hengli.com.au, davem@...emloft.net,
	netdev@...r.kernel.org
Subject: Re: [PATCHv2 net-next 0/3] Small IPsec fix

On Thu, Nov 07, 2013 at 05:47:47PM +0800, Fan Du wrote:
> Hi
> 
> This patchset made below modifications:
>  - Fix setting policy index with "ip xfrm ... index=xx"
>    which is currently broken
> 
>  - Using correct name space for home agent when migrating
>    key info.
> 
>  - Put xfrm locks into per namespace to improve scalability.
> 
> Changelog:
> v2:
>   xfrm: Namespacify xfrm state/policy locks
>   -Fix compile error when CONFIG_NET_NS is unset, thanks for the lovely build robot.
> 
> Fan Du (3):
>   xfrm: Try to honor policy index if it's supplied by user
>   xfrm: Using the right namespace to migrate key info
>   xfrm: Namespacify xfrm state/policy locks

Your patches are currently in the ipsec-next testing branch.
linux-next should not contain v3.14 material at the moment,
so I'll wait until after the merge window before I'm pushing
them to the master branch. No further action from your side
required.

Thanks, Fan!

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