From: Jann Horn <jannh@google.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: "James Morris" <jmorris@namei.org>,
"Serge E . Hallyn" <serge@hallyn.com>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Andy Lutomirski" <luto@amacapital.net>,
"Anton Ivanov" <anton.ivanov@cambridgegreys.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Casey Schaufler" <casey@schaufler-ca.com>,
"Jeff Dike" <jdike@addtoit.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Kees Cook" <keescook@chromium.org>,
"Michael Kerrisk" <mtk.manpages@gmail.com>,
"Richard Weinberger" <richard@nod.at>,
"Shuah Khan" <shuah@kernel.org>,
"Vincent Dagonneau" <vincent.dagonneau@ssi.gouv.fr>,
"Kernel Hardening" <kernel-hardening@lists.openwall.com>,
"Linux API" <linux-api@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"kernel list" <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
"the arch/x86 maintainers" <x86@kernel.org>,
"Mickaël Salaün" <mic@linux.microsoft.com>
Subject: Re: [PATCH v24 12/12] landlock: Add user and kernel documentation
Date: Sat, 21 Nov 2020 08:00:00 +0100 [thread overview]
Message-ID: <CAG48ez0S1_jd0YzXZ9tx94gU0sw-WeXgG336d=3YP7+iZvRgaA@mail.gmail.com> (raw)
In-Reply-To: <20201112205141.775752-13-mic@digikod.net>
On Thu, Nov 12, 2020 at 9:52 PM Mickaël Salaün <mic@digikod.net> wrote:
> This documentation can be built with the Sphinx framework.
>
> Cc: James Morris <jmorris@namei.org>
> Cc: Jann Horn <jannh@google.com>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Serge E. Hallyn <serge@hallyn.com>
> Signed-off-by: Mickaël Salaün <mic@linux.microsoft.com>
> Reviewed-by: Vincent Dagonneau <vincent.dagonneau@ssi.gouv.fr>
Reviewed-by: Jann Horn <jannh@google.com>
next prev parent reply other threads:[~2020-11-21 7:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 20:51 [PATCH v24 00/12] Landlock LSM Mickaël Salaün
2020-11-12 20:51 ` [PATCH v24 01/12] landlock: Add object management Mickaël Salaün
2020-11-21 7:00 ` Jann Horn
2020-11-21 10:11 ` Mickaël Salaün
2020-11-12 20:51 ` [PATCH v24 02/12] landlock: Add ruleset and domain management Mickaël Salaün
2020-11-20 1:52 ` James Morris
2020-11-21 7:00 ` Jann Horn
2020-11-21 9:45 ` Mickaël Salaün
2020-11-12 20:51 ` [PATCH v24 03/12] landlock: Set up the security framework and manage credentials Mickaël Salaün
2020-11-12 20:51 ` [PATCH v24 04/12] landlock: Add ptrace restrictions Mickaël Salaün
2020-11-12 20:51 ` [PATCH v24 05/12] LSM: Infrastructure management of the superblock Mickaël Salaün
2020-11-12 20:51 ` [PATCH v24 06/12] fs,security: Add sb_delete hook Mickaël Salaün
2020-11-12 20:51 ` [PATCH v24 07/12] landlock: Support filesystem access-control Mickaël Salaün
2020-11-21 7:00 ` Jann Horn
2020-11-21 10:06 ` Mickaël Salaün
2020-11-23 19:44 ` Jann Horn
2020-11-23 21:16 ` Mickaël Salaün
2020-11-23 21:19 ` Jann Horn
2020-11-12 20:51 ` [PATCH v24 08/12] landlock: Add syscall implementations Mickaël Salaün
2020-11-21 7:00 ` Jann Horn
2020-11-12 20:51 ` [PATCH v24 09/12] arch: Wire up Landlock syscalls Mickaël Salaün
2020-11-12 20:51 ` [PATCH v24 10/12] selftests/landlock: Add user space tests Mickaël Salaün
2020-11-12 20:51 ` [PATCH v24 11/12] samples/landlock: Add a sandbox manager example Mickaël Salaün
2020-11-12 20:51 ` [PATCH v24 12/12] landlock: Add user and kernel documentation Mickaël Salaün
2020-11-21 7:00 ` Jann Horn [this message]
2020-11-24 2:38 ` James Morris
2020-11-17 5:37 ` [PATCH v24 00/12] Landlock LSM James Morris
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='CAG48ez0S1_jd0YzXZ9tx94gU0sw-WeXgG336d=3YP7+iZvRgaA@mail.gmail.com' \
--to=jannh@google.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=arnd@arndb.de \
--cc=casey@schaufler-ca.com \
--cc=corbet@lwn.net \
--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@digikod.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 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).