linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: "tee-dev @ lists . linaro . org" <tee-dev@lists.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stuart Yoder <stuart.yoder@arm.com>,
	Daniel Thompson <daniel.thompson@linaro.org>
Subject: Re: [PATCH v4 2/2] tee: add private login method for kernel clients
Date: Wed, 25 Mar 2020 09:33:45 +0100	[thread overview]
Message-ID: <CAHUa44Fd3ujQY8ev9sZOMya7wrTmHnvda_05XhQA7X3knB3auA@mail.gmail.com> (raw)
In-Reply-To: <1584965910-19068-3-git-send-email-sumit.garg@linaro.org>

On Mon, Mar 23, 2020 at 1:19 PM Sumit Garg <sumit.garg@linaro.org> wrote:
>
> There are use-cases where user-space shouldn't be allowed to communicate
> directly with a TEE device which is dedicated to provide a specific
> service for a kernel client. So add a private login method for kernel
> clients and disallow user-space to open-session using GP implementation
> defined login method range: (0x80000000 - 0xFFFFFFFF).
>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> ---
>  drivers/tee/tee_core.c   | 6 ++++++
>  include/uapi/linux/tee.h | 8 ++++++++
>  2 files changed, 14 insertions(+)

Looks good.

Thanks,
Jens

>
> diff --git a/drivers/tee/tee_core.c b/drivers/tee/tee_core.c
> index 37d22e3..533e7a8 100644
> --- a/drivers/tee/tee_core.c
> +++ b/drivers/tee/tee_core.c
> @@ -334,6 +334,12 @@ static int tee_ioctl_open_session(struct tee_context *ctx,
>                         goto out;
>         }
>
> +       if (arg.clnt_login & TEE_IOCTL_LOGIN_MASK) {
> +               pr_debug("login method not allowed for user-space client\n");
> +               rc = -EPERM;
> +               goto out;
> +       }
> +
>         rc = ctx->teedev->desc->ops->open_session(ctx, &arg, params);
>         if (rc)
>                 goto out;
> diff --git a/include/uapi/linux/tee.h b/include/uapi/linux/tee.h
> index 6596f3a..19172a2 100644
> --- a/include/uapi/linux/tee.h
> +++ b/include/uapi/linux/tee.h
> @@ -173,6 +173,14 @@ struct tee_ioctl_buf_data {
>  #define TEE_IOCTL_LOGIN_APPLICATION            4
>  #define TEE_IOCTL_LOGIN_USER_APPLICATION       5
>  #define TEE_IOCTL_LOGIN_GROUP_APPLICATION      6
> +/*
> + * Disallow user-space to use GP implementation specific login
> + * method range (0x80000000 - 0xFFFFFFFF). This range is rather
> + * being reserved for REE kernel clients or TEE implementation.
> + */
> +#define TEE_IOCTL_LOGIN_MASK                   0x80000000
> +/* Private login method for REE kernel clients */
> +#define TEE_IOCTL_LOGIN_REE_KERNEL             0x80000000
>
>  /**
>   * struct tee_ioctl_param - parameter
> --
> 2.7.4
>

      reply	other threads:[~2020-03-25  8:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 12:18 [PATCH v4 0/2] Enhance TEE kernel client interface Sumit Garg
2020-03-23 12:18 ` [PATCH v4 1/2] tee: enable support to register kernel memory Sumit Garg
2020-03-25  8:29   ` Jens Wiklander
2020-03-25  8:48     ` Sumit Garg
2020-03-23 12:18 ` [PATCH v4 2/2] tee: add private login method for kernel clients Sumit Garg
2020-03-25  8:33   ` Jens Wiklander [this message]

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=CAHUa44Fd3ujQY8ev9sZOMya7wrTmHnvda_05XhQA7X3knB3auA@mail.gmail.com \
    --to=jens.wiklander@linaro.org \
    --cc=daniel.thompson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stuart.yoder@arm.com \
    --cc=sumit.garg@linaro.org \
    --cc=tee-dev@lists.linaro.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;
as well as URLs for NNTP newsgroup(s).