summaryrefslogtreecommitdiffstats
path: root/net/ipv4
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2014-09-12 17:51:32 -0400
committerDavid S. Miller <davem@davemloft.net>2014-09-12 17:51:32 -0400
commitc5306726bc619be21303c55e09aac317072b3c25 (patch)
tree88068940307b6369cc1f6a2b346f6a070949f4bd /net/ipv4
parent72b126a45eaca22fb6a8788e8a89c159f3ae2ac5 (diff)
parentbf7fa551e0ce507b82935055f4b4aa229be73eeb (diff)
downloadlinux-stable-c5306726bc619be21303c55e09aac317072b3c25.tar.gz
linux-stable-c5306726bc619be21303c55e09aac317072b3c25.tar.bz2
linux-stable-c5306726bc619be21303c55e09aac317072b3c25.zip
Merge branch 'sock_queue_err_skb'
Alexander Duyck says: ==================== Address reference counting issues with sock_queue_err_skb After looking over the code for skb_clone_sk after some comments made by Eric Dumazet I have come to the conclusion that skb_clone_sk is taking the correct approach in how to handle the sk_refcnt when creating a buffer that is eventually meant to be returned to the socket via the sock_queue_err_skb function. However upon review of other callers I found what I believe to be a possible reference count issue in the path for handling "wifi ack" packets. To address this I have applied the same logic that is currently in place so that the sk_refcnt will be forced to stay at least 1, or we will not provide an skb to return in the sk_error_queue. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4')
0 files changed, 0 insertions, 0 deletions