public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: Brian Gerst <brgerst@gmail.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H . Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/4] x86-32: Clean up GS segment handling
Date: Fri, 25 Mar 2022 08:45:59 -0700	[thread overview]
Message-ID: <9e1a95ef-69ad-1f6c-e1f3-dcff3ed65e79@kernel.org> (raw)
In-Reply-To: <20220325153953.162643-1-brgerst@gmail.com>

On 3/25/22 08:39, Brian Gerst wrote:
> Since commit 3fb0fdb3bbe ("Make the canary into a regular percpu
> variable"), the GS segment is no longer switched on kernel entry for
> 32-bit kernels.  Clean up the remaining code that handled lazy GS
> switching.
> 

Acked-by: Andy Lutomirski <luto@kernel.org>

Thanks!

> Brian Gerst (4):
>    x86-32: Simplify ELF_CORE_COPY_REGS
>    ELF: Remove elf_core_copy_kernel_regs()
>    x86-32: Remove lazy GS macros
>    x86: Merge load_gs_index()
> 
>   arch/powerpc/kernel/fadump.c               |  2 +-
>   arch/powerpc/platforms/powernv/opal-core.c |  2 +-
>   arch/x86/include/asm/elf.h                 | 15 ++-------------
>   arch/x86/include/asm/mmu_context.h         |  2 +-
>   arch/x86/include/asm/segment.h             | 12 ------------
>   arch/x86/include/asm/special_insns.h       |  7 ++++---
>   arch/x86/kernel/process.c                  |  5 +----
>   arch/x86/kernel/process_32.c               | 11 ++++-------
>   arch/x86/kernel/ptrace.c                   |  6 +++---
>   arch/x86/kernel/signal.c                   |  8 +++++---
>   arch/x86/kernel/vm86_32.c                  |  4 ++--
>   arch/x86/lib/insn-eval.c                   |  5 +++--
>   arch/x86/math-emu/get_address.c            |  2 +-
>   include/linux/elfcore.h                    |  9 ---------
>   kernel/kexec_core.c                        |  2 +-
>   15 files changed, 29 insertions(+), 63 deletions(-)
> 


  parent reply	other threads:[~2022-03-25 15:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 15:39 [PATCH 0/4] x86-32: Clean up GS segment handling Brian Gerst
2022-03-25 15:39 ` [PATCH 1/4] x86-32: Simplify ELF_CORE_COPY_REGS Brian Gerst
2022-04-15  9:42   ` [tip: x86/core] x86/32: " tip-bot2 for Brian Gerst
2022-03-25 15:39 ` [PATCH 2/4] ELF: Remove elf_core_copy_kernel_regs() Brian Gerst
2022-04-13 11:41   ` Borislav Petkov
2022-04-13 12:31     ` Michael Ellerman
2022-04-15  9:42   ` [tip: x86/core] " tip-bot2 for Brian Gerst
2022-03-25 15:39 ` [PATCH 3/4] x86-32: Remove lazy GS macros Brian Gerst
2022-04-15  9:42   ` [tip: x86/core] x86/32: " tip-bot2 for Brian Gerst
2022-03-25 15:39 ` [PATCH 4/4] x86: Merge load_gs_index() Brian Gerst
2022-04-15  9:42   ` [tip: x86/core] x86/asm: " tip-bot2 for Brian Gerst
2022-03-25 15:45 ` Andy Lutomirski [this message]
2022-04-05 16:12 ` [PATCH 0/4] x86-32: Clean up GS segment handling 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=9e1a95ef-69ad-1f6c-e1f3-dcff3ed65e79@kernel.org \
    --to=luto@kernel.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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