Re: [PATCH 2/2] fs: don't reset userspace_init_fs when PID 1 stops sharing it
From: Akisaira
Date: Sat Nov 21 2026 - 13:10:04 EST
On Thu, Nov 19, 2026 at 02:25:02PM +0100, Christian Brauner wrote:
> There are a couple of fixes to not leave stale state behind but it seems
> that there is legitimate userspace out there that does need this. So
> stop resetting userspace_init_fs for now. I can probably rework this to
> something sane but I'm not sure it's worth it. Kthreads and
> usermodehelpers keep using what PID 1 left behind, just like they kept
> using init_fs before PID 1 got its own fs_struct. Keep the notice
> though but downgrade it to pr_info().
Thanks for the quick fix. I applied both patches on top of v7.4-rc3
instead of my local workaround and booted Android 17 on arm64
(Qualcomm SC8280XP).
Android boots cleanly with no init property denials, "VFS: Pid 1 stopped
sharing filesystem state" appears once at info level, and post-unshare
direct firmware loads from /vendor/firmware (ath11k, Adreno SQE/GMU, QCA
Bluetooth) continue to work. I didn't exercise the pivot_root() path in
1/2 since Android doesn't use pivot_root(), so tagging 2/2 only.
Tested-by: Akisaira <akisaira@xxxxxxxxxxx>