From: Amit Choudhary <amit2030@yahoo.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org
Subject: Re: Hopefully, kmalloc() will always succeed, but if it doesn't then....
Date: Sun, 22 Oct 2006 21:00:17 -0700 (PDT) [thread overview]
Message-ID: <20061023040018.28823.qmail@web55602.mail.re4.yahoo.com> (raw)
In-Reply-To: <adalkn7j2th.fsf@cisco.com>
--- Roland Dreier <rdreier@cisco.com> wrote:
> > struct mixart_enum_connector_resp *connector;
> > struct mixart_audio_info_req *audio_info_req;
> > struct mixart_audio_info_resp *audio_info;
> >
> > connector = kmalloc(sizeof(*connector), GFP_KERNEL);
> > audio_info_req = kmalloc(sizeof(*audio_info_req), GFP_KERNEL);
> > audio_info = kmalloc(sizeof(*audio_info), GFP_KERNEL);
> > if (! connector || ! audio_info_req || ! audio_info) {
> > err = -ENOMEM;
> > goto __error;
> > }
>
> This is not a bug. All of the pointers are initialized, and if
Yes, this is not a bug. Although the case for arrays go unnoticed by gcc. Something like this:
char *abcd[20];
int i;
for (i = 0; i < 20; i++) {
abcd[i] = kmalloc(10, GFP_KERNEL);
if (!abcd[i])
goto error;
}
error:
for (i = 0; i < 20; i++)
kfree(abcd[i]);
-Amit
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-10-23 4:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 19:58 Amit Choudhary
2006-10-22 20:22 ` Pekka Enberg
2006-10-22 21:09 ` Jan Engelhardt
2006-10-22 23:09 ` Amit Choudhary
2006-10-23 0:25 ` Roland Dreier
2006-10-23 4:00 ` Amit Choudhary [this message]
2006-10-22 22:51 ` Amit Choudhary
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=20061023040018.28823.qmail@web55602.mail.re4.yahoo.com \
--to=amit2030@yahoo.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rdreier@cisco.com \
/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
all inboxes | Powered by JetHome®