This is a note to let you know that I've just added the patch titled
ip_tunnel:multicast process cause panic due to skb->_skb_refdst NULL pointer
to the 3.13-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:
ip_tunnel-multicast-process-cause-panic-due-to-skb-_skb_refdst-null-pointer.patch
and it can be found in the queue-3.13 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From foo@baz Wed Mar 19 23:31:33 Local time zone must be set--see zic manual page 2014
From: Xin Long <lucien.xin@xxxxxxxxx>
Date: Mon, 3 Mar 2014 20:18:36 +0800
Subject: ip_tunnel:multicast process cause panic due to skb->_skb_refdst NULL pointer
From: Xin Long <lucien.xin@xxxxxxxxx>
[ Upstream commit 10ddceb22bab11dab10ba645c7df2e4a8e7a5db5 ]
when ip_tunnel process multicast packets, it may check if the packet is looped
back packet though 'rt_is_output_route(skb_rtable(skb))' in ip_tunnel_rcv(),
but before that , skb->_skb_refdst has been dropped in iptunnel_pull_header(),
so which leads to a panic.
fix the bug: https://bugzilla.kernel.org/show_bug.cgi?id=70681
Signed-off-by: Xin Long <lucien.xin@xxxxxxxxx>
Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
net/ipv4/ip_tunnel_core.c | 1 -
1 file changed, 1 deletion(-)
--- a/net/ipv4/ip_tunnel_core.c
+++ b/net/ipv4/ip_tunnel_core.c
@@ -109,7 +109,6 @@ int iptunnel_pull_header(struct sk_buff
secpath_reset(skb);
if (!skb->l4_rxhash)
skb->rxhash = 0;
- skb_dst_drop(skb);
skb->vlan_tci = 0;
skb_set_queue_mapping(skb, 0);
skb->pkt_type = PACKET_HOST;
Patches currently in stable-queue which might be from lucien.xin@xxxxxxxxx are
queue-3.13/ip_tunnel-multicast-process-cause-panic-due-to-skb-_skb_refdst-null-pointer.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html