public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Paul Barker <paul@pbarker.dev>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3 1/3] overlayfs: Fix the QA skip for ignored mounts
Date: Thu, 15 Jan 2026 22:18:30 +0100	[thread overview]
Message-ID: <30338f3a-39e5-4e2a-b7a6-120142ecd6b3@gmail.com> (raw)
In-Reply-To: <4c89ce299fb704382932a367669852b0617c9232.camel@pbarker.dev>

This is actually a good point, but I'm not sure how WARN_QA/ERROR_QA can 
be utilized here. WARN_QA/ERROR_QA expects one keyword, but 
OVERLAYFS_QA_SKIP expects a flag per mount unit. If we simplify it to 
WARN_QA/ERROR_QA, then we enable/disable the QA for all mount units. 
This will be a breaking change though, but it sounds like it might 
simplify things a bit. Do you think that would be better to use 
WARN_QA/ERROR_QA instead of current mechanism?

As for the check performed twice question. The file list is populated / 
expanded at the parsing stage, but the actual QA is performed at the 
rootfs postprocessing, because the overlayfs class works on a recipe 
basis, so to check if everything is provided the whole file system is 
needed.

Slava

On 15.01.2026 14:41, Paul Barker wrote:
> On Wed, 2026-01-14 at 18:54 +0000, Vyacheslav Yurkov via
> lists.openembedded.org wrote:
>> From: Vyacheslav Yurkov <uvv.mail@gmail.com>
>>
>> The supressing of QA check for mounts should happens twice, at parsing stage
>> and at rootfs postprocessing. If the mount point is configured to be skipped,
>> but it is still present in the configuration (machine or distro), then the
>> parsing would complain.
> Thanks for respinning these patches.
>
> I'm still unsure why the check is being performed twice. Are we checking
> for different errors at parse time and rootfs time?
>
> Also, can we convert this to fit in our existing QA framework so that it
> is controlled by the WARN_QA/ERROR_QA variables?
>
>> Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
>> ---
>>   meta/lib/oe/overlayfs.py | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/lib/oe/overlayfs.py b/meta/lib/oe/overlayfs.py
>> index 5a5ea03d45..3805746d90 100644
>> --- a/meta/lib/oe/overlayfs.py
>> +++ b/meta/lib/oe/overlayfs.py
>> @@ -33,7 +33,8 @@ def unitFileList(d):
>>       # check that we have required mount points set first
>>       requiredMountPoints = d.getVarFlags('OVERLAYFS_WRITABLE_PATHS')
>>       for mountPoint in requiredMountPoints:
>> -        if mountPoint not in overlayMountPoints:
>> +        qaSkip = (d.getVarFlag("OVERLAYFS_QA_SKIP", mountPoint) or "").split()
>> +        if mountPoint not in overlayMountPoints and not "mount-configured" in qaSkip:
>>               bb.fatal("Missing required mount point for OVERLAYFS_MOUNT_POINT[%s] in your MACHINE configuration" % mountPoint)
>>   
>>       for mountPoint in overlayMountPoints:
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#229369): https://lists.openembedded.org/g/openembedded-core/message/229369
>> Mute This Topic: https://lists.openembedded.org/mt/117266570/1826184
>> Group Owner: openembedded-core+owner@lists.openembedded.org
>> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [paul@pbarker.dev]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>



  reply	other threads:[~2026-01-15 21:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 18:54 [PATCH v3 0/3] Overlayfs improvements uvv.mail
2026-01-14 18:54 ` [PATCH v3 1/3] overlayfs: Fix the QA skip for ignored mounts uvv.mail
2026-01-15 13:41   ` [OE-core] " Paul Barker
2026-01-15 21:18     ` Vyacheslav Yurkov [this message]
2026-01-14 18:54 ` [PATCH v3 2/3] oe-selftest: overlayfs: Make the test more deterministic uvv.mail
2026-01-15 13:53   ` [OE-core] " Paul Barker
2026-01-14 18:54 ` [PATCH v3 3/3] oe-selftest: overlayfs: Add a demo case for /etc uvv.mail
2026-01-15 14:01   ` [OE-core] " Paul Barker

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=30338f3a-39e5-4e2a-b7a6-120142ecd6b3@gmail.com \
    --to=uvv.mail@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    /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