All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9746] New: ext4 image generated by Buildroot is not working properly with U-Boot
Date: Tue, 14 Mar 2017 14:08:25 +0000	[thread overview]
Message-ID: <bug-9746-163@https.bugs.busybox.net/> (raw)

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.

             reply	other threads:[~2017-03-14 14:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 14:08 bugzilla at busybox.net [this message]
2017-07-19 20:27 ` [Buildroot] [Bug 9746] ext4 image generated by Buildroot is not working properly with U-Boot bugzilla at busybox.net

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=bug-9746-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.