From: venkata.pyla@toshiba-tsip.com
To: isar-users@googlegroups.com
Cc: venkata pyla <venkata.pyla@toshiba-tsip.com>,
amikan@ilbers.de, jan.kiszka@siemens.com,
kazuhiro3.hayashi@toshiba.co.jp, dinesh.kumar@toshiba-tsip.com,
felix.moessbauer@siemens.com, vijaikumar.kanagarajan@gmail.com
Subject: [PATCH v2 1/2] image.bbclass: remove core files generated in rootfs
Date: Wed, 9 Aug 2023 19:17:02 +0530 [thread overview]
Message-ID: <20230809134703.8475-2-venkata.pyla@toshiba-tsip.com> (raw)
In-Reply-To: <OSYPR01MB55424DA5116B5FA2FC7102BFA412A@OSYPR01MB5542.jpnprd01.prod.outlook.com>
From: venkata pyla <venkata.pyla@toshiba-tsip.com>
Sometimes core dumps are created in rootfs and left in the final image,
and that causes non-reproducible images, so move those files to
${WORKDIR}/temp location and warn the user.
In armhf there is an issue with qemu-user-static that results in
creating core dumps which is reported in Debian upstream [1], meanwhile
move these core dumps outside the rootfs.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040981
Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com>
---
meta/classes/image.bbclass | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 08b6d3d6..9aa6c856 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -461,6 +461,13 @@ do_rootfs_finalize() {
fi
EOSUDO
+ # Sometimes qemu-user-static generates coredumps in chroot, move them
+ # to work temporary directory and inform user about it.
+ for f in $(sudo find ${ROOTFSDIR} -name *.core); do
+ sudo mv "${f}" "${WORKDIR}/temp/"
+ bbwarn "found core dump in rootfs, check it in ${WORKDIR}/temp/${f##*/}"
+ done
+
# Set same time-stamps to the newly generated file/folders in the
# rootfs image for the purpose of reproducible builds.
if [ -n "${SOURCE_DATE_EPOCH}" ]; then
--
2.20.1
next prev parent reply other threads:[~2023-08-09 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 16:35 [PATCH 0/2] Fix reproducible issues in armhf venkata.pyla
2023-08-07 16:35 ` [PATCH 1/2] rootfs.bbclass: clean blkid cache files from rootfs venkata.pyla
2023-08-07 16:58 ` vijai kumar
2023-08-09 4:05 ` Venkata.Pyla
2023-08-09 13:47 ` [PATCH v2 0/2] Fix reproducible issues in armhf venkata.pyla
2023-08-14 11:57 ` vijai kumar
2023-08-15 14:59 ` Uladzimir Bely
2023-08-09 13:47 ` venkata.pyla [this message]
2023-08-09 13:47 ` [PATCH v2 2/2] image.bbclass: clean blkid cache files from rootfs venkata.pyla
2023-08-31 6:16 ` [PATCH 1/2] rootfs.bbclass: " MOESSBAUER, Felix
2023-08-07 16:35 ` [PATCH 2/2] image.bbclass: remove core files generated in rootfs venkata.pyla
2023-08-31 6:21 ` MOESSBAUER, Felix
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=20230809134703.8475-2-venkata.pyla@toshiba-tsip.com \
--to=venkata.pyla@toshiba-tsip.com \
--cc=amikan@ilbers.de \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=vijaikumar.kanagarajan@gmail.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