From: Al Viro <viro@zeniv.linux.org.uk>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: Paul Moore <paul@paul-moore.com>,
selinux@vger.kernel.org, linux-fsdevel@vger.kernel.org,
torvalds@linux-foundation.org, brauner@kernel.org, jack@suse.cz,
kees@kernel.org, casey@schaufler-ca.com,
linux-security-module@vger.kernel.org,
john.johansen@canonical.com
Subject: Re: [PATCH 31/39] convert selinuxfs
Date: Mon, 22 Sep 2025 14:46:23 +0100 [thread overview]
Message-ID: <20250922134623.GS39973@ZenIV> (raw)
In-Reply-To: <CAEjxPJ4Ez1oYXa4hEcSLSrO+ikLN0kgrWQc+2n2K7wWoy7a7pQ@mail.gmail.com>
On Mon, Sep 22, 2025 at 08:34:02AM -0400, Stephen Smalley wrote:
> Is there a reason why these patches weren't sent to selinux list in
> the first place?
Will Cc on the next posting of that series.
> In any event, yes, Android userspace (in particular the Android init
> program) relies on /sys/fs/selinux/null at a point where /dev/null
> does not yet exist [1]. Hence, I don't believe we can drop it since it
> would break userspace.
Pity. Oh, well...
prev parent reply other threads:[~2025-09-22 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250920074156.GK39973@ZenIV>
[not found] ` <20250920074759.3564072-1-viro@zeniv.linux.org.uk>
[not found] ` <20250920074759.3564072-31-viro@zeniv.linux.org.uk>
[not found] ` <CAHC9VhTRsQtncKx4bkbkSqVXpZyQLHbvKkcaVO-ss21Fq36r+Q@mail.gmail.com>
[not found] ` <20250921214110.GN39973@ZenIV>
2025-09-22 2:45 ` [PATCH 31/39] convert selinuxfs Paul Moore
2025-09-22 12:34 ` Stephen Smalley
2025-09-22 13:46 ` Al Viro [this message]
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=20250922134623.GS39973@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=jack@suse.cz \
--cc=john.johansen@canonical.com \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=torvalds@linux-foundation.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.
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).