All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/kdump changes for v5.5
Date: Mon, 25 Nov 2019 15:16:51 +0100	[thread overview]
Message-ID: <20191125141651.GA21990@gmail.com> (raw)

Linus,

Please pull the latest x86-kdump-for-linus git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-kdump-for-linus

   # HEAD: 9eff303725da6530b615e9258f696149baa51df6 x86/crash: Align function arguments on opening braces

This tree solves a kdump artifact where encrypted memory contents are 
dumped, instead of unencrypted ones. The solution also happens to 
simplify the kdump code, to everyone's delight.

 Thanks,

	Ingo

------------------>
Borislav Petkov (1):
      x86/crash: Align function arguments on opening braces

Lianbo Jiang (3):
      x86/crash: Add a forward declaration of struct kimage
      x86/kdump: Always reserve the low 1M when the crashkernel option is specified
      x86/kdump: Remove the backup region handling


 arch/x86/include/asm/crash.h       |   8 +++
 arch/x86/include/asm/kexec.h       |  10 ---
 arch/x86/include/asm/purgatory.h   |  10 ---
 arch/x86/kernel/crash.c            | 128 +++++++++++--------------------------
 arch/x86/kernel/machine_kexec_64.c |  47 --------------
 arch/x86/purgatory/purgatory.c     |  19 ------
 arch/x86/realmode/init.c           |   2 +
 7 files changed, 46 insertions(+), 178 deletions(-)

             reply	other threads:[~2019-11-25 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 14:16 Ingo Molnar [this message]
2019-11-26 19:30 ` [GIT PULL] x86/kdump changes for v5.5 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=20191125141651.GA21990@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.