Re: [PATCH] rootfs: Use separate mounts lock file

[Anton Mikanovich <amikan@ilbers.de>]

08.07.2021 18:22, Anton Mikanovich wrote:
> MOUNTS_LOCKFILE value inside rootfs.bbclass is overwritten by later
> inherited buildchroot.bbclass. We need to use other value name.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
>   

Applied to next with the following commit message:

> We couldn't identify any resource sharing in any combination of
> buildchroot and rootfses, so a separate lock has been recently
> introduced in e438c8f6 "rootfs: Unmount rootfs mounts if not needed".
>
> This didn't work correctly: MOUNTS_LOCKFILE value inside rootfs.bbclass
> is overwritten by buildchroot.bbclass inherited later.
>
> rootfs_do_mounts and buildchroot_do_mounts would only need to be
> serialized if mount(8) would have unlocked shared resources. At least a
> simple script running 100 mounts and umounts in parallel didn't reveal
> any issues.
>
> Use a different lock file.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
>   

-- 
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov