[Buildroot] [Bug 9746] New: ext4 image generated by Buildroot is not working properly with U-Boot

[Buildroot] [Bug 9746] New: ext4 image generated by Buildroot is not working properly with U-Boot

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=9746

            Bug ID: 9746
           Summary: ext4 image generated by Buildroot is not working
                    properly with U-Boot
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: sebastien.szymanski at armadeus.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

The ext4 image generated by Buildroot can make U-Boot crash once you wrote the
image and then try to write a file into it. Notice this is hardware independent
as it is reproducible on the U-Boot sandbox. See [1] for more details and the
steps to reproduce it.
U-Boot works fine if the ext4 image is generated with mkfs.ext4
(Hence my patch to use mkfs.ext4 instead of genextfs [2])

[1] https://lists.denx.de/pipermail/u-boot/2017-January/278827.html
[2] https://patchwork.ozlabs.org/patch/734525/

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 9746] ext4 image generated by Buildroot is not working properly with U-Boot

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=9746

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
This is fixed now that we use mkfs.ext4, since commit
https://git.buildroot.org/buildroot/commit/fs/ext2?id=67aaa90d3bbe6ad5b5ffa9e66cdb0a1928448eb9.

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.