summaryrefslogtreecommitdiff
path: root/sound
diff options
context:
space:
mode:
authorStefano Brivio <sbrivio@redhat.com>2017-07-24 21:14:28 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-08-11 15:49:33 (GMT)
commit23a91c8ab682b841a18a88cb1d5332f20f1ec219 (patch)
tree4324aa80972dc479a69595c2f28aff9f5a9a33c5 /sound
parent47f3bf6e31164a0a3b77746d30bf9b3ac9664b03 (diff)
downloadlinux-23a91c8ab682b841a18a88cb1d5332f20f1ec219.tar.xz
ipv6: Don't increase IPSTATS_MIB_FRAGFAILS twice in ip6_fragment()
[ Upstream commit afce615aaabfbaad02550e75c0bec106dafa1adf ] RFC 2465 defines ipv6IfStatsOutFragFails as: "The number of IPv6 datagrams that have been discarded because they needed to be fragmented at this output interface but could not be." The existing implementation, instead, would increase the counter twice in case we fail to allocate room for single fragments: once for the fragment, once for the datagram. This didn't look intentional though. In one of the two affected affected failure paths, the double increase was simply a result of a new 'goto fail' statement, introduced to avoid a skb leak. The other path appears to be affected since at least 2.6.12-rc2. Reported-by: Sabrina Dubroca <sdubroca@redhat.com> Fixes: 1d325d217c7f ("ipv6: ip6_fragment: fix headroom tests and skb leak") Signed-off-by: Stefano Brivio <sbrivio@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'sound')
0 files changed, 0 insertions, 0 deletions