Bug#779902: /tmp can be mounted as tmpfs against user's will

[Didier Roche]

Le 20/03/2015 08:39, Michael Biebl a écrit :
> Am 20.03.2015 um 08:26 schrieb Didier Roche:
>> Hey,
>>
>> Attaching the patch (which tries to be less intrusive with mounts, only
>> affecting /tmp) that I pinged on IRC for better tracking.
>> Tested under multiple configurations. /tmp isn't mounted as tmpfs
>> neither at boot, nor after a service restart having PrivateTmp. Enabling
>> the tmp mount unit now ensures that it's started at boot, before
>> services having PrivateTmp.
> Hi Didier,

Hey Michael,
>
> thanks for the patch. I had something like this in mind.
> We could be extra nice and only add the After=tmp.mount if tmp.mount is
> actually enabled, because we only need the After ordering in this case.
> But that's mostly a cosmetic issue and I'm happy to ship the patch as is.

That's a nice idea. It needs testing though to ensure that the fstab 
generator generated the right enablement for that unit (in case the 
tmpfs config was done in fstab). Also, we need to ensure that any later 
enablement of that unit, this is taken into account by new units. Not 
sure I'll have time to test this properly today, will be more early next 
week if needed though.

Didier