All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Kees Cook <keescook@chromium.org>
Cc: James Morris <james.l.morris@oracle.com>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Yama: allow access for the current ptrace parent
Date: Mon, 5 Dec 2016 11:13:34 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LRH.2.20.1612051113190.12163@namei.org> (raw)
In-Reply-To: <20161202234943.GA116779@beast>

On Fri, 2 Dec 2016, Kees Cook wrote:

> James, can you pull this into your -next tree? I made a tiny fix to the
> comment style, but it is otherwise identical to what Josh sent originally.

Applied, thanks!


-- 
James Morris
<jmorris@namei.org>

  reply	other threads:[~2016-12-05  0:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 23:49 [PATCH] Yama: allow access for the current ptrace parent Kees Cook
2016-12-05  0:13 ` James Morris [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-12-01  1:24 Josh Stone
2016-12-02 23:27 ` Kees Cook
2016-12-05 19:13   ` Josh Stone
2016-12-05 19:38     ` Kees Cook

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.20.1612051113190.12163@namei.org \
    --to=jmorris@namei.org \
    --cc=james.l.morris@oracle.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.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.