This is a note to let you know that I've just added the patch titled

    xfrm: release neighbor upon dst destruction

to the 3.8-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     xfrm-release-neighbor-upon-dst-destruction.patch
and it can be found in the queue-3.8 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From b79c2530c1d19741a701259d417cae0fd1ed2cd9 Mon Sep 17 00:00:00 2001
From: Romain KUNTZ <[email protected]>
Date: Mon, 18 Feb 2013 02:36:24 +0000
Subject: xfrm: release neighbor upon dst destruction


From: Romain KUNTZ <[email protected]>

[ Upstream commit 18cf0d0784b4a634472ed24d0d7ca1c721d93e90 ]

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 <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
 net/ipv6/xfrm6_policy.c |    2 ++
 1 file changed, 2 insertions(+)

--- a/net/ipv6/xfrm6_policy.c
+++ b/net/ipv6/xfrm6_policy.c
@@ -236,6 +236,8 @@ static void xfrm6_dst_destroy(struct dst
 {
        struct xfrm_dst *xdst = (struct xfrm_dst *)dst;
 
+       if (likely(xdst->u.rt6.n))
+               neigh_release(xdst->u.rt6.n);
        if (likely(xdst->u.rt6.rt6i_idev))
                in6_dev_put(xdst->u.rt6.rt6i_idev);
        dst_destroy_metrics_generic(dst);


Patches currently in stable-queue which might be from [email protected] are

queue-3.8/xfrm-release-neighbor-upon-dst-destruction.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to