Re: [PATCH][next] net/mlx4_core: fix memory leaks on error exit path

2017-09-03 Thread David Miller
From: Colin King Date: Thu, 31 Aug 2017 17:30:53 +0100 > From: Colin Ian King > > The structures hca_param and func_cap are not being kfree'd on an error > exit path causing two memory leaks. Fix this by jumping to the existing > free memory

Re: [PATCH][next] net/mlx4_core: fix memory leaks on error exit path

2017-09-03 Thread David Miller
From: Colin King Date: Thu, 31 Aug 2017 17:30:53 +0100 > From: Colin Ian King > > The structures hca_param and func_cap are not being kfree'd on an error > exit path causing two memory leaks. Fix this by jumping to the existing > free memory error exit path. > > Detected by CoverityScan,

Re: [PATCH][next] net/mlx4_core: fix memory leaks on error exit path

2017-09-03 Thread Tariq Toukan
On 31/08/2017 7:30 PM, Colin King wrote: From: Colin Ian King The structures hca_param and func_cap are not being kfree'd on an error exit path causing two memory leaks. Fix this by jumping to the existing free memory error exit path. Detected by CoverityScan,

Re: [PATCH][next] net/mlx4_core: fix memory leaks on error exit path

2017-09-03 Thread Tariq Toukan
On 31/08/2017 7:30 PM, Colin King wrote: From: Colin Ian King The structures hca_param and func_cap are not being kfree'd on an error exit path causing two memory leaks. Fix this by jumping to the existing free memory error exit path. Detected by CoverityScan, CID#1455219, CID#1455224

[PATCH][next] net/mlx4_core: fix memory leaks on error exit path

2017-08-31 Thread Colin King
From: Colin Ian King The structures hca_param and func_cap are not being kfree'd on an error exit path causing two memory leaks. Fix this by jumping to the existing free memory error exit path. Detected by CoverityScan, CID#1455219, CID#1455224 ("Resource Leak")

[PATCH][next] net/mlx4_core: fix memory leaks on error exit path

2017-08-31 Thread Colin King
From: Colin Ian King The structures hca_param and func_cap are not being kfree'd on an error exit path causing two memory leaks. Fix this by jumping to the existing free memory error exit path. Detected by CoverityScan, CID#1455219, CID#1455224 ("Resource Leak") Fixes: c73c8b1e47ca