From: David Miller <davem@davemloft.net>
To: lucien.xin@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net] dccp: fix a memleak that dccp_ipv6 doesn't put reqsk properly
Date: Thu, 27 Jul 2017 00:01:22 -0700 (PDT) [thread overview]
Message-ID: <20170727.000122.1772066009028441614.davem@davemloft.net> (raw)
In-Reply-To: <17b2008535695e5885775418a31ee74f3ca704f5.1501049949.git.lucien.xin@gmail.com>
From: Xin Long <lucien.xin@gmail.com>
Date: Wed, 26 Jul 2017 14:19:09 +0800
> In dccp_v6_conn_request, after reqsk gets alloced and hashed into
> ehash table, reqsk's refcnt is set 3. one is for req->rsk_timer,
> one is for hlist, and the other one is for current using.
>
> The problem is when dccp_v6_conn_request returns and finishes using
> reqsk, it doesn't put reqsk. This will cause reqsk refcnt leaks and
> reqsk obj never gets freed.
>
> Jianlin found this issue when running dccp_memleak.c in a loop, the
> system memory would run out.
>
> dccp_memleak.c:
> int s1 = socket(PF_INET6, 6, IPPROTO_IP);
> bind(s1, &sa1, 0x20);
> listen(s1, 0x9);
> int s2 = socket(PF_INET6, 6, IPPROTO_IP);
> connect(s2, &sa1, 0x20);
> close(s1);
> close(s2);
>
> This patch is to put the reqsk before dccp_v6_conn_request returns,
> just as what tcp_conn_request does.
>
> Reported-by: Jianlin Shi <jishi@redhat.com>
> Signed-off-by: Xin Long <lucien.xin@gmail.com>
Applied and queued up for -stable.
prev parent reply other threads:[~2017-07-27 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 6:19 [PATCH net] dccp: fix a memleak that dccp_ipv6 doesn't put reqsk properly Xin Long
2017-07-27 7:01 ` David Miller [this message]
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=20170727.000122.1772066009028441614.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lucien.xin@gmail.com \
--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).