diff options
| author | Dave Jones <davej@codemonkey.org.uk> | 2016-09-02 20:39:50 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-09-06 21:54:17 +0200 |
| commit | 03c2778a938aaba0893f6d6cdc29511d91a79848 (patch) | |
| tree | c910de1f10013bbc12295c279c727e5e39099ba5 /drivers | |
| parent | af_unix: split 'u->readlock' into two: 'iolock' and 'bindlock' (diff) | |
| download | linux-03c2778a938aaba0893f6d6cdc29511d91a79848.tar.xz linux-03c2778a938aaba0893f6d6cdc29511d91a79848.zip | |
ipv6: release dst in ping_v6_sendmsg
Neither the failure or success paths of ping_v6_sendmsg release
the dst it acquires. This leads to a flood of warnings from
"net/core/dst.c:288 dst_release" on older kernels that
don't have 8bf4ada2e21378816b28205427ee6b0e1ca4c5f1 backported.
That patch optimistically hoped this had been fixed post 3.10, but
it seems at least one case wasn't, where I've seen this triggered
a lot from machines doing unprivileged icmp sockets.
Cc: Martin Lau <kafai@fb.com>
Signed-off-by: Dave Jones <davej@codemonkey.org.uk>
Acked-by: Martin KaFai Lau <kafai@fb.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions