From: Baoquan He <bhe@redhat.com>
To: James Morse <james.morse@arm.com>
Cc: David Hildenbrand <david@redhat.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
Eric Biederman <ebiederm@xmission.com>,
Dave Young <dyoung@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kexec: Discard loaded image on memory hotplug
Date: Sun, 10 May 2020 21:06:46 +0800 [thread overview]
Message-ID: <20200510130646.GA4922@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20200501165701.24587-1-james.morse@arm.com>
Hi James,
On 05/01/20 at 05:57pm, James Morse wrote:
> On x86, the kexec payload contains a copy of the current memory map.
> If memory is added or removed, this copy of the memory map becomes
> stale. Getting this wrong may prevent the next kernel from booting.
> The first kernel may die if it tries to re-assemble the next kernel
> in memory that has been removed.
>
> Discard the loaded kexec image when the memory map changes, user-space
> should reload it.
As we have discarded in your patches thread, adding a kexec service to
reload kexec should fix this. Do you mean there's still another issue
that we need fix? I may not get it clearly.
>
> Kdump is unaffected, as it is placed within the crashkernel reserved
> memory area and only uses this memory. The stale memory map may affect
> generation of the vmcore, but the kdump kernel should be in a position
> to validate it.
>
> Signed-off-by: James Morse <james.morse@arm.com>
> ---
> This patch obsoletes:
> * kexec/memory_hotplug: Prevent removal and accidental use
> https://lore.kernel.org/linux-arm-kernel/20200326180730.4754-1-james.morse@arm.com/
>
> kernel/kexec_core.c | 40 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
>
> diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
> index c19c0dad1ebe..e1901e5bd4b5 100644
> --- a/kernel/kexec_core.c
> +++ b/kernel/kexec_core.c
> @@ -12,6 +12,7 @@
> #include <linux/slab.h>
> #include <linux/fs.h>
> #include <linux/kexec.h>
> +#include <linux/memory.h>
> #include <linux/mutex.h>
> #include <linux/list.h>
> #include <linux/highmem.h>
> @@ -22,10 +23,12 @@
> #include <linux/elf.h>
> #include <linux/elfcore.h>
> #include <linux/utsname.h>
> +#include <linux/notifier.h>
> #include <linux/numa.h>
> #include <linux/suspend.h>
> #include <linux/device.h>
> #include <linux/freezer.h>
> +#include <linux/pfn.h>
> #include <linux/pm.h>
> #include <linux/cpu.h>
> #include <linux/uaccess.h>
> @@ -1219,3 +1222,40 @@ void __weak arch_kexec_protect_crashkres(void)
>
> void __weak arch_kexec_unprotect_crashkres(void)
> {}
> +
> +/*
> + * If the memory layout changes, any loaded kexec image should be evicted
> + * as it may contain a copy of the (now stale) memory map. This also means
> + * we don't need to check the memory is still present when re-assembling the
> + * new kernel at machine_kexec() time.
> + */
> +static int mem_change_cb(struct notifier_block *nb, unsigned long action,
> + void *data)
> +{
> + /*
> + * Actions are either a change, or a change being cancelled.
> + * A second discard for 'cancel's is harmless.
> + */
> +
> + mutex_lock(&kexec_mutex);
> + if (kexec_image) {
> + kimage_free(xchg(&kexec_image, NULL));
> + pr_warn("loaded image discarded due to memory hotplug");
> + }
> + mutex_unlock(&kexec_mutex);
> +
> + return NOTIFY_DONE;
> +}
> +
> +static struct notifier_block mem_change_nb = {
> + .notifier_call = mem_change_cb,
> +};
> +
> +static int __init register_mem_change_cb(void)
> +{
> + if (IS_ENABLED(CONFIG_MEMORY_HOTPLUG))
> + return register_memory_notifier(&mem_change_nb);
> +
> + return 0;
> +}
> +device_initcall(register_mem_change_cb);
> --
> 2.26.1
>
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: James Morse <james.morse@arm.com>
Cc: David Hildenbrand <david@redhat.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
Eric Biederman <ebiederm@xmission.com>,
Dave Young <dyoung@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kexec: Discard loaded image on memory hotplug
Date: Sun, 10 May 2020 21:06:46 +0800 [thread overview]
Message-ID: <20200510130646.GA4922@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20200501165701.24587-1-james.morse@arm.com>
Hi James,
On 05/01/20 at 05:57pm, James Morse wrote:
> On x86, the kexec payload contains a copy of the current memory map.
> If memory is added or removed, this copy of the memory map becomes
> stale. Getting this wrong may prevent the next kernel from booting.
> The first kernel may die if it tries to re-assemble the next kernel
> in memory that has been removed.
>
> Discard the loaded kexec image when the memory map changes, user-space
> should reload it.
As we have discarded in your patches thread, adding a kexec service to
reload kexec should fix this. Do you mean there's still another issue
that we need fix? I may not get it clearly.
>
> Kdump is unaffected, as it is placed within the crashkernel reserved
> memory area and only uses this memory. The stale memory map may affect
> generation of the vmcore, but the kdump kernel should be in a position
> to validate it.
>
> Signed-off-by: James Morse <james.morse@arm.com>
> ---
> This patch obsoletes:
> * kexec/memory_hotplug: Prevent removal and accidental use
> https://lore.kernel.org/linux-arm-kernel/20200326180730.4754-1-james.morse@arm.com/
>
> kernel/kexec_core.c | 40 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
>
> diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
> index c19c0dad1ebe..e1901e5bd4b5 100644
> --- a/kernel/kexec_core.c
> +++ b/kernel/kexec_core.c
> @@ -12,6 +12,7 @@
> #include <linux/slab.h>
> #include <linux/fs.h>
> #include <linux/kexec.h>
> +#include <linux/memory.h>
> #include <linux/mutex.h>
> #include <linux/list.h>
> #include <linux/highmem.h>
> @@ -22,10 +23,12 @@
> #include <linux/elf.h>
> #include <linux/elfcore.h>
> #include <linux/utsname.h>
> +#include <linux/notifier.h>
> #include <linux/numa.h>
> #include <linux/suspend.h>
> #include <linux/device.h>
> #include <linux/freezer.h>
> +#include <linux/pfn.h>
> #include <linux/pm.h>
> #include <linux/cpu.h>
> #include <linux/uaccess.h>
> @@ -1219,3 +1222,40 @@ void __weak arch_kexec_protect_crashkres(void)
>
> void __weak arch_kexec_unprotect_crashkres(void)
> {}
> +
> +/*
> + * If the memory layout changes, any loaded kexec image should be evicted
> + * as it may contain a copy of the (now stale) memory map. This also means
> + * we don't need to check the memory is still present when re-assembling the
> + * new kernel at machine_kexec() time.
> + */
> +static int mem_change_cb(struct notifier_block *nb, unsigned long action,
> + void *data)
> +{
> + /*
> + * Actions are either a change, or a change being cancelled.
> + * A second discard for 'cancel's is harmless.
> + */
> +
> + mutex_lock(&kexec_mutex);
> + if (kexec_image) {
> + kimage_free(xchg(&kexec_image, NULL));
> + pr_warn("loaded image discarded due to memory hotplug");
> + }
> + mutex_unlock(&kexec_mutex);
> +
> + return NOTIFY_DONE;
> +}
> +
> +static struct notifier_block mem_change_nb = {
> + .notifier_call = mem_change_cb,
> +};
> +
> +static int __init register_mem_change_cb(void)
> +{
> + if (IS_ENABLED(CONFIG_MEMORY_HOTPLUG))
> + return register_memory_notifier(&mem_change_nb);
> +
> + return 0;
> +}
> +device_initcall(register_mem_change_cb);
> --
> 2.26.1
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: James Morse <james.morse@arm.com>
Cc: kexec@lists.infradead.org, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org,
Eric Biederman <ebiederm@xmission.com>,
David Hildenbrand <david@redhat.com>,
Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH] kexec: Discard loaded image on memory hotplug
Date: Sun, 10 May 2020 21:06:46 +0800 [thread overview]
Message-ID: <20200510130646.GA4922@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20200501165701.24587-1-james.morse@arm.com>
Hi James,
On 05/01/20 at 05:57pm, James Morse wrote:
> On x86, the kexec payload contains a copy of the current memory map.
> If memory is added or removed, this copy of the memory map becomes
> stale. Getting this wrong may prevent the next kernel from booting.
> The first kernel may die if it tries to re-assemble the next kernel
> in memory that has been removed.
>
> Discard the loaded kexec image when the memory map changes, user-space
> should reload it.
As we have discarded in your patches thread, adding a kexec service to
reload kexec should fix this. Do you mean there's still another issue
that we need fix? I may not get it clearly.
>
> Kdump is unaffected, as it is placed within the crashkernel reserved
> memory area and only uses this memory. The stale memory map may affect
> generation of the vmcore, but the kdump kernel should be in a position
> to validate it.
>
> Signed-off-by: James Morse <james.morse@arm.com>
> ---
> This patch obsoletes:
> * kexec/memory_hotplug: Prevent removal and accidental use
> https://lore.kernel.org/linux-arm-kernel/20200326180730.4754-1-james.morse@arm.com/
>
> kernel/kexec_core.c | 40 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
>
> diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
> index c19c0dad1ebe..e1901e5bd4b5 100644
> --- a/kernel/kexec_core.c
> +++ b/kernel/kexec_core.c
> @@ -12,6 +12,7 @@
> #include <linux/slab.h>
> #include <linux/fs.h>
> #include <linux/kexec.h>
> +#include <linux/memory.h>
> #include <linux/mutex.h>
> #include <linux/list.h>
> #include <linux/highmem.h>
> @@ -22,10 +23,12 @@
> #include <linux/elf.h>
> #include <linux/elfcore.h>
> #include <linux/utsname.h>
> +#include <linux/notifier.h>
> #include <linux/numa.h>
> #include <linux/suspend.h>
> #include <linux/device.h>
> #include <linux/freezer.h>
> +#include <linux/pfn.h>
> #include <linux/pm.h>
> #include <linux/cpu.h>
> #include <linux/uaccess.h>
> @@ -1219,3 +1222,40 @@ void __weak arch_kexec_protect_crashkres(void)
>
> void __weak arch_kexec_unprotect_crashkres(void)
> {}
> +
> +/*
> + * If the memory layout changes, any loaded kexec image should be evicted
> + * as it may contain a copy of the (now stale) memory map. This also means
> + * we don't need to check the memory is still present when re-assembling the
> + * new kernel at machine_kexec() time.
> + */
> +static int mem_change_cb(struct notifier_block *nb, unsigned long action,
> + void *data)
> +{
> + /*
> + * Actions are either a change, or a change being cancelled.
> + * A second discard for 'cancel's is harmless.
> + */
> +
> + mutex_lock(&kexec_mutex);
> + if (kexec_image) {
> + kimage_free(xchg(&kexec_image, NULL));
> + pr_warn("loaded image discarded due to memory hotplug");
> + }
> + mutex_unlock(&kexec_mutex);
> +
> + return NOTIFY_DONE;
> +}
> +
> +static struct notifier_block mem_change_nb = {
> + .notifier_call = mem_change_cb,
> +};
> +
> +static int __init register_mem_change_cb(void)
> +{
> + if (IS_ENABLED(CONFIG_MEMORY_HOTPLUG))
> + return register_memory_notifier(&mem_change_nb);
> +
> + return 0;
> +}
> +device_initcall(register_mem_change_cb);
> --
> 2.26.1
>
>
next prev parent reply other threads:[~2020-05-10 13:07 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 16:57 [PATCH] kexec: Discard loaded image on memory hotplug James Morse
2020-05-01 16:57 ` James Morse
2020-05-01 16:57 ` James Morse
2020-05-01 17:26 ` David Hildenbrand
2020-05-01 17:26 ` David Hildenbrand
2020-05-01 17:26 ` David Hildenbrand
2020-05-09 15:14 ` Eric W. Biederman
2020-05-09 15:14 ` Eric W. Biederman
2020-05-09 15:14 ` Eric W. Biederman
2020-05-11 8:19 ` David Hildenbrand
2020-05-11 8:19 ` David Hildenbrand
2020-05-11 8:19 ` David Hildenbrand
2020-05-11 11:27 ` Baoquan He
2020-05-11 11:27 ` Baoquan He
2020-05-11 11:27 ` Baoquan He
2020-05-11 11:55 ` David Hildenbrand
2020-05-11 11:55 ` David Hildenbrand
2020-05-11 11:55 ` David Hildenbrand
2020-05-12 10:34 ` Baoquan He
2020-05-12 10:34 ` Baoquan He
2020-05-12 10:34 ` Baoquan He
2020-05-12 10:54 ` David Hildenbrand
2020-05-12 10:54 ` David Hildenbrand
2020-05-12 10:54 ` David Hildenbrand
2020-05-12 14:11 ` Baoquan He
2020-05-12 14:11 ` Baoquan He
2020-05-12 14:11 ` Baoquan He
2020-05-11 17:05 ` Eric W. Biederman
2020-05-11 17:05 ` Eric W. Biederman
2020-05-11 17:05 ` Eric W. Biederman
2020-05-12 7:45 ` David Hildenbrand
2020-05-12 7:45 ` David Hildenbrand
2020-05-12 7:45 ` David Hildenbrand
2020-05-12 11:59 ` Eric W. Biederman
2020-05-12 11:59 ` Eric W. Biederman
2020-05-12 11:59 ` Eric W. Biederman
2020-05-10 13:06 ` Baoquan He [this message]
2020-05-10 13:06 ` Baoquan He
2020-05-10 13:06 ` Baoquan He
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=20200510130646.GA4922@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=david@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.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.