lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 11 Jan 2012 08:59:10 -0800
From:	Greg KH <greg@...ah.com>
To:	Ananth N Mavinakayanahalli <ananth@...ibm.com>
Cc:	Jiang Liu <liuj97@...il.com>, linux-kernel@...r.kernel.org,
	Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
	"David S . Miller" <davem@...emloft.net>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Jim Keniston <jkenisto@...ibm.com>,
	Jun Ma <harry.majun@...wei.com>, stable@...r.kernel.org,
	Jiang Liu <jiang.liu@...wei.com>
Subject: Re: [PATCH] kprobes: fix a memory leak in function
 pre_handler_kretprobe()

On Wed, Jan 11, 2012 at 09:42:33PM +0530, Ananth N Mavinakayanahalli wrote:
> On Wed, Jan 11, 2012 at 11:21:51PM +0800, Jiang Liu wrote:
> > From: Jiang Liu <liuj97@...il.com>
> > 
> > In function pre_handler_kretprobe(), the allocated kretprobe_instance object
> > will be leaked if the entry_handler callback returns non-zero. This may cause
> > all the preallocated kretprobe_instance objects exhausted. This issue could be
> > reproduced by changing samples/kprobes/kretprobe_example.c to probe 
> > "mutex_unlock". And the fix is straight forward, just put the allocated 
> > kretprobe_instance object back onto the free_instances list. 
> > 
> > Signed-off-by: Jiang Liu <jiang.liu@...wei.com>
> > Acked-by: Jim Keniston <jkenisto@...ibm.com>
> > Acked-by: Ananth N Mavinakayanahalli <ananth@...ibm.com>
> 
> Thank you Jiang. I think the correct ID for stable is now
> stable@...r.kernel.org.

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ