From: Martin KaFai Lau <kafai@fb.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: <netdev@vger.kernel.org>
Subject: Re: ipv6: release dst in ping_v6_sendmsg
Date: Tue, 6 Sep 2016 10:36:21 -0700 [thread overview]
Message-ID: <20160906173621.GA33747@kafai-mba.local> (raw)
In-Reply-To: <20160902183950.p3iv25jnuwmq74sg@codemonkey.org.uk>
On Fri, Sep 02, 2016 at 02:39:50PM -0400, Dave Jones wrote:
> 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>
>
> diff --git a/net/ipv6/ping.c b/net/ipv6/ping.c
> index 0900352c924c..0e983b694ee8 100644
> --- a/net/ipv6/ping.c
> +++ b/net/ipv6/ping.c
> @@ -126,8 +126,10 @@ static int ping_v6_sendmsg(struct sock *sk, struct msghdr *msg, size_t len)
> rt = (struct rt6_info *) dst;
>
> np = inet6_sk(sk);
> - if (!np)
> - return -EBADF;
> + if (!np) {
> + err = -EBADF;
> + goto dst_err_out;
> + }
>
> if (!fl6.flowi6_oif && ipv6_addr_is_multicast(&fl6.daddr))
> fl6.flowi6_oif = np->mcast_oif;
> @@ -163,6 +165,9 @@ static int ping_v6_sendmsg(struct sock *sk, struct msghdr *msg, size_t len)
> }
> release_sock(sk);
>
> +dst_err_out:
> + dst_release(dst);
> +
> if (err)
> return err;
>
Acked-by: Martin KaFai Lau <kafai@fb.com>
next prev parent reply other threads:[~2016-09-06 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 18:39 ipv6: release dst in ping_v6_sendmsg Dave Jones
2016-09-06 17:36 ` Martin KaFai Lau [this message]
2016-09-06 17:52 ` Eric Dumazet
2016-09-06 18:50 ` Dave Jones
2016-09-06 19:56 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160906173621.GA33747@kafai-mba.local \
--to=kafai@fb.com \
--cc=davej@codemonkey.org.uk \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).