mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	dave.hansen@linux.intel.com, oleg@redhat.com, bp@alien8.de,
	riel@redhat.com, sbsiddha@gmail.com, luto@amacapital.net,
	mingo@redhat.com, hpa@zytor.com, fenghua.yu@intel.com
Subject: Re: [PATCH 03/19] x86, mpx: use new tsk_get_xsave_addr()
Date: Mon, 18 May 2015 22:36:01 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1505182218220.4225@nanos> (raw)
In-Reply-To: <20150508185949.3250100D@viggo.jf.intel.com>

On Fri, 8 May 2015, Dave Hansen wrote:

> Subject: x86, mpx: use new tsk_get_xsave_addr()

-NOSUCHFUNCTION

And please let the sentence start with an upper case letter.

x86, mpx: Use ...

>  #ifdef CONFIG_X86_INTEL_MPX
>  siginfo_t *mpx_generate_siginfo(struct pt_regs *regs,
> -				struct xsave_struct *xsave_buf);
> -int mpx_handle_bd_fault(struct xsave_struct *xsave_buf);
> +				struct task_struct *tsk);
> +int mpx_handle_bd_fault(struct task_struct *tsk);

So you still keep *tsk and remove it in the next patch. I guess either
ordering has its value, so no problem to do it this way.

>  static inline int kernel_managing_mpx_tables(struct mm_struct *mm)
>  {
>  	return (mm->bd_addr != MPX_INVALID_BOUNDS_DIR);
> @@ -78,11 +78,11 @@ void mpx_notify_unmap(struct mm_struct *
>  		      unsigned long start, unsigned long end);
>  #else
>  static inline siginfo_t *mpx_generate_siginfo(struct pt_regs *regs,
> -					      struct xsave_struct *xsave_buf)
> +					      struct task_struct *tsk)

But that makes no sense. Introduce a new instance just to remove it
one patch later. So maybe cleaning up the *tsk thing first might be
the better approach, but I let you decide.

>  #include <asm/mach_traps.h>
>  #include <asm/alternative.h>
>  #include <asm/mpx.h>
> +#include <asm/xsave.h>
>  
>  #ifdef CONFIG_X86_64
>  #include <asm/x86_init.h>
> @@ -372,7 +373,6 @@ dotraplinkage void do_double_fault(struc
>  dotraplinkage void do_bounds(struct pt_regs *regs, long error_code)
>  {
>  	struct task_struct *tsk = current;
> -	struct xsave_struct *xsave_buf;
>  	enum ctx_state prev_state;
>  	struct bndcsr *bndcsr;
>  	siginfo_t *info;
> @@ -393,12 +393,11 @@ dotraplinkage void do_bounds(struct pt_r
>  
>  	/*
>  	 * We need to look at BNDSTATUS to resolve this exception.
> -	 * It is not directly accessible, though, so we need to
> -	 * do an xsave and then pull it out of the xsave buffer.
> +	 * A NULL here might mean that it is in its 'init state',
> +	 * which is all zeros which indicates MPX was not
> +	 * responsible for the exception.
>  	 */
> -	fpu_save_init(&tsk->thread.fpu);
> -	xsave_buf = &(tsk->thread.fpu.state->xsave);
> -	bndcsr = get_xsave_addr(xsave_buf, XSTATE_BNDCSR);
> +	bndcsr = get_xsave_field(XSTATE_BNDCSR);

Hmm, I did not notice when I looked at the patch which introduced
get_xsave_field(). But with the removed get_xsave_addr() I really had
to look twice.

get_xsave_field() suggest that you get the field content. So wouldn't
it be better to name it get_xsave_field_ptr() or such?

>  	if (!bndcsr)
>  		goto exit_trap;
>  
> @@ -409,11 +408,11 @@ dotraplinkage void do_bounds(struct pt_r
>  	 */
>  	switch (bndcsr->bndstatus & MPX_BNDSTA_ERROR_CODE) {
>  	case 2:	/* Bound directory has invalid entry. */
> -		if (mpx_handle_bd_fault(xsave_buf))
> +		if (mpx_handle_bd_fault(tsk))
>  			goto exit_trap;
>  		break; /* Success, it was handled */
>  	case 1: /* Bound violation. */
> -		info = mpx_generate_siginfo(regs, xsave_buf);
> +		info = mpx_generate_siginfo(regs, tsk);
>  		if (IS_ERR(info)) {
>  			/*
>  			 * We failed to decode the MPX instruction.  Act as if
> diff -puN arch/x86/mm/mpx.c~use-new-tsk_get_xsave_addr arch/x86/mm/mpx.c
> --- a/arch/x86/mm/mpx.c~use-new-tsk_get_xsave_addr	2015-05-08 11:46:11.388599581 -0700
> +++ b/arch/x86/mm/mpx.c	2015-05-08 11:46:11.393599807 -0700
> @@ -273,7 +273,7 @@ bad_opcode:
>   * The caller is expected to kfree() the returned siginfo_t.
>   */
>  siginfo_t *mpx_generate_siginfo(struct pt_regs *regs,
> -				struct xsave_struct *xsave_buf)
> +				struct task_struct *tsk)

Looking at the implementation makes me wonder about the extra *tsk
argument some more ....

>  {
>  	struct bndreg *bndregs, *bndreg;
>  	siginfo_t *info = NULL;
> @@ -295,8 +295,8 @@ siginfo_t *mpx_generate_siginfo(struct p
>  		err = -EINVAL;
>  		goto err_out;
>  	}
> -	/* get the bndregs _area_ of the xsave structure */
> -	bndregs = get_xsave_addr(xsave_buf, XSTATE_BNDREGS);
> +	/* get bndregs field from urrent task's xsave area */

  urrent?

> +	bndregs = get_xsave_field(XSTATE_BNDREGS);
>  	if (!bndregs) {
>  		err = -EINVAL;
>  		goto err_out;

Still no user of *tsk ....

> @@ -358,8 +358,7 @@ static __user void *task_get_bounds_dir(
> -int mpx_handle_bd_fault(struct xsave_struct *xsave_buf)
> +int mpx_handle_bd_fault(struct task_struct *tsk)
>  {
>  	/*
>  	 * Userspace never asked us to manage the bounds tables,
> @@ -535,7 +534,7 @@ int mpx_handle_bd_fault(struct xsave_str
>  	if (!kernel_managing_mpx_tables(current->mm))
>  		return -EINVAL;
>  
> -	if (do_mpx_bt_fault(xsave_buf)) {
> +	if (do_mpx_bt_fault(tsk)) {

Same problem actually with do_mpx_bt_fault().

Thanks,

	tglx

  reply	other threads:[~2015-05-18 20:35 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 18:59 [PATCH 00/19] x86, mpx updates for 4.2 (take 6) Dave Hansen
2015-05-08 18:59 ` [PATCH 01/19] x86, mpx, xsave: fix up bad get_xsave_addr() assumptions Dave Hansen
2015-05-18 19:34   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 02/19] x86, fpu: wrap get_xsave_addr() to make it safer Dave Hansen
2015-05-18 19:38   ` Thomas Gleixner
2015-05-18 19:42     ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 03/19] x86, mpx: use new tsk_get_xsave_addr() Dave Hansen
2015-05-18 20:36   ` Thomas Gleixner [this message]
2015-05-19  0:01     ` Dave Hansen
2015-05-08 18:59 ` [PATCH 05/19] x86, mpx: remove redundant MPX_BNDCFG_ADDR_MASK Dave Hansen
2015-05-18 20:38   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 04/19] x86, mpx: cleanup: do not pass task around when unnecessary Dave Hansen
2015-05-18 20:38   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 06/19] x86, mpx: we do not allocate the bounds directory Dave Hansen
2015-05-18 20:43   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 07/19] x86, mpx: boot-time disable Dave Hansen
2015-05-18 20:45   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 08/19] x86, mpx: trace #BR exceptions Dave Hansen
2015-05-18 21:00   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 09/19] x86, mpx: trace entry to bounds exception paths Dave Hansen
2015-05-18 20:58   ` Thomas Gleixner
2015-05-18 23:06     ` Dave Hansen
2015-05-18 23:35       ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 10/19] x86, mpx: trace ranged MPX operations Dave Hansen
2015-05-18 21:04   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 11/19] x86, mpx: trace allocation of new bounds tables Dave Hansen
2015-05-18 21:04   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 12/19] x86: make is_64bit_mm() widely available Dave Hansen
2015-05-18 21:06   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 14/19] x86, mpx: new directory entry to addr helper Dave Hansen
2015-05-18 21:10   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 13/19] x86, mpx: Add temporary variable to reduce masking Dave Hansen
2015-05-18 21:07   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 15/19] x86, mpx: do 32-bit-only cmpxchg for 32-bit apps Dave Hansen
2015-05-18 21:22   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 16/19] x86, mpx: support 32-bit binaries on 64-bit kernel Dave Hansen
2015-05-18 21:53   ` Thomas Gleixner
2015-05-18 23:29     ` Dave Hansen
2015-05-18 23:37       ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 17/19] x86, mpx: rewrite unmap code Dave Hansen
2015-05-18 21:55   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 18/19] x86, mpx: do not count MPX VMAs as neighbors when unmapping Dave Hansen
2015-05-18 21:54   ` Thomas Gleixner
2015-05-08 18:59 ` [PATCH 19/19] x86, mpx: allow mixed binaries again Dave Hansen
2015-05-18 21:55   ` Thomas Gleixner

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.DEB.2.11.1505182218220.4225@nanos \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave@sr71.net \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=oleg@redhat.com \
    --cc=riel@redhat.com \
    --cc=sbsiddha@gmail.com \
    --cc=x86@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

all inboxes | Powered by JetHome®