Files
systemd/src/basic
Mike Yuan 01184496a2 virt: revert to detect chroot by comparing with / rather than /proc/PID/root
This partially reverts d6267b9b18

So, arch-chroot currently uses a rather cursed setup:
it sets up a PID namespace, but mounts /proc/ from the outside
into the chroot tree, and then call chroot(2), essentially
making it somewhere between chroot(8) and a full-blown
container. Hence, the PID dirs in /proc/ reveal the outer world.
The offending commit switched chroot detection to compare
/proc/1/root and /proc/OUR_PID/root, exhibiting the faulty behavior
where the mentioned environment now gets deemed to be non-chroot.

Now, this is very much an issue in arch-chroot. However,
if /proc/ is to be properly associated with the pidns,
then we'd treat it as a container and no longer a chroot.
Also, the previous logic feels more readable and more
honestly reported errors in proc_mounted(). Hence I opted
for reverting the change here. Still note that the culprit
(once again :/) lies in the arch-chroot's pidns impl, not
systemd.

Fixes https://gitlab.archlinux.org/archlinux/packaging/packages/systemd/-/issues/54
2025-09-19 13:09:34 +02:00
..
2025-05-25 10:06:07 +02:00
2025-05-25 10:06:07 +02:00
2025-09-19 15:33:15 +09:00
2025-05-25 10:06:07 +02:00
2025-09-17 09:45:47 +02:00
2025-06-02 17:39:43 +02:00
2025-06-02 17:39:43 +02:00
2025-09-19 08:39:32 +02:00
2025-09-19 08:39:32 +02:00
2025-07-27 13:14:05 +02:00
2025-09-19 15:33:17 +09:00
2025-06-23 23:11:44 +09:00
2025-05-25 10:06:07 +02:00
2025-05-25 10:06:07 +02:00
2025-06-02 18:05:45 +02:00
2025-05-25 10:06:07 +02:00
2025-05-25 10:06:07 +02:00
2025-05-25 10:06:07 +02:00
2025-06-17 11:44:50 +02:00
2025-07-27 13:14:05 +02:00
2025-05-25 10:06:07 +02:00
2025-05-25 10:06:07 +02:00
2025-07-26 05:00:02 +09:00
2025-05-25 10:06:07 +02:00
2025-05-25 10:06:07 +02:00
2025-05-25 10:06:07 +02:00
2025-05-25 10:06:07 +02:00
2025-05-25 10:06:07 +02:00
2025-05-25 10:06:07 +02:00