public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] FAT12 regression after 8d48c92b45aea91e2a2be90f2ed93677e85526f1
Date: Thu, 26 Jan 2017 07:40:21 +0100	[thread overview]
Message-ID: <588999D5.4000704@denx.de> (raw)
In-Reply-To: <20170125232546.GA93084@bluezbox.com>

Hello Oleksandr,

added Stefan and Tom to cc...

Am 26.01.2017 um 00:25 schrieb Oleksandr Tymoshenko:
> Hello,
>
> U-Boot 2017.01 and master branch is broken on BeagleBone Black
> with boot partition formatted as FAT12, it hang after printing "Loading
> u-boot.img" message. I bisected regression to this patch:
>
> http://lists.denx.de/pipermail/u-boot/2016-December/276305.html

Yep, I detected this issue for another am335x based board, too,
see thread here:'
http://lists.denx.de/pipermail/u-boot/2017-January/279078.html

But I did not found time to look into it...

> This code simplification is not going to work on architectures
> with strict alignment requirements:
>
> +               ret = FAT2CPU16(*(__u16 *)(mydata->fatbuf + off16));
>
> fatbuf is a pointer to __u8 and off16 can take any values so
> mydata->fatbuf + off16 is not guaranteed to be 16-bits aligned
> and 16-bit access to non-aligned address will cause exception.

Good explanation! Thanks!

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2017-01-26  6:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 23:25 [U-Boot] FAT12 regression after 8d48c92b45aea91e2a2be90f2ed93677e85526f1 Oleksandr Tymoshenko
2017-01-26  6:40 ` Heiko Schocher [this message]
2017-01-26 17:55 ` [U-Boot] [PATCH] fs/fat: Fix unaligned __u16 reads for FAT12 access Brüns, Stefan
2017-01-26 19:50   ` Oleksandr Tymoshenko

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=588999D5.4000704@denx.de \
    --to=hs@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox