mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: X86 ML <x86@kernel.org>, Borislav Petkov <bpetkov@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Brian Gerst <brgerst@gmail.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH 11/16] x86/asm/64: Use a percpu trampoline stack for IDT entries
Date: Tue, 21 Nov 2017 08:20:37 +0100	[thread overview]
Message-ID: <20171121072037.kkgaxvtalvv7d4sc@gmail.com> (raw)
In-Reply-To: <3ff604702987cf6af1e191705fd937517ceeeeb7.1511195781.git.luto@kernel.org>


* Andy Lutomirski <luto@kernel.org> wrote:

> diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
> index 1ea03027a4a9..e4a941be96cf 100644
> --- a/arch/x86/kernel/traps.c
> +++ b/arch/x86/kernel/traps.c

> -asmlinkage __visible notrace
> +asmlinkage __visible notrace __no_sanitize_address
>  struct bad_iret_stack *fixup_bad_iret(struct bad_iret_stack *s)
>  {
>  	/*
>  	 * This is called from entry_64.S early in handling a fault
>  	 * caused by a bad iret to user mode.  To handle the fault
> -	 * correctly, we want move our stack frame to task_pt_regs
> -	 * and we want to pretend that the exception came from the
> -	 * iret target.
> +	 * correctly, we want move our stack frame to where it would
> +	 * be had we entered directly on the entry stack (rather than
> +	 * just below the IRET frame) and we want to pretend that the
> +	 * exception came from the iret target.
>  	 */
>  	struct bad_iret_stack *new_stack =
> -		container_of(task_pt_regs(current),
> -			     struct bad_iret_stack, regs);
> +		(struct bad_iret_stack *)this_cpu_read(cpu_tss.x86_tss.sp0) - 1;
>  
>  	/* Copy the IRET target to the new stack. */
>  	memmove(&new_stack->regs.ip, (void *)s->regs.sp, 5*8);

So the addition of the __no_sanitize_address attribute to fixup_bad_iret() made 
the 64-bit allyesconfig/allmodconfig kernels fail the build:

 In file included from ./include/linux/bitmap.h:9:0,
 arch/x86/kernel/traps.c: In function ‘fixup_bad_iret’:
 ./include/linux/string.h:344:24: error: inlining failed in call to always_inline 
 ‘memmove’: function attribute mismatch
  __FORTIFY_INLINE void *memmove(void *p, const void *q, __kernel_size_t size)
 arch/x86/kernel/traps.c:645:2: error: called from here
 In file included from ./include/linux/bitmap.h:9:0,
 ./include/linux/string.h:344:24: error: inlining failed in call to always_inline 
 ‘memmove’: function attribute mismatch
  __FORTIFY_INLINE void *memmove(void *p, const void *q, __kernel_size_t size)
 arch/x86/kernel/traps.c:642:2: error: called from here
 scripts/Makefile.build:314: recipe for target 'arch/x86/kernel/traps.o' failed

Thanks,

	Ingo

  reply	other threads:[~2017-11-21  7:20 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 17:07 [PATCH 00/16] Entry stuff, in decent shape now Andy Lutomirski
2017-11-20 17:07 ` [PATCH 01/16] x86/asm/64: Allocate and enable the SYSENTER stack Andy Lutomirski
2017-11-20 21:55   ` Thomas Gleixner
2017-11-21 10:47   ` Borislav Petkov
2017-11-20 17:07 ` [PATCH 02/16] x86/dumpstack: Add get_stack_info() support for " Andy Lutomirski
2017-11-20 20:42   ` Josh Poimboeuf
2017-11-20 20:46     ` Andy Lutomirski
2017-11-20 21:00       ` Josh Poimboeuf
2017-11-20 21:07         ` Andy Lutomirski
2017-11-20 21:27           ` Josh Poimboeuf
2017-11-20 21:30             ` Andy Lutomirski
2017-11-20 21:55               ` Josh Poimboeuf
2017-11-21  1:39                 ` Andy Lutomirski
2017-11-21  2:29                   ` Josh Poimboeuf
2017-11-20 17:07 ` [PATCH 03/16] x86/gdt: Put per-cpu GDT remaps in ascending order Andy Lutomirski
2017-11-20 21:56   ` Thomas Gleixner
2017-11-21 17:16   ` Borislav Petkov
2017-11-20 17:07 ` [PATCH 04/16] x86/fixmap: Generalize the GDT fixmap mechanism Andy Lutomirski
2017-11-20 22:01   ` Thomas Gleixner
2017-11-21  1:21     ` Andy Lutomirski
2017-11-21  8:29       ` Thomas Gleixner
2017-11-20 17:07 ` [PATCH 05/16] x86/asm: Fix assumptions that the HW TSS is at the beginning of cpu_tss Andy Lutomirski
2017-11-20 22:22   ` Thomas Gleixner
2017-11-20 17:07 ` [PATCH 06/16] x86/dumpstack: Handle stack overflow on all stacks Andy Lutomirski
2017-11-20 17:07 ` [PATCH 07/16] x86/asm: Move SYSENTER_stack to the beginning of struct tss_struct Andy Lutomirski
2017-11-20 23:37   ` Thomas Gleixner
2017-11-21  1:25     ` Andy Lutomirski
2017-11-20 17:07 ` [PATCH 08/16] x86/asm: Remap the TSS into the cpu entry area Andy Lutomirski
2017-11-20 17:07 ` [PATCH 09/16] x86/asm/64: Separate cpu_current_top_of_stack from TSS.sp0 Andy Lutomirski
2017-11-20 17:07 ` [PATCH 10/16] x86/espfix/64: Stop assuming that pt_regs is on the entry stack Andy Lutomirski
2017-11-20 17:07 ` [PATCH 11/16] x86/asm/64: Use a percpu trampoline stack for IDT entries Andy Lutomirski
2017-11-21  7:20   ` Ingo Molnar [this message]
2017-11-21 15:36     ` Andy Lutomirski
2017-11-21 18:57   ` Dave Hansen
2017-11-22  3:45     ` Andy Lutomirski
2017-11-20 17:07 ` [PATCH 12/16] x86/asm/64: Return to userspace from the trampoline stack Andy Lutomirski
2017-11-20 17:07 ` [PATCH 13/16] x86/entry/64: Create a percpu SYSCALL entry trampoline Andy Lutomirski
2017-11-21  2:34   ` Josh Poimboeuf
2017-11-21  3:20     ` Andy Lutomirski
2017-11-20 17:07 ` [PATCH 14/16] x86/irq: Remove an old outdated comment about context tracking races Andy Lutomirski
2017-11-21  6:25   ` Ingo Molnar
2017-11-20 17:07 ` [PATCH 15/16] x86/irq/64: In the stack overflow warning, print the offending IP Andy Lutomirski
2017-11-21  6:26   ` Ingo Molnar
2017-11-20 17:07 ` [PATCH 16/16] x86/entry/64: Move the IST stacks into cpu_entry_area Andy Lutomirski
2017-11-21  7:38   ` Ingo Molnar
2017-11-21 14:45     ` Andrey Ryabinin
2017-11-23 15:25       ` Andy Lutomirski
2017-11-21 15:33     ` Andy Lutomirski
2017-11-20 18:48 ` [PATCH 00/16] Entry stuff, in decent shape now Andy Lutomirski
2017-11-21  7:33 ` Ingo Molnar
2017-11-21 15:59   ` Andy Lutomirski
2017-11-21 16:12     ` Andy Lutomirski

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=20171121072037.kkgaxvtalvv7d4sc@gmail.com \
    --to=mingo@kernel.org \
    --cc=bpetkov@suse.de \
    --cc=brgerst@gmail.com \
    --cc=dave.hansen@intel.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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®