Re: [PATCH 2/2] init: ensure that /dev/null is (nearly) always available in initramfs
Askar Safin <[email protected]> Sat, 21 Feb 2026 03:16:09 +0300
| Newsgroups | org.kernel.vger.initramfs,dev.linux.lists.patches,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kbuild,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
David Disseldorp <[email protected]>: > It looks as though Bionic has extra logic to handle missing /dev/null > during early boot, although it's dependent on !is_AT_SECURE: > https://cs.android.com/android/platform/superproject/main/+/main:bionic/libc/bionic/libc_init_common.cpp;drc=a7637a8f06f103c53d61a400a6b66f48f2da32be;l=400 > > I think this would be better addressed via documentation (e.g. in Bionic > or ramfs-rootfs-initramfs.rst). Okay, I see, current bionic behavior is good. Okay, I agree that this /dev/null patch is not necessary. -- Askar Safin