All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mickaël Salaün" <mic@digikod.net>
To: James Morris <jmorris@namei.org>
Cc: linux-kernel@vger.kernel.org,
	"Serge E . Hallyn" <serge@hallyn.com>,
	"Al Viro" <viro@zeniv.linux.org.uk>,
	"Richard Weinberger" <richard@nod.at>,
	"Andy Lutomirski" <luto@amacapital.net>,
	"Anton Ivanov" <anton.ivanov@cambridgegreys.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Casey Schaufler" <casey@schaufler-ca.com>,
	"Jann Horn" <jannh@google.com>, "Jeff Dike" <jdike@addtoit.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Kees Cook" <keescook@chromium.org>,
	"Michael Kerrisk" <mtk.manpages@gmail.com>,
	"Shuah Khan" <shuah@kernel.org>,
	"Vincent Dagonneau" <vincent.dagonneau@ssi.gouv.fr>,
	kernel-hardening@lists.openwall.com, linux-api@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-security-module@vger.kernel.org, x86@kernel.org,
	"Mickaël Salaün" <mic@linux.microsoft.com>
Subject: Re: [PATCH v21 07/12] landlock: Support filesystem access-control
Date: Wed, 14 Oct 2020 20:52:08 +0200	[thread overview]
Message-ID: <77ea263c-4200-eb74-24b2-9a8155aff9b5@digikod.net> (raw)
In-Reply-To: <alpine.LRH.2.21.2010150504360.26012@namei.org>


On 14/10/2020 20:07, James Morris wrote:
> On Thu, 8 Oct 2020, Mickaël Salaün wrote:
> 
>> +config ARCH_EPHEMERAL_STATES
>> +	def_bool n
>> +	help
>> +	  An arch should select this symbol if it does not keep an internal kernel
>> +	  state for kernel objects such as inodes, but instead relies on something
>> +	  else (e.g. the host kernel for an UML kernel).
>> +
> 
> This is used to disable Landlock for UML, correct?

Yes

> I wonder if it could be 
> more specific: "ephemeral states" is a very broad term.
> 
> How about something like ARCH_OWN_INODES ?

Sounds good. We may need add new ones (e.g. for network socket, UID,
etc.) in the future though.

  reply	other threads:[~2020-10-14 18:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 15:30 [PATCH v21 00/12] Landlock LSM Mickaël Salaün
2020-10-08 15:30 ` [PATCH v21 01/12] landlock: Add object management Mickaël Salaün
2020-10-08 15:30 ` [PATCH v21 02/12] landlock: Add ruleset and domain management Mickaël Salaün
2020-10-08 15:30 ` [PATCH v21 03/12] landlock: Set up the security framework and manage credentials Mickaël Salaün
2020-10-08 15:30 ` [PATCH v21 04/12] landlock: Add ptrace restrictions Mickaël Salaün
2020-10-08 15:30 ` [PATCH v21 05/12] LSM: Infrastructure management of the superblock Mickaël Salaün
2020-10-08 15:30 ` [PATCH v21 06/12] fs,security: Add sb_delete hook Mickaël Salaün
2020-10-08 15:30 ` [PATCH v21 07/12] landlock: Support filesystem access-control Mickaël Salaün
2020-10-14 18:07   ` James Morris
2020-10-14 18:52     ` Mickaël Salaün [this message]
2020-10-14 19:13       ` Mickaël Salaün
2020-10-14 20:46         ` James Morris
2020-10-08 15:30 ` [PATCH v21 08/12] landlock: Add syscall implementations Mickaël Salaün
2020-10-08 15:31 ` [PATCH v21 09/12] arch: Wire up Landlock syscalls Mickaël Salaün
2020-10-08 15:31 ` [PATCH v21 10/12] selftests/landlock: Add initial tests Mickaël Salaün
2020-10-08 15:31 ` [PATCH v21 11/12] samples/landlock: Add a sandbox manager example Mickaël Salaün
2020-10-08 15:31 ` [PATCH v21 12/12] landlock: Add user and kernel documentation Mickaël Salaün
2020-10-15 12:31   ` Mickaël Salaün

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=77ea263c-4200-eb74-24b2-9a8155aff9b5@digikod.net \
    --to=mic@digikod.net \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=arnd@arndb.de \
    --cc=casey@schaufler-ca.com \
    --cc=corbet@lwn.net \
    --cc=jannh@google.com \
    --cc=jdike@addtoit.com \
    --cc=jmorris@namei.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mic@linux.microsoft.com \
    --cc=mtk.manpages@gmail.com \
    --cc=richard@nod.at \
    --cc=serge@hallyn.com \
    --cc=shuah@kernel.org \
    --cc=vincent.dagonneau@ssi.gouv.fr \
    --cc=viro@zeniv.linux.org.uk \
    --cc=x86@kernel.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 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.