mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bae, Chang Seok" <chang.seok.bae@intel.com>
To: "Zhong, Yang" <yang.zhong@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"bp@suse.de" <bp@suse.de>, "Hansen, Dave" <dave.hansen@intel.com>,
	"Liu, Jing2" <jing2.liu@intel.com>
Subject: Re: [PATCH] x86/fpu: Set the corret permission value for perm.__state_perm
Date: Mon, 8 Nov 2021 16:13:58 +0000	[thread overview]
Message-ID: <045FEB79-B7AE-421F-A7F1-1ABC86E0E19F@intel.com> (raw)
In-Reply-To: <20211108222815.4078-1-yang.zhong@intel.com>

On Nov 8, 2021, at 14:28, Zhong, Yang <yang.zhong@intel.com> wrote:
> 
> The perm.__state_perm is default xsave set features, when we request
> AMX permission from application, the requested value(bit18) should be
> replaced with mask value(requested | permitted), which can keep default
> features there.
> 
> Without this change, the below prctl syscall:
> (1). ARCH_GET_XCOMP_PERM, the bitmask=0x202e7
> (2). set ARCH_REQ_XCOMP_PERM with XFEATURE_XTILEDATA
> (3). ARCH_GET_XCOMP_PERM, the bitmask=0x40000, the correct value
>     should be 0x602e7 here.

Oh, bad. 

> diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c
> index d28829403ed0..fc1ab0116f4e 100644
> --- a/arch/x86/kernel/fpu/xstate.c
> +++ b/arch/x86/kernel/fpu/xstate.c
> @@ -1626,7 +1626,7 @@ static int __xstate_request_perm(u64 permitted, u64 requested)
> 		return ret;
> 
> 	/* Pairs with the READ_ONCE() in xstate_get_group_perm() */
> -	WRITE_ONCE(fpu->perm.__state_perm, requested);
> +	WRITE_ONCE(fpu->perm.__state_perm, mask);

I think this has to update the group leader’s like:
    WRITE_ONCE(current->group_leader->thread.fpu.perm.__state_perm, mask);

Thanks,
Chang




  reply	other threads:[~2021-11-08 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 22:28 Yang Zhong
2021-11-08 16:13 ` Bae, Chang Seok [this message]
2021-11-08 23:45   ` Bae, Chang Seok
2021-11-09  0:36   ` Yang Zhong

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=045FEB79-B7AE-421F-A7F1-1ABC86E0E19F@intel.com \
    --to=chang.seok.bae@intel.com \
    --cc=bp@suse.de \
    --cc=dave.hansen@intel.com \
    --cc=jing2.liu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yang.zhong@intel.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®