All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fix packing issue of machine_mmap_entry
Date: Tue, 23 Oct 2007 07:34:58 +0200	[thread overview]
Message-ID: <20071023053458.GB19186@thorin> (raw)
In-Reply-To: <471D0F5B.20805@t-online.de>

On Mon, Oct 22, 2007 at 11:00:11PM +0200, Christian Franke wrote:
> --- grub2.orig/include/grub/i386/pc/init.h	2007-07-22 01:32:23.000000000 +0200
> +++ grub2/include/grub/i386/pc/init.h	2007-10-13 21:25:24.000000000 +0200
> @@ -40,10 +40,14 @@ grub_uint32_t grub_get_eisa_mmap (void);
>  struct grub_machine_mmap_entry
>  {
>    grub_uint32_t size;
> -  grub_uint64_t addr;
> +  grub_uint64_t addr; /* must be at offset 4, see startup.S */ 
>    grub_uint64_t len;
>    grub_uint32_t type;
> -};
> +} __attribute__((packed));

Looks fine to me (I suppose we would have the same problem on x86_64).

> +/* Compile time assert to check packing */
> +typedef char ASSERT_sizeof_grub_machine_mmap_entry[
> +  sizeof (struct grub_machine_mmap_entry) == 4+8+8+4 ? 1 : -1];

Nice, I didn't know you could do compile time assertion in C.  But is it
really necessary to check for gcc bugs?  That __attribute__((packed)) can
only have the expected effect, right?  Besides, in this case maybe it'd
be better to use autoconf.

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)



  reply	other threads:[~2007-10-23  6:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 21:00 [PATCH] Fix packing issue of machine_mmap_entry Christian Franke
2007-10-23  5:34 ` Robert Millan [this message]
2007-10-23  8:09   ` Christian Franke
2007-11-09 14:00 ` Marco Gerards
2007-11-09 19:55   ` Christian Franke
2007-11-10 15:55     ` Marco Gerards
2007-11-18  7:11       ` Robert Millan

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=20071023053458.GB19186@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.org \
    /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.