From: Julia Lawall <julia@diku.dk>
To: Takashi Iwai <tiwai@suse.de>
Cc: linuxppc-dev@ozlabs.org,
Johannes Berg <johannes@sipsolutions.net>,
kernel-janitors@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] sound/aoa: Add kmalloc NULL tests
Date: Fri, 31 Jul 2009 08:31:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0907310831160.13462@ask.diku.dk> (raw)
In-Reply-To: <s5hws5pid6u.wl%tiwai@suse.de>
On Fri, 31 Jul 2009, Takashi Iwai wrote:
> At Thu, 30 Jul 2009 16:29:54 +0200 (CEST),
> Julia Lawall wrote:
> >
> > On Thu, 30 Jul 2009, Johannes Berg wrote:
> >
> > > On Thu, 2009-07-30 at 16:11 +0200, Julia Lawall wrote:
> > > > From: Julia Lawall <julia@diku.dk>
> > > >
> > > > Check that the result of kzalloc is not NULL before a dereference.
> > >
> > > > irq_client = kzalloc(sizeof(struct pmf_irq_client),
> > > > GFP_KERNEL);
> > > > + if (!irq_client) {
> > > > + err = -ENOMEM;
> > > > + printk(KERN_ERR "snd-aoa: gpio layer failed to"
> > > > + " register %s irq (%d)\n", name, err);
> > > > + goto out_unlock;
> > > > + }
> > >
> > > Looks good, thanks, but I'd really drop the printk if only to not have
> > > the string there, that doesn't really seem interesting.
> >
> > The printk is based on similar error handling code a few lines later:
>
> But another problem is that the same error message is reused although
> the error condition is totally different. The kzalloc NULL isn't
> about the registration error. So, it's rather confusing.
>
> However, for this particular error path, I agree with Johannes; we can
> skip the error message since the error code ENOMEM is obvious.
OK, I will send a new patch.
julia
next prev parent reply other threads:[~2009-07-31 6:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 14:11 [PATCH 5/5] sound/aoa: Add kmalloc NULL tests Julia Lawall
2009-07-30 14:17 ` Johannes Berg
2009-07-30 14:29 ` Julia Lawall
2009-07-31 6:22 ` Takashi Iwai
2009-07-31 6:31 ` Julia Lawall [this message]
2009-07-31 6:32 ` Julia Lawall
2009-07-31 8:16 ` Takashi Iwai
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=Pine.LNX.4.64.0907310831160.13462@ask.diku.dk \
--to=julia@diku.dk \
--cc=alsa-devel@alsa-project.org \
--cc=johannes@sipsolutions.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tiwai@suse.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