netdev - Re: [RFC PATCH] xfrm: release neighbor upon dst destruction

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] [day] [month] [year] [list]

Message-Id: <20130218.145808.1730142643182502981.davem@davemloft.net>
Date:	Mon, 18 Feb 2013 14:58:08 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	r.kuntz@...lavors.com
Cc:	netdev@...r.kernel.org, steffen.klassert@...unet.com,
	yoshfuji@...ux-ipv6.org
Subject: Re: [RFC PATCH] xfrm: release neighbor upon dst destruction 

From: Romain KUNTZ <r.kuntz@...lavors.com>
Date: Mon, 18 Feb 2013 13:36:24 +0100

> Neighbor is cloned in xfrm6_fill_dst but seems to never be released.
> Neighbor entry should be released when XFRM6 dst entry is destroyed
> in xfrm6_dst_destroy, otherwise references may be kept forever on 
> the device pointed by the neighbor entry.
> 
> I may not have understood all the subtleties of XFRM & dst so I would
> be happy to receive comments on this patch. 
> 
> Signed-off-by: Romain Kuntz <r.kuntz@...lavors.com>

This patch is definitely correct.

Applied and queued up for -stable, thanks.
--
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