This is a note to let you know that I've just added the patch titled
ipv4: Missing sk_nulls_node_init() in ping_unhash().
to the 3.19-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:
ipv4-missing-sk_nulls_node_init-in-ping_unhash.patch
and it can be found in the queue-3.19 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 Fri May 8 13:04:43 CEST 2015
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
Date: Fri, 1 May 2015 22:02:47 -0400
Subject: ipv4: Missing sk_nulls_node_init() in ping_unhash().
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
[ Upstream commit a134f083e79fb4c3d0a925691e732c56911b4326 ]
If we don't do that, then the poison value is left in the ->pprev
backlink.
This can cause crashes if we do a disconnect, followed by a connect().
Tested-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Reported-by: Wen Xu <hotdog3645@xxxxxxxxx>
Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
net/ipv4/ping.c | 1 +
1 file changed, 1 insertion(+)
--- a/net/ipv4/ping.c
+++ b/net/ipv4/ping.c
@@ -158,6 +158,7 @@ void ping_unhash(struct sock *sk)
if (sk_hashed(sk)) {
write_lock_bh(&ping_table.lock);
hlist_nulls_del(&sk->sk_nulls_node);
+ sk_nulls_node_init(&sk->sk_nulls_node);
sock_put(sk);
isk->inet_num = 0;
isk->inet_sport = 0;
Patches currently in stable-queue which might be from davem@xxxxxxxxxxxxx are
queue-3.19/ipv4-missing-sk_nulls_node_init-in-ping_unhash.patch
queue-3.19/bpf-fix-64-bit-divide.patch
queue-3.19/cxgb4-fix-mc1-memory-offset-calculation.patch
queue-3.19/mlx4-fix-tx-ring-affinity_mask-creation.patch
queue-3.19/net-mlx4_en-schedule-napi-when-rx-buffers-allocation-fails.patch
queue-3.19/route-use-ipv4_mtu-instead-of-raw-rt_pmtu.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