From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10141] New: Squashfs extended attribute failures
Date: Wed, 02 Aug 2017 15:01:43 +0000 [thread overview]
Message-ID: <bug-10141-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10141
Bug ID: 10141
Summary: Squashfs extended attribute failures
Product: buildroot
Version: 2016.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: clayton.shotwell at rockwellcollins.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7136
--> https://bugs.busybox.net/attachment.cgi?id=7136&action=edit
Patch to workaround the issue
I periodically see failures when generating squashfs images with
BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES makedevs option enabled. I
am setting specific capabilities on files which are required for them to run
properly but these settings get dropped sometimes.
I only see this when doing builds on servers with a large number of cores.
Running on small machines seems to hide the bug. I believe the issue is related
to fakeroot but have been unable to verify that for sure. I have checked the
Debian fakeroot package (there is a newer version) but no commits have been
made related to this issue.
The current work around I have in place is to enable erroring out when
generating the squashfs image and to attempt to generate the squashfs 10 times
before failing. Not the best solution but it's better than silently failing.
Attached is the patch with the hack.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-08-02 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 15:01 bugzilla at busybox.net [this message]
2017-08-02 15:06 ` [Buildroot] [Bug 10141] Squashfs extended attribute failures bugzilla at busybox.net
2017-08-02 20:56 ` bugzilla at busybox.net
2017-08-02 21:26 ` bugzilla at busybox.net
2017-08-03 13:54 ` bugzilla at busybox.net
2017-08-08 20:33 ` bugzilla at busybox.net
2017-08-13 21:35 ` bugzilla at busybox.net
2017-08-13 21:50 ` bugzilla at busybox.net
2017-08-15 16:19 ` bugzilla at busybox.net
2018-02-02 21:39 ` bugzilla at busybox.net
2018-02-03 13:56 ` bugzilla at busybox.net
2018-02-05 17:35 ` bugzilla at busybox.net
2018-02-05 18:10 ` 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-10141-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox