public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Bruens <stefan.bruens@rwth-aachen.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ext4: crash when writing a file
Date: Sun, 11 Dec 2016 18:10:25 +0100	[thread overview]
Message-ID: <14836236.mPPJId54W8@pebbles.site> (raw)
In-Reply-To: <4f253a2a-2be3-321e-11d8-a6a3a354cc19@armadeus.com>

On Dienstag, 29. November 2016 16:23:28 CET S?bastien Szymanski wrote:
> On 11/29/2016 03:38 PM, Br?ns, Stefan wrote:
> > On Dienstag, 29. November 2016 14:10:54 CET S?bastien Szymanski wrote:
> >>> Btw, which u-boot version are you using?
> >> 
> >> I first noticed the issue on U-Boot 2016.05 so I rebase on master from
> >> http://git.denx.de/u-boot.git
> >> 
> >> Regards,
> > 
> > That still doesn't make clear on which version you see this issue.
> > 2016.05?
> > Master? Which date/tag/hash?
> > 
> > U-Boot 2016.11 has received a huge number of fixes, and current master has
> > some more.
> 
> Sorry for being unclear.
> 
> I was working with U-Boot 2016.05 (commit
> aeaec0e682f45b9e0c62c522fafea353931f73ed) when I saw this issue. Then, I
> rebased on current master (commit
> e94793c844a40606252f2e3f6428063e057b3fd2) and I still see this issue.
> 
> I hope it's clearer now.
> 
> Regards,
> 
> > Regards,
> > 
> > Stefan
> 
> S?bastien Szymanski

So to restate what you are doing:

1. You have a partitioned MMC, where the 2nd partition starts at block 
264192/0x40800
2. You load a 93958144 byte (~90 MB) file via TFTP to ${loadaddr}
3. You write this partition image to 0x40800 using "mmc write"
4. You load another 5345128 byte (5 MB) file via TFTP to $loadaddr
5. You try to write this file to the 2nd partition, which now is ext4 
formatted, and already contains a file of the same name, i.e. boot/opos6ul-
linux.bin


Actually, I can't reproduce the crash. Maybe you have corrupted part of the 
memory when loading the image, e.g. overwritten part of u-boot or its heap.

Things you can try:
a) reboot the system after loading/writing the partion image.
b) checking the fs contents after the reboot, e.g "ls mmc 0:2 /boot" 
c) overwriting opos6ul-linux.bin with just a single byte, e.g "ext4write mmc 
0:2 0x0 /boot/opos6ul-linux.bin 1"
d) transferring back the partition image to your host and running fschk on it

You may also able to reproduce this using the u-boot sandbox.

Kind regards,

Stefan



-- 
Stefan Br?ns  /  Bergstra?e 21  /  52062 Aachen
home: +49 241 53809034     mobile: +49 151 50412019
work: +49 2405 49936-424

  reply	other threads:[~2016-12-11 17:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29  9:50 [U-Boot] ext4: crash when writing a file Sébastien Szymanski
2016-11-29 12:14 ` Brüns, Stefan
2016-11-29 13:10   ` Sébastien Szymanski
2016-11-29 14:38     ` Brüns, Stefan
2016-11-29 15:23       ` Sébastien Szymanski
2016-12-11 17:10         ` Stefan Bruens [this message]
2017-01-20 17:32   ` Sébastien Szymanski
2017-01-23 16:38     ` Brüns, Stefan
2017-01-24  9:58       ` Sébastien Szymanski

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=14836236.mPPJId54W8@pebbles.site \
    --to=stefan.bruens@rwth-aachen.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