From: dancol <dancol@dancol.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Lokesh Gidra <lokeshgidra@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
James Morris <jmorris@namei.org>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Casey Schaufler <casey@schaufler-ca.com>,
Eric Biggers <ebiggers@kernel.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Eric Paris <eparis@parisplace.org>,
Kees Cook <keescook@chromium.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
KP Singh <kpsingh@google.com>,
David Howells <dhowells@redhat.com>,
Anders Roxell <anders.roxell@linaro.org>,
Sami Tolvanen <samitolvanen@google.com>,
Matthew Garrett <matthewgarrett@google.com>,
Aaron Goidel <acgoide@tycho.nsa.gov>,
Randy Dunlap <rdunlap@infradead.org>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
YueHaibing <yuehaibing@huawei.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Alexei Starovoitov <ast@kernel.org>,
Alexey Budankov <alexey.budankov@linux.intel.com>,
Adrian Reber <areber@redhat.com>,
Aleksa Sarai <cyphar@cyphar.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
kaleshsingh@google.com, calin@google.com, surenb@google.com,
jeffv@google.com, kernel-team@android.com, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
hch@infradead.org, Daniel Colascione <dancol@google.com>,
Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH v13 2/4] fs: add LSM-supporting anon-inode interface
Date: Wed, 06 Jan 2021 21:42:20 -0500 [thread overview]
Message-ID: <f7dfe33a4d0f9c27f3e25f72a988201a@dancol.org> (raw)
In-Reply-To: <CAHC9VhScpFVtxzU_nUDUc4zGT7+EZKFRpYAm+Ps5vd2AjKkaMQ@mail.gmail.com>
On 2021-01-06 21:09, Paul Moore wrote:
> Is it necessary to pass both the context_inode pointer and the secure
> boolean? It seems like if context_inode is non-NULL then one could
> assume that a secure anonymous inode was requested; is there ever
> going to be a case where this is not true?
The converse isn't true though: it makes sense to ask for a secure inode
with a NULL context inode.
next prev parent reply other threads:[~2021-01-07 3:17 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 1:53 [PATCH v13 0/4] SELinux support for anonymous inodes and UFFD Lokesh Gidra
2020-11-12 1:53 ` Lokesh Gidra
2020-11-12 1:53 ` [PATCH v13 1/4] security: add inode_init_security_anon() LSM hook Lokesh Gidra
2020-11-12 1:53 ` Lokesh Gidra
2020-11-12 1:53 ` [PATCH v13 2/4] fs: add LSM-supporting anon-inode interface Lokesh Gidra
2020-11-12 1:53 ` Lokesh Gidra
2021-01-07 2:09 ` Paul Moore
2021-01-07 2:09 ` Paul Moore
2021-01-07 2:42 ` dancol [this message]
2021-01-07 3:05 ` Paul Moore
2021-01-07 3:05 ` Paul Moore
2021-01-07 2:43 ` Lokesh Gidra
2021-01-07 2:43 ` Lokesh Gidra
2021-01-07 3:08 ` Paul Moore
2021-01-07 3:08 ` Paul Moore
2020-11-12 1:53 ` [PATCH v13 3/4] selinux: teach SELinux about anonymous inodes Lokesh Gidra
2020-11-12 1:53 ` Lokesh Gidra
2021-01-07 3:03 ` Paul Moore
2021-01-07 3:03 ` Paul Moore
2021-01-07 3:55 ` Lokesh Gidra
2021-01-07 3:55 ` Lokesh Gidra
2021-01-07 22:30 ` Paul Moore
2021-01-07 22:30 ` Paul Moore
2021-01-07 22:40 ` Lokesh Gidra
2021-01-07 22:40 ` Lokesh Gidra
2021-01-08 19:35 ` Stephen Smalley
2021-01-08 19:35 ` Stephen Smalley
2021-01-08 20:17 ` Lokesh Gidra
2021-01-08 20:17 ` Lokesh Gidra
2021-01-08 21:23 ` Stephen Smalley
2021-01-08 21:23 ` Stephen Smalley
2021-01-08 21:31 ` Lokesh Gidra
2021-01-08 21:31 ` Lokesh Gidra
2021-01-08 20:58 ` Paul Moore
2021-01-08 20:58 ` Paul Moore
2020-11-12 1:53 ` [PATCH v13 4/4] userfaultfd: use secure anon inodes for userfaultfd Lokesh Gidra
2020-11-12 1:53 ` Lokesh Gidra
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=f7dfe33a4d0f9c27f3e25f72a988201a@dancol.org \
--to=dancol@dancol.org \
--cc=aarcange@redhat.com \
--cc=acgoide@tycho.nsa.gov \
--cc=akpm@linux-foundation.org \
--cc=alexey.budankov@linux.intel.com \
--cc=anders.roxell@linaro.org \
--cc=areber@redhat.com \
--cc=ast@kernel.org \
--cc=calin@google.com \
--cc=casey@schaufler-ca.com \
--cc=christian.brauner@ubuntu.com \
--cc=cyphar@cyphar.com \
--cc=dancol@google.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=ebiggers@google.com \
--cc=ebiggers@kernel.org \
--cc=eparis@parisplace.org \
--cc=hch@infradead.org \
--cc=jeffv@google.com \
--cc=jmorris@namei.org \
--cc=joel@joelfernandes.org \
--cc=kaleshsingh@google.com \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=kpsingh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lokeshgidra@google.com \
--cc=matthewgarrett@google.com \
--cc=paul@paul-moore.com \
--cc=rdunlap@infradead.org \
--cc=samitolvanen@google.com \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.com \
--cc=surenb@google.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yuehaibing@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.