mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/core for 5.19
Date: Mon, 23 May 2022 17:28:49 +0200	[thread overview]
Message-ID: <YouoMW6jtD3BRavh@zn.tnic> (raw)

Hi Linus,

please pull a set of x86/core fixes for 5.19.

Thx.

---

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_core_for_v5.19_rc1

for you to fetch changes up to 69505e3d9a39a988aaed9b58aa6b3482238f6516:

  bug: Use normal relative pointers in 'struct bug_entry' (2022-05-19 23:46:10 +0200)

----------------------------------------------------------------
- Remove all the code around GS switching on 32-bit now that it is not
needed anymore

- Other misc improvements

----------------------------------------------------------------
Brian Gerst (4):
      x86/32: Simplify ELF_CORE_COPY_REGS
      ELF: Remove elf_core_copy_kernel_regs()
      x86/32: Remove lazy GS macros
      x86/asm: Merge load_gs_index()

Josh Poimboeuf (1):
      bug: Use normal relative pointers in 'struct bug_entry'

Thomas Gleixner (1):
      x86/nmi: Make register_nmi_handler() more robust

 arch/arm64/include/asm/asm-bug.h           |  4 ++--
 arch/powerpc/include/asm/bug.h             | 14 ++++++++------
 arch/powerpc/kernel/fadump.c               |  2 +-
 arch/powerpc/platforms/powernv/opal-core.c |  2 +-
 arch/riscv/include/asm/bug.h               |  4 ++--
 arch/s390/include/asm/bug.h                |  5 +++--
 arch/x86/include/asm/bug.h                 |  2 +-
 arch/x86/include/asm/elf.h                 | 15 ++-------------
 arch/x86/include/asm/mmu_context.h         |  2 +-
 arch/x86/include/asm/nmi.h                 |  1 +
 arch/x86/include/asm/segment.h             | 12 ------------
 arch/x86/include/asm/special_insns.h       |  7 ++++---
 arch/x86/kernel/nmi.c                      | 12 ++++++++----
 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 +-
 lib/bug.c                                  | 15 +++++++--------
 23 files changed, 61 insertions(+), 88 deletions(-)

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)

             reply	other threads:[~2022-05-23 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 15:28 Borislav Petkov [this message]
2022-05-24  2:51 ` pr-tracker-bot

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=YouoMW6jtD3BRavh@zn.tnic \
    --to=bp@suse.de \
    --cc=linux-kernel@vger.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®