All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: David Miller <davem@davemloft.net>,
	 The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: ELF bugfixes
Date: Thu, 12 Mar 2009 14:43:51 +0100	[thread overview]
Message-ID: <49B91197.6050008@gmail.com> (raw)
In-Reply-To: <20090312.062628.260166400.davem@davemloft.net>

David Miller wrote:
> From: phcoder <phcoder@gmail.com>
> Date: Thu, 12 Mar 2009 14:21:45 +0100
> 
>> I knew it but normally when you parse files normally offsets aren't
>> guaranteed to be aligned. But now it seems that elf parser is
>> written in a way to guarantee at least some alignments. Then this
>> part of patch probably is to be dropped or changed to proper aligned
>> attribute
> 
> These ELF structures DO NOT need the aligned attribute either.
> 
> Nobody, in any source tree anyways, adds either the aligned
> or packed attributes to the core ELF data structures because
> they are absolutely not necessary.  And this includes source
> trees that support basically every CPU type out there.
> 
> Please stop making arbitrary changes, and instead describe on the
> mailing list the exact problem you are trying to solve.  Then,
> implement the solution which you can show is necessary and fully
> understand.
Actually what I was doing now was discussing. If we don't discuss we may 
everyone create our own fork. I previously had problems because some of 
the structures in headers didn't have proper alignment attribute. My 
problem was that grub2 didn't load solaris kernel. Further it revealed 
that the problem wasn't the attributes. I fixed the problem (see the 
rest of my patch) however I decided to submit also that part to prevent 
potential problems in the future. If you're expert with ELF format and 
say that this part will never be needed, it's ok with me but please stay 
respectful and discuss instead of accusing.

-- 

Regards
Vladimir 'phcoder' Serbinenko



       reply	other threads:[~2009-03-12 13:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49B8F067.2040503@gmail.com>
     [not found] ` <20090312.055819.95768237.davem@davemloft.net>
     [not found]   ` <49B90C69.60703@gmail.com>
     [not found]     ` <20090312.062628.260166400.davem@davemloft.net>
2009-03-12 13:43       ` phcoder [this message]
2009-03-12 14:05         ` ELF bugfixes David Miller
2009-03-02  0:35 phcoder
2009-03-11 21:15 ` Robert Millan
2009-03-11 21:21   ` phcoder
2009-03-12  8:23     ` phcoder
2009-03-12  9:07       ` David Miller
2009-03-13 19:14     ` Robert Millan
2009-03-13 20:41       ` phcoder
2009-03-13 20:45         ` David Miller
2009-03-13 20:52           ` phcoder
2009-03-18 10:12             ` Robert Millan
2009-03-18 13:26               ` phcoder
2009-03-21 17:46                 ` Robert Millan
2009-03-21 17:58                   ` phcoder
2009-03-21 18:03                     ` Robert Millan
2009-03-21 18:05                       ` phcoder
2009-03-21 22:03                         ` Robert Millan
2009-03-21 22:49                           ` phcoder
2009-03-21 23:02                             ` Robert Millan
2009-03-21 22:55                           ` Robert Millan
2009-03-13 22:46         ` Robert Millan
2009-03-13 23:01           ` phcoder
2009-03-14 14:53             ` Robert Millan
2009-03-15 21:30           ` phcoder

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=49B91197.6050008@gmail.com \
    --to=phcoder@gmail.com \
    --cc=davem@davemloft.net \
    --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.