public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manu Abraham <abraham.manu@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: mchehab@infradead.org, v4l-dvb-maintainer@linuxtv.org,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/media/dvb/bt8xx/dst_ca.c: fix 2 memory leaks
Date: Sat, 11 Mar 2006 22:33:50 +0400	[thread overview]
Message-ID: <4413180E.5020105@gmail.com> (raw)
In-Reply-To: <20060311184409.GB21864@stusta.de>

Adrian Bunk wrote:
> On Sat, Mar 11, 2006 at 05:12:13PM +0100, Adrian Bunk wrote:
>   
>> On Sat, Mar 11, 2006 at 07:53:34PM +0400, Manu Abraham wrote:
>>     
>>> Yeah, it is better indeed. Would you mind if i schedule this for a 
>>> little while later, since i have a couple of other fixes/additions as well ?
>>>       
>> There's no need to hurry since the whole problem is only a small memory 
>> leak in a very unlikely case.
>>     
>
> But when you'll apply it, please used the improved version below (based 
> on a suggestion by Ingo Oeser).
>
>   

Ok, i will apply the same thing.


> cu
> Adrian
>
>   

Thanks,
Manu

> The Coverity checker spotted that thre was a memory leak if the second
> or third kmalloc() failed.
>
> Besides this, I've also consolidated the three error handlings into one 
> and removed the unneeded casts.
>
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> ---
>
>  drivers/media/dvb/bt8xx/dst_ca.c |   19 +++++++++----------
>  1 file changed, 9 insertions(+), 10 deletions(-)
>
> --- linux-2.6.16-rc5-mm3-full/drivers/media/dvb/bt8xx/dst_ca.c.old	2006-03-11 14:36:59.000000000 +0100
> +++ linux-2.6.16-rc5-mm3-full/drivers/media/dvb/bt8xx/dst_ca.c	2006-03-11 15:28:26.000000000 +0100
> @@ -473,18 +473,17 @@ static int dst_ca_ioctl(struct inode *in
>  	void __user *arg = (void __user *)ioctl_arg;
>  	int result = 0;
>  
> -	if ((p_ca_message = (struct ca_msg *) kmalloc(sizeof (struct ca_msg), GFP_KERNEL)) == NULL) {
> -		dprintk(verbose, DST_CA_ERROR, 1, " Memory allocation failure");
> -		return -ENOMEM;
> -	}
> -	if ((p_ca_slot_info = (struct ca_slot_info *) kmalloc(sizeof (struct ca_slot_info), GFP_KERNEL)) == NULL) {
> -		dprintk(verbose, DST_CA_ERROR, 1, " Memory allocation failure");
> -		return -ENOMEM;
> -	}
> -	if ((p_ca_caps = (struct ca_caps *) kmalloc(sizeof (struct ca_caps), GFP_KERNEL)) == NULL) {
> +	p_ca_message = kmalloc(sizeof (struct ca_msg), GFP_KERNEL);
> +	p_ca_slot_info = kmalloc(sizeof (struct ca_slot_info), GFP_KERNEL);
> +	p_ca_caps = kmalloc(sizeof (struct ca_caps), GFP_KERNEL);
> +
> +
> +	if (!p_ca_message || !p_ca_slot_info || !p_ca_caps) {
>  		dprintk(verbose, DST_CA_ERROR, 1, " Memory allocation failure");
> -		return -ENOMEM;
> +		result = -ENOMEM;
> +		goto free_mem_and_exit;
>  	}
> +
>  	/*	We have now only the standard ioctl's, the driver is upposed to handle internals.	*/
>  	switch (cmd) {
>  	case CA_SEND_MSG:
>
>
>   


      reply	other threads:[~2006-03-11 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-11 15:11 [2.6 patch] drivers/media/dvb/bt8xx/dst_ca.c: fix 2 memory leaks Adrian Bunk
2006-03-11 15:53 ` Manu Abraham
2006-03-11 16:12   ` Adrian Bunk
2006-03-11 18:44     ` Adrian Bunk
2006-03-11 18:33       ` Manu Abraham [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=4413180E.5020105@gmail.com \
    --to=abraham.manu@gmail.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=v4l-dvb-maintainer@linuxtv.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