From: James Morris <jmorris@namei.org>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Joe Perches <joe@perches.com>,
John Johansen <john.johansen@canonical.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Paul Moore <paul@paul-moore.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
Kentaro Takeda <takedakn@nttdata.co.jp>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
selinux@tycho.nsa.gov
Subject: Re: [-next PATCH] security: use octal not symbolic permissions
Date: Wed, 13 Jun 2018 06:32:34 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1806130631400.13763@namei.org> (raw)
In-Reply-To: <fcac609a-08a8-b3ab-a69e-2e65e2ad63e9@schaufler-ca.com>
On Mon, 11 Jun 2018, Casey Schaufler wrote:
> If you want to break this up by security module I would take
> the Smack part as soon as James does the tree update. If James
> wants to take the whole thing at once you can add my:
>
> Acked-by: Casey Schaufler <casey@schaufler-ca.com>
>
> for the Smack changes.
It's probably simplest for me to take them as one patch.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2018-06-12 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 19:01 Joe Perches
2018-06-11 20:07 ` Casey Schaufler
2018-06-12 20:32 ` James Morris [this message]
2018-06-12 21:12 ` Paul Moore
2018-06-12 21:29 ` John Johansen
2018-06-12 21:36 ` Mimi Zohar
2018-06-13 0:29 ` Joe Perches
2018-06-13 15:49 ` Paul Moore
2018-06-13 16:04 ` Joe Perches
2018-06-13 16:19 ` Paul Moore
2018-06-13 19:30 ` Joe Perches
2018-06-13 19:57 ` Paul Moore
2018-06-13 21:14 ` Casey Schaufler
2018-06-13 21:22 ` Paul Moore
2018-06-13 15:19 ` Serge E. Hallyn
2018-06-13 23:49 ` Joe Perches
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=alpine.LRH.2.21.1806130631400.13763@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eparis@parisplace.org \
--cc=joe@perches.com \
--cc=john.johansen@canonical.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serge@hallyn.com \
--cc=takedakn@nttdata.co.jp \
--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
all inboxes | Powered by JetHome®