summaryrefslogtreecommitdiff
path: root/include/crypto/dh.h
diff options
context:
space:
mode:
authorXin Long <lucien.xin@gmail.com>2017-07-26 14:19:09 +0800
committerDavid S. Miller <davem@davemloft.net>2017-07-27 00:01:05 -0700
commit0c2232b0a71db0ac1d22f751aa1ac0cadb950fd2 (patch)
tree2f4a859da0fc7891d6e06e923e2405b16b2938e0 /include/crypto/dh.h
parentd777b2ddbecf509bc61ee4f0fe0d3b5a909d698a (diff)
dccp: fix a memleak that dccp_ipv6 doesn't put reqsk properly
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> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/crypto/dh.h')
0 files changed, 0 insertions, 0 deletions