From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ext4: massive corruption with ext4write
Date: Thu, 26 Jul 2018 15:32:06 +0200 [thread overview]
Message-ID: <20180726133206.E4EFA240032@gemini.denx.de> (raw)
In-Reply-To: <6444410.LK6WS1oxaM@awilliams-suse>
Dear Aaron,
In message <6444410.LK6WS1oxaM@awilliams-suse> you wrote:
>
...
> While mainline U-Boot does not support Octeon, we have our own fork of it that
> I maintain. I am using the 2018.07 release with only a few minor changes
> around the periphery to support the older version of U-Boot Octeon is based
> off of. I found one source of the corruption in ext4fs_get_new_inode_no()
> where it is setting bgd->bg_itable_unused without cpu_to_le16, which causes
> this to break on big-endian systems. Additionally, for 64-bit filesystems,
> bg_itable_unused_high never gets set.
So when you know the/one cause of the problems, and how to fix it,
then why don't you submit a patch?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Computers are not intelligent. They only think they are.
next prev parent reply other threads:[~2018-07-26 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 2:35 [U-Boot] ext4: Issue with ext4write Aaron Williams
2018-07-24 6:15 ` [U-Boot] ext4: massive corruption " Aaron Williams
2018-07-24 6:25 ` Aaron Williams
2018-07-24 9:45 ` Marek Vasut
2018-07-25 2:05 ` Aaron Williams
2018-07-25 7:55 ` [U-Boot] Cavium Octeon support for u-boot Chris Packham
2018-08-21 6:07 ` Aaron Williams
2018-08-21 12:57 ` Alexander Graf
2018-08-21 22:00 ` Suneel Garapati
2018-08-22 7:46 ` Alexander Graf
2018-07-26 13:32 ` Wolfgang Denk [this message]
2018-07-24 10:53 ` [U-Boot] ext4: massive corruption with ext4write Aaron Williams
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=20180726133206.E4EFA240032@gemini.denx.de \
--to=wd@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