aboutsummaryrefslogtreecommitdiffstats
path: root/include/uapi/linux/if_fddi.h
diff options
context:
space:
mode:
authorYing Xue <ying.xue@windriver.com>2014-04-25 10:44:15 +0800
committerDavid S. Miller <davem@davemloft.net>2014-04-27 19:08:06 -0400
commit22e7987ae7d8d13beeaf0717215800f7e803ddcf (patch)
treebf796b7b8020397483e5a2ed4bc6b48dd7a6cb86 /include/uapi/linux/if_fddi.h
parentqlge: Convert /n to \n (diff)
downloadlinux-dev-22e7987ae7d8d13beeaf0717215800f7e803ddcf.tar.xz
linux-dev-22e7987ae7d8d13beeaf0717215800f7e803ddcf.zip
tipc: fix a possible memory leak
The commit a8b9b96e959f3c035af20b1bd2ba67b0b7269b19 ("tipc: fix race in disc create/delete") leads to the following static checker warning: net/tipc/discover.c:352 tipc_disc_create() warn: possible memory leak of 'req' The risk of memory leak really exists in practice. Especially when it's failed to allocate memory for "req->buf", tipc_disc_create() doesn't free its allocated memory, instead just directly returns with ENOMEM error code. In this situation, memory leak, of course, happens. Reported-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Ying Xue <ying.xue@windriver.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/uapi/linux/if_fddi.h')
0 files changed, 0 insertions, 0 deletions