From: Al Viro <viro@ZenIV.linux.org.uk>
To: Kees Cook <keescook@chromium.org>
Cc: James Morris <jmorris@namei.org>, Joe Perches <joe@perches.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Jonathan Corbet <corbet@lwn.net>,
Kalle Valo <kvalo@codeaurora.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Guenter Roeck <linux@roeck-us.net>, Jiri Slaby <jslaby@suse.com>,
Paul Moore <pmoore@redhat.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Casey Schaufler <casey@schaufler-ca.com>,
Andreas Gruenbacher <agruenba@redhat.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Ulf Hansson <ulf.hansson@linaro.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 5/6] fs: provide function to report enum strings
Date: Tue, 12 Apr 2016 23:31:17 +0100 [thread overview]
Message-ID: <20160412223117.GP25498@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1460480085-32263-6-git-send-email-keescook@chromium.org>
On Tue, Apr 12, 2016 at 09:54:44AM -0700, Kees Cook wrote:
> Providing human-readable (and audit-parsable) strings for the READING_*
> enums is needed by some LSMs.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> fs/exec.c | 19 +++++++++++++++++++
> include/linux/fs.h | 1 +
> 2 files changed, 20 insertions(+)
What the devil is that doing in fs/exec.c, of all places?
next prev parent reply other threads:[~2016-04-12 22:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 16:54 [PATCH v4 0/6] LSM: LoadPin for kernel file loading restrictions Kees Cook
2016-04-12 16:54 ` [PATCH v4 1/6] string_helpers: add kstrdup_quotable Kees Cook
2016-04-12 21:13 ` Serge E. Hallyn
2016-04-12 16:54 ` [PATCH v4 2/6] string_helpers: add kstrdup_quotable_cmdline Kees Cook
2016-04-12 21:19 ` Serge E. Hallyn
2016-04-13 11:53 ` Andy Shevchenko
2016-04-12 16:54 ` [PATCH v4 3/6] string_helpers: add kstrdup_quotable_file Kees Cook
2016-04-12 21:24 ` Serge E. Hallyn
2016-04-12 16:54 ` [PATCH v4 4/6] Yama: consolidate error reporting Kees Cook
2016-04-12 21:26 ` Serge E. Hallyn
2016-04-12 16:54 ` [PATCH v4 5/6] fs: provide function to report enum strings Kees Cook
2016-04-12 21:30 ` Serge E. Hallyn
2016-04-12 22:31 ` Al Viro [this message]
2016-04-12 22:38 ` Kees Cook
2016-04-13 11:53 ` Mimi Zohar
2016-04-12 16:54 ` [PATCH v4 6/6] LSM: LoadPin for kernel file loading restrictions Kees Cook
2016-04-12 21:44 ` Serge E. Hallyn
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=20160412223117.GP25498@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=agruenba@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=casey@schaufler-ca.com \
--cc=corbet@lwn.net \
--cc=jmorris@namei.org \
--cc=joe@perches.com \
--cc=jslaby@suse.com \
--cc=keescook@chromium.org \
--cc=kvalo@codeaurora.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=mchehab@osg.samsung.com \
--cc=pmoore@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=serge@hallyn.com \
--cc=ulf.hansson@linaro.org \
--cc=vkuznets@redhat.com \
--cc=zohar@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox