All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] disk: fix unaligned access in efi partitions
Date: Fri, 29 Mar 2013 09:57:05 -0600	[thread overview]
Message-ID: <5155B9D1.80407@wwwdotorg.org> (raw)
In-Reply-To: <1620255.73TLX5Us40@ax5200p>

On 03/29/2013 09:13 AM, Marc Dietrich wrote:
> On Friday 29 March 2013 13:32:26 Albert ARIBAUD wrote:
>> On Fri, 29 Mar 2013 12:28:58 +0100, Marc Dietrich <marvin24@gmx.de> wrote:
>>> start_sect is not aligned to a 4 byte boundary thus causing exceptions
>>> on ARM platforms. Access this field via the get_unaligned macro.

>>> -		le32_to_cpu(part->start_sect) == 1UL) {
>>> +		le32_to_cpu(get_unaligned(&part->start_sect)) == 1UL) {

>> Also, beside the asm/unaligned.h file I gave as an example, other header
>> files in include/linux/unaligned/ exist that provide alignment-related
>> macros, notably with _le and _be versions. Maybe you can find one that
>> combines the effects of both le32_to_cpu() and get_unaligned()?
> 
> I looks like get_unaligned does the job for us already, so we can leave the 
> le32_to_cpu out. But I cannot test it here because of missing big endian 
> machine with efi and my two brain halfs are already swapped until confusion 
> (start_sect is defined as _le32). 
> 
> Albert, I like to get a fix for this into 2013.04 if possible. Maybe someone 
> with more endian experience can look at it quickly.

Looking at include/linux/unaligned/generic.h, I think you can just use:

__get_unaligned_le(&part->start_sect) == 1UL

I don't believe the __le32 marking of the start_sect field will have any
effect, since the implementation of __get_unaligned_le accesses the
variable byte-by-byte.

      reply	other threads:[~2013-03-29 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 11:28 [U-Boot] [PATCH] disk: fix unaligned access in efi partitions Marc Dietrich
2013-03-29 12:32 ` Albert ARIBAUD
2013-03-29 15:13   ` Marc Dietrich
2013-03-29 15:57     ` Stephen Warren [this message]

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=5155B9D1.80407@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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.