From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH 1/2] host/rootfs: remove /proc/kcore bind mounts
Date: Tue, 27 Jan 2026 17:40:16 +0100 [thread overview]
Message-ID: <87a4xzxb4f.fsf@alyssa.is> (raw)
In-Reply-To: <87ike6y4mu.fsf@alyssa.is>
[-- Attachment #1: Type: text/plain, Size: 2847 bytes --]
Alyssa Ross <hi@alyssa.is> writes:
> Alyssa Ross <hi@alyssa.is> writes:
>
>> Demi Marie Obenour <demiobenour@gmail.com> writes:
>>
>>> On 12/15/25 07:27, Alyssa Ross wrote:
>>>> Neither of these services run as root any more, so they don't have
>>>> access to /proc/kcore any more regardless. (Also we don't have
>>>> /proc/kcore on aarch64 so this previously errored there.)
>>>>
>>>> Fixes: 62590b8 ("host/rootfs: Sandbox crosvm")
>>>> Fixes: ec47d36 ("host/rootfs: Sandbox Cloud Hypervisor")
>>>> Signed-off-by: Alyssa Ross <hi@alyssa.is>
>>>> ---
>>>> .../service/vm-services/template/data/service/vhost-user-gpu/run | 1 -
>>>> host/rootfs/image/usr/bin/run-vmm | 1 -
>>>> 2 files changed, 2 deletions(-)
>>>>
>>>> diff --git a/host/rootfs/image/etc/s6-linux-init/run-image/service/vm-services/template/data/service/vhost-user-gpu/run b/host/rootfs/image/etc/s6-linux-init/run-image/service/vm-services/template/data/service/vhost-user-gpu/run
>>>> index b1f9bac..e063a82 100755
>>>> --- a/host/rootfs/image/etc/s6-linux-init/run-image/service/vm-services/template/data/service/vhost-user-gpu/run
>>>> +++ b/host/rootfs/image/etc/s6-linux-init/run-image/service/vm-services/template/data/service/vhost-user-gpu/run
>>>> @@ -40,7 +40,6 @@ bwrap
>>>> --tmpfs /proc/irq
>>>> --remount-ro /proc/irq
>>>> --ro-bind /dev/null /proc/timer_list
>>>> - --ro-bind /dev/null /proc/kcore
>>>> --ro-bind /dev/null /proc/kallsyms
>>>> --ro-bind /dev/null /proc/sysrq-trigger
>>>> --
>>>> diff --git a/host/rootfs/image/usr/bin/run-vmm b/host/rootfs/image/usr/bin/run-vmm
>>>> index 0640239..e30b14c 100755
>>>> --- a/host/rootfs/image/usr/bin/run-vmm
>>>> +++ b/host/rootfs/image/usr/bin/run-vmm
>>>> @@ -113,7 +113,6 @@ bwrap
>>>> --tmpfs /proc/irq
>>>> --remount-ro /proc/irq
>>>> --ro-bind /dev/null /proc/timer_list
>>>> - --ro-bind /dev/null /proc/kcore
>>>> --ro-bind /dev/null /proc/kallsyms
>>>> --ro-bind /dev/null /proc/sysrq-trigger
>>>> --
>>>>
>>>> base-commit: 6ceeb9b236cc50d2bba90068533ca1b7ff229c8b
>>>
>>> /proc/sysrq-trigger and /proc/timer_list can also be dropped,
>>> as they are not accessible to unprivileged users.
>>
>> And what about the others? I see systemd just makes them all read-only
>> — is that only to protect against root? Do we still need to hide
>> /proc/sys, /proc/scsi, /proc/acpi, /proc/fs, and /proc/irq? The only
>> entry I see that's writable by non-root in any of those on my NixOS
>> system is /proc/sys/kernel/ns_last_pid, which doesn't look very harmful…
>
> I'm just going to drop the /proc/scsi bind mount as well for now to fix
> aarch64, but if you still think it's necessary we can instead do the
> kernel config change.
(and same with /proc/acpi, now done)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2026-01-27 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 12:27 [PATCH 1/2] host/rootfs: remove /proc/kcore bind mounts Alyssa Ross
2025-12-15 12:27 ` [PATCH 2/2] host/rootfs: disable CONFIG_PROC_SCSI in kernel Alyssa Ross
2025-12-16 5:15 ` Demi Marie Obenour
2025-12-15 18:36 ` [PATCH 1/2] host/rootfs: remove /proc/kcore bind mounts Demi Marie Obenour
2025-12-16 9:55 ` Alyssa Ross
2025-12-16 12:48 ` Alyssa Ross
2026-01-27 16:40 ` Alyssa Ross [this message]
2026-02-01 19:40 ` Demi Marie Obenour
2025-12-16 10:30 ` Alyssa Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a4xzxb4f.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).