From: Paul Barker <paul@pbarker.dev>
To: daniel.dragomir@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] wic/engine: warn about old host debugfs for standalone directory copy
Date: Thu, 18 Dec 2025 11:34:31 +0000 [thread overview]
Message-ID: <494e78c31feaaec6cf5c4c96ad3cbf45ac19dd5d.camel@pbarker.dev> (raw)
In-Reply-To: <20251218101524.703244-1-daniel.dragomir@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
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.
On the kirkstone branch we have e2fsprogs 1.46.5, does the same debugfs
issue apply there or has it been patched?
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2025-12-18 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 10:15 [OE-core][PATCH] wic/engine: warn about old host debugfs for standalone directory copy Daniel Dragomir
2025-12-18 11:34 ` Paul Barker [this message]
2025-12-18 11:46 ` Paul Barker
2025-12-18 13:48 ` Daniel Dragomir
2026-02-09 18:12 ` Ross Burton
2026-02-10 13:02 ` Daniel Dragomir
2026-01-09 17:45 ` [OE-core][PATCH v2] " Daniel Dragomir
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=494e78c31feaaec6cf5c4c96ad3cbf45ac19dd5d.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=daniel.dragomir@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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