All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH] Yama: handle 32-bit userspace prctl
Date: Wed, 05 Sep 2012 15:06:03 -0700	[thread overview]
Message-ID: <5047CCCB.1000108@canonical.com> (raw)
In-Reply-To: <20120827183813.GA23991@www.outflux.net>

On 08/27/2012 11:38 AM, Kees Cook wrote:
> When running a 64-bit kernel and receiving prctls from a 32-bit
> userspace, the "-1" used as an unsigned long will end up being
> misdetected. The kernel is looking for 0xffffffffffffffff instead of
> 0xffffffff. Since prctl lacks a distinct compat interface, Yama needs
> to handle this translation itself. As such, support either value as
> meaning PR_SET_PTRACER_ANY, to avoid breaking the ABI for 64-bit.
> 
> Signed-off-by: Kees Cook <keescook@chromium.org>
> Cc: stable@vger.kernel.org
> ---
>  security/yama/yama_lsm.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/security/yama/yama_lsm.c b/security/yama/yama_lsm.c
> index 0cc99a3..dcd6178 100644
> --- a/security/yama/yama_lsm.c
> +++ b/security/yama/yama_lsm.c
> @@ -143,7 +143,7 @@ static int yama_task_prctl(int option, unsigned long arg2, unsigned long arg3,
>  		if (arg2 == 0) {
>  			yama_ptracer_del(NULL, myself);
>  			rc = 0;
> -		} else if (arg2 == PR_SET_PTRACER_ANY) {
> +		} else if (arg2 == PR_SET_PTRACER_ANY || (int)arg2 == -1) {
>  			rc = yama_ptracer_add(NULL, myself);
>  		} else {
>  			struct task_struct *tracer;
> 

yeah this looks good it should at least hit stable

Acked-by: John Johansen <john.johansen@canonical.com>


  parent reply	other threads:[~2012-09-05 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 18:38 [PATCH] Yama: handle 32-bit userspace prctl Kees Cook
2012-09-05 21:41 ` Kees Cook
2012-09-05 22:06 ` John Johansen [this message]
2012-09-07 15:25 ` 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=5047CCCB.1000108@canonical.com \
    --to=john.johansen@canonical.com \
    --cc=dan.carpenter@oracle.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 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.