From: Julia Lawall <julia@diku.dk>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
kernel-janitors@vger.kernel.org, linux@arm.linux.org.uk,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH 1/5] arch/arm: Correct NULL test
Date: Mon, 28 Dec 2009 17:51:15 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0912281747570.6928@ask.diku.dk> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE19090200F461@mi8nycmail19.Mi8.com>
On Mon, 28 Dec 2009, H Hartley Sweeten wrote:
> On Sunday, December 27, 2009 3:08 PM, Julia Lawall wrote:
> >>> dbgfs_chan = kmalloc(sizeof(*dbgfs_state) * num_dma_channels,
> >>> GFP_KERNEL);
> >>> - if (!dbgfs_state)
> >>> + if (!dbgfs_chan)
> >>> goto err_alloc;
> >> Shouldn't the malloc line read:
> >>
> >> ... = kmalloc(sizeof(*dbgfs_chan) * ...)
> >> ^^^^^^^^^^
> >>
> >> ?
> >
> > Good point, thanks. I will send a revised patch.
>
> Wouldn't this be clearer?
>
> ... = kmalloc(sizeof(struct dentry) * ...)
Documentation/CodingStyle thinks otherwise:
"The preferred form for passing a size of a struct is the following:
p = kmalloc(sizeof(*p), ...);
The alternative form where struct name is spelled out hurts readability
and introduces an opportunity for a bug when the pointer variable type is
changed but the corresponding sizeof that is passed to a memory allocator
is not."
And actually, in this case, sizeof(struct dentry) would be wrong, because
the type of dbgfs_chan is struct dentry **, not struct dentry *. What is
wanted is an array of pointers.
julia
next prev parent reply other threads:[~2009-12-28 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 21:26 Julia Lawall
2009-12-27 21:51 ` Uwe Kleine-König
2009-12-27 22:07 ` Julia Lawall
2009-12-28 16:24 ` H Hartley Sweeten
2009-12-28 16:51 ` Julia Lawall [this message]
2009-12-28 17:09 ` H Hartley Sweeten
2009-12-27 22:25 ` Julia Lawall
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.0912281747570.6928@ask.diku.dk \
--to=julia@diku.dk \
--cc=hartleys@visionengravers.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=u.kleine-koenig@pengutronix.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
all inboxes | Powered by JetHome®