From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH] ubifs-img: Force cross-compile usage
Date: Wed, 7 Jul 2021 19:46:27 +0300 [thread overview]
Message-ID: <20210707164627.204630-1-amikan@ilbers.de> (raw)
mkfs.ubifs creates an empty image at armhf target with error:
>Value too large for defined data type
This error is throwed by readdir(glibc 2.28+) inside 32-bit QEMU on
64-bit kernel with ext4 filesystem. It happens because of incorrect
filesystem metadata storage if _FILE_OFFSET_BITS=64 is not set.
Upstream bugs
QEMU: https://gitlab.com/qemu-project/qemu/-/issues/263
glibc: https://sourceware.org/bugzilla/show_bug.cgi?id=23960
kernel: https://bugzilla.kernel.org/show_bug.cgi?id=205957
maillist: https://lkml.org/lkml/2018/12/27/155
It was already fixed in mtd-utils v2.1.3 by enabling LFS
(commit e91700286ff531f344f4d9a1f1c96c501bfeadad), but until this
version will be released and backported to Debian we need a hotfix to
make Isar to use host arch mkfs.ubifs.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
meta/classes/ubifs-img.bbclass | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/meta/classes/ubifs-img.bbclass b/meta/classes/ubifs-img.bbclass
index e422b46..7d78a79 100644
--- a/meta/classes/ubifs-img.bbclass
+++ b/meta/classes/ubifs-img.bbclass
@@ -12,6 +12,10 @@ UBIFS_IMAGE_FILE ?= "${IMAGE_FULLNAME}.ubifs.img"
IMAGER_INSTALL += "mtd-utils"
+# glibc bug 23960 https://sourceware.org/bugzilla/show_bug.cgi?id=23960
+# should not use QEMU on armhf target with mkfs.ubifs < v2.1.3
+ISAR_CROSS_COMPILE_armhf = "1"
+
# Generate ubifs filesystem image
do_ubifs_image() {
rm -f '${DEPLOY_DIR_IMAGE}/${UBIFS_IMAGE_FILE}'
--
2.20.1
next reply other threads:[~2021-07-07 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 16:46 Anton Mikanovich [this message]
2021-09-07 12:32 ` Anton Mikanovich
2021-09-08 9:28 ` Henning Schild
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=20210707164627.204630-1-amikan@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
/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