netdev - Re: [PATCHv4 net-next] xfrm: Namespacify xfrm_policy_sk

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: <20131224103521.GB29716@secunet.com>
Date:	Tue, 24 Dec 2013 11:35:21 +0100
From:	Steffen Klassert <steffen.klassert@...unet.com>
To:	Fan Du <fan.du@...driver.com>
Cc:	Eric Dumazet <eric.dumazet@...il.com>,
	王聪 <xiyou.wangcong@...il.com>,
	davem@...emloft.net, netdev@...r.kernel.org
Subject: Re: [PATCHv4 net-next] xfrm: Namespacify xfrm_policy_sk_bundles

On Fri, Dec 20, 2013 at 11:34:41AM +0800, Fan Du wrote:
> 
> Subject: [PATCHv4 net-next] xfrm: Namespacify xfrm_policy_sk_bundles
> 
> xfrm_policy_sk_bundles, protected by net->xfrm.xfrm_policy_sk_bundle_lock
> should be put into netns xfrm structure, otherwise xfrm_policy_sk_bundles
> can be corrupted from different net namespace.

I'm ok with this patch, but I wonder where we use these cached socket
bundles. After a quick look I see where we add and where we delete
them, but I can't see how we use these cached bundles. 
--
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