Control: reassign -1 systemd 236-1
Control: forcemerge 885325 -1

Hello,

Marius Vollmer [2018-01-10 10:59 +0200]:
> Version: 1:7.6p1-2
> 
> Mounting or unmounting filesystems from within a ssh session used to
> affect all processes, but now it only affects ssh sessions (all of them,
> not just the one doing the mounts/unmounts).

This can be reproduced more easily with a bind mount:

  # mount -o bind /etc /mnt
  # grep /mnt /proc/1/mounts

Some more background: This is a very recent regression. Our debian-testing
image rebuild on Dec 18 was still fine, and the regression started on the image
rebuild on Dec 25.

  - openssh itself did not change in between

  - We found this regression through udisks2, but Marius showed it can be
    reproduced without udisks. I also confirmed that upgrading udisks2 to 2.7.5
    and rebooting does not change the behaviour.

  - The most obvious and likely change during that time period was systemd 263
    which migrated into testing on Dec 23 [2]. And indeed upgrading just
    systemd (and its dependencies) and rebooting introduces the bug. So it's
    likely a regression in systemd itself, possibly related to changed
    implementation of RuntimeDirectory= or so, to keep that private? But I
    don't see any "magic" option in ssh.service that would warrant this
    behaviour.

With that in mind, I looked for existing bug reports, and it turns out that
this was already reported as #885325 and fixed upstream [3]. So merging bugs.
Glad to see that this will be fixed soon!

Martin

[1] https://tracker.debian.org/news/893521
[2] https://tracker.debian.org/news/896130
[3] https://github.com/systemd/systemd/pull/7763

Attachment: signature.asc
Description: PGP signature

Reply via email to