From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] part_efi: fix protective_mbr struct allocation
Date: Wed, 12 Feb 2014 18:58:37 +0100 [thread overview]
Message-ID: <20140212185837.153dd8df@lilith> (raw)
In-Reply-To: <CAOMZO5Cb8ACpuKjsfh24RdnZ7UrL+Lu0TpqS4TP0sgtOT3WHjw@mail.gmail.com>
Hi Fabio,
On Wed, 12 Feb 2014 15:33:17 -0200, Fabio Estevam <festevam@gmail.com>
wrote:
> Hi Albert,
>
> On Wed, Feb 12, 2014 at 2:33 PM, Albert ARIBAUD
> <albert.u.boot@aribaud.net> wrote:
>
> >> What about:
> >>
> >> p_mbr = calloc(1, sizeof(*p_mbr)) ?
> >
> > I don't like the idea of setting p_mbr based on *p_mbr at a time where
> > p_mbr is still undefined. I know that from a C standard perspective
> > this is ok, but I'd rather simply not run any risk and pass sizeof
> > the struct type, not a (non-existent) dereferenced 'value'.
>
> At least in kernel this is the preferred way.
>
> According to Documentation/CodingStyle:
>
> "Chapter 14: Allocating memory
>
> 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."
I still don't like it, but it makes sense indeed.
> Regards,
>
> Fabio Estevam
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-02-12 17:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 14:40 [U-Boot] [PATCH] part_efi: fix protective_mbr struct allocation Hector Palacios
2014-02-12 14:43 ` Fabio Estevam
2014-02-12 16:33 ` Albert ARIBAUD
2014-02-12 17:33 ` Fabio Estevam
2014-02-12 17:58 ` Albert ARIBAUD [this message]
2014-02-12 15:55 ` Lukasz Majewski
2014-02-12 16:24 ` Palacios, Hector
2014-02-12 16:30 ` Albert ARIBAUD
2014-02-12 16:48 ` Palacios, Hector
2014-02-12 20:45 ` Lukasz Majewski
2014-02-13 2:23 ` Albert ARIBAUD
2014-02-19 8:19 ` Lukasz Majewski
2014-02-19 10:08 ` Albert ARIBAUD
2014-02-19 10:15 ` Albert ARIBAUD
2014-02-19 12:52 ` Palacios, Hector
2014-02-19 14:14 ` Albert ARIBAUD
2014-02-19 14:25 ` Lukasz Majewski
2014-02-19 14:38 ` Albert ARIBAUD
2014-02-19 15:11 ` Lukasz Majewski
2014-02-19 14:22 ` Tom Rini
2014-02-19 15:10 ` Lukasz Majewski
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=20140212185837.153dd8df@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.