On 12/18/25 13:46, Paul Barker wrote:
On Thu, 2025-12-18 at 11:34 +0000, Paul Barker wrote:
On Thu, 2025-12-18 at 12:15 +0200, Dragomir, Daniel via
lists.openembedded.org wrote:
When wic is used in standalone mode, it relies on host tools such as
debugfs. For directory host->image copies into ext* partitions, wic
uses scripted debugfs "-f" input with multiple mkdir/write commands.
Older host debugfs versions (< 1.47) may behave unreliably in this
mode and can silently miss files. This does not affect builds using
debugfs from OE where the version is known to be sufficiently new.
Add a debugfs version check and emit a warning when an older host
debugfs is detected. The warning is shown once per run and does not
alter execution.
If the risk here is silently missing files, resulting in a corrupted
rootfs or worse, I think this should be a hard error.
Consider the case where someone relies on a device having a firewall
enabled, but /etc/nftables.conf is silently missed during construction
of the rootfs ext4 image. That could result in all ports being open.
This failure can only occur when copying directories into an already
created WIC image with an ext* partition. It does not affect image or
rootfs construction.
My understanding is that `wic cp` is a post-creation image manipulation
tool and is not used during rootfs generation or WIC image creation.
It is intended solely for modifying an existing WIC image without
mounting it.
On the kirkstone branch we have e2fsprogs 1.46.5, does the same debugfs
issue apply there or has it been patched?
I built a kirkstone SDK and tested this again: debugfs 1.46.5 works
fine, and all ~1500 files were copied successfully. This issue appears
to affect only version 1.45.
I can send a v2 of the patch to adjust the minimum required version.
Also, do you have any links to upstream bug reports or the commit(s)
that fixed this? I can't find anything relevant in the recent e2fsprogs
release notes.
No, I have not investigated so far why older versions of scripted
debugfs (-f) fail to copy complex directory structures.
Adding a warning was discussed in this thread for a patch I sent to fix
copying directories into a WIC image with an ext* partition. I also
explained how I discovered this behavior on different servers while
testing the fix.
I only tested standalone usage of wic, using host tools from e2fsprogs.
https://lists.openembedded.org/g/openembedded-core/topic/115585333#msg228042
Regards,
Daniel
Best regards,
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#228125):
https://lists.openembedded.org/g/openembedded-core/message/228125
Mute This Topic: https://lists.openembedded.org/mt/116840134/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
