Re: [PATCH v6 0/6] Restore downstream mounts compatibility

[Henning Schild <henning.schild@siemens.com>]

Am Thu, 9 Sep 2021 11:13:37 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:

> 08.09.2021 18:48, Henning Schild wrote:
> > Is that what was recently applied to next?
> >
> > We are still having issues some issues with current next and are
> > trying to understand things.
> >
> > One thing i did find is that next contains
> > 57b3dc055837 ("Revert "rootfs: Unmount rootfs mounts if not
> > needed"")
> >
> > which reverts
> > e438c8f62b9a ("rootfs: Unmount rootfs mounts if not needed")
> >
> > this guy
> > 5e563ac4b707 ("rootfs: Use separate mounts lock file")
> >
> > was a fix on top of e438c8f62b9a and now also potentially deserves a
> > revert.
> >
> > Henning  
> 
> Yes, that was already applied to next.
> What kind of issues do you have, are there any logs?

I just wrote an email on that. Some builds are getting stuck and it
seems that ROOTFS/isar.lock is part of the problem. The layer does have
a few recipes that use buildchroot_do_mounts but nothing with locking.
Investigation is ongoing, but if you know the problem that builds get
stuck at do_deploy_deb that would be interesting to us.

> The lockfile changed by 5e563ac4b707 was gone with revert, because it 
> was introduced by e438c8f62b9a.

I see 57b3dc05583743781cad3b46bec915a601d2fbe2 in fact reverts multiple
commits.

It would be helpful to revert single commits in reverse order and _not_
remove the part of the commit message that contains the sha of the
reverted commit.

Henning