public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: wharms@bfs.de
Cc: alsa-devel@alsa-project.org,
	Fengguang Wu <fengguang.wu@intel.com>,
	kernel-janitors@vger.kernel.org,
	Ian Minett <ian_minett@creativelabs.com>
Subject: Re: sound/pci/hda/patch_ca0132.c: potential null dereference 'dma_engine'
Date: Fri, 21 Sep 2012 12:00:40 +0000	[thread overview]
Message-ID: <s5hk3vnpouv.wl%tiwai@suse.de> (raw)
In-Reply-To: <505C53EA.2090206@bfs.de>

At Fri, 21 Sep 2012 13:47:54 +0200,
walter harms wrote:
> 
> 
> 
> Am 21.09.2012 13:46, schrieb Takashi Iwai:
> > At Fri, 21 Sep 2012 18:22:42 +0800,
> > Fengguang Wu wrote:
> >>
> >> Hi Ian,
> >>
> >> FYI, there are new smatch warnings show up in
> >>
> >> commit 0b37d4c7982442730061a737c16939e8cc363861
> >> Author:     Ian Minett <ian_minett@creativelabs.com>
> >> Commit:     Takashi Iwai <tiwai@suse.de>
> >> CommitDate: Fri Sep 21 09:54:29 2012 +0200
> >>
> >> + sound/pci/hda/patch_ca0132.c:2056 dspxfr_image() error: potential null dereference 'dma_engine'.  (kzalloc returns null)
> >> + sound/pci/hda/patch_ca0132.c:2056 dspxfr_image() error: we previously assumed 'dma_engine' could be null (see line 1963)
> > 
> > Fixed with the patch below.  Thanks!
> > 
> > 
> > Takashi
> > 
> > => > Subject: [PATCH] ALSA: hda - Fix NULL dereference in error path of patch_ca0132.c
> > 
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > ---
> >  sound/pci/hda/patch_ca0132.c | 6 ++----
> >  1 file changed, 2 insertions(+), 4 deletions(-)
> > 
> > diff --git a/sound/pci/hda/patch_ca0132.c b/sound/pci/hda/patch_ca0132.c
> > index 5c6a056..03f57c9 100644
> > --- a/sound/pci/hda/patch_ca0132.c
> > +++ b/sound/pci/hda/patch_ca0132.c
> > @@ -1960,10 +1960,8 @@ static int dspxfr_image(struct hda_codec *codec,
> >  		return -EINVAL;
> >  
> >  	dma_engine = kzalloc(sizeof(*dma_engine), GFP_KERNEL);
> > -	if (!dma_engine) {
> > -		status = -ENOMEM;
> > -		goto exit;
> > -	}
> > +	if (!dma_engine)
> > +		return -ENOMEM;
> >  	memset((void *)dma_engine, 0, sizeof(*dma_engine));
> >  
> 
> Why do you need that memset() ? kzalloc() should fill the buffer with 0.

True.


Takashi

      reply	other threads:[~2012-09-21 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 10:22 sound/pci/hda/patch_ca0132.c: potential null dereference 'dma_engine' Fengguang Wu
2012-09-21 11:46 ` Takashi Iwai
2012-09-21 11:47 ` walter harms
2012-09-21 12:00   ` Takashi Iwai [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=s5hk3vnpouv.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=fengguang.wu@intel.com \
    --cc=ian_minett@creativelabs.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=wharms@bfs.de \
    /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