[buildd-tools-devel] Bug#726375: Bug#726375: [Pkg-systemd-maintainers] Bug#726375: schroot: Fails during umount on system booted with systemd

[Christoph Berg]

Re: Roger Leigh 2014-03-13 <20140313221817.GF30912 at codelibre.net>
> Thanks for the confirmation that the patch helps.
> 
> I'll consider applying the patch.  However, I won't be doing this
> without a good justification for why systemd has broken behaviour
> which has worked fine for over a decade.  This isn't a schroot bug.
> This breaks any use of bind mounts for anyone doing a similar
> thing.
> 
> Changing to use "shared" mountpoints is a massively breaking
> change, and I've not seen anything to justify it.  How many admins
> are going to be screwed over by this?  What exactly makes use of
> this changed behaviour, if anything?

Hi Roger,

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739593#54 has an
explanation.

I'm also not happy that systemd changes this kernel default to some
other "default" - maybe "shared" is the better mount propagation
default, but does that need to be "fixed" by the init system?

Anyway, strictly speaking, schroot is also "buggy" without that change
- the admin could have made that change themselves, and then the
situation would be the same. I guess everyone doing mounts will need
to learn more about the namespacing and propagation mechanism in
Linux, and make sure the program will work independenly from what
settings are made on the parent filesystem.

Christoph
-- 
cb at df7cb.de | http://www.df7cb.de/