From: John Johansen <john.johansen@canonical.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
James Morris <james.l.morris@oracle.com>,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] Yama: access current->comm directly
Date: Mon, 30 Jul 2012 14:21:33 -0700 [thread overview]
Message-ID: <5016FADD.1030503@canonical.com> (raw)
In-Reply-To: <20120730165848.GA28288@www.outflux.net>
On 07/30/2012 09:58 AM, Kees Cook wrote:
> The core ptrace access checking routine already holds the task lock,
> so there is no need to use get_task_comm() which just tries to take the
> lock again. Drop its use and access current->comm directly.
>
> Reported-by: Fengguang Wu <fengguang.wu@intel.com>
> Suggested-by: Oleg Nesterov <oleg@redhat.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
yep, looks good
Acked-by: John Johansen <john.johansen@canonical.com>
> ---
> security/yama/yama_lsm.c | 6 ++----
> 1 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/security/yama/yama_lsm.c b/security/yama/yama_lsm.c
> index 83554ee..20a68ca 100644
> --- a/security/yama/yama_lsm.c
> +++ b/security/yama/yama_lsm.c
> @@ -279,12 +279,10 @@ static int yama_ptrace_access_check(struct task_struct *child,
> }
>
> if (rc) {
> - char name[sizeof(current->comm)];
> + /* task_lock is held by the caller, so use comm directly. */
> printk_ratelimited(KERN_NOTICE
> "ptrace of pid %d was attempted by: %s (pid %d)\n",
> - child->pid,
> - get_task_comm(name, current),
> - current->pid);
> + child->pid, current->comm, current->pid);
> }
>
> return rc;
>
next prev parent reply other threads:[~2012-07-30 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 16:58 Kees Cook
2012-07-30 21:21 ` John Johansen [this message]
2012-07-30 21:50 ` Alan Cox
2012-07-30 23:04 ` 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=5016FADD.1030503@canonical.com \
--to=john.johansen@canonical.com \
--cc=james.l.morris@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.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
Powered by JetHome