From: Baoquan He <bhe@redhat.com>
To: Coiby Xu <coxu@redhat.com>
Cc: kexec@lists.infradead.org, "Ondrej Kozina" <okozina@redhat.com>,
"Milan Broz" <gmazyland@gmail.com>,
"Thomas Staudt" <tstaudt@de.ibm.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Kairui Song" <ryncsn@gmail.com>,
"Jan Pazdziora" <jpazdziora@redhat.com>,
"Pingfan Liu" <kernelfans@gmail.com>,
"Dave Young" <dyoung@redhat.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
"Dave Hansen" <dave.hansen@intel.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
"Greg KH" <gregkh@linuxfoundation.org>,
"Eric Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH v6 1/7] kexec_file: allow to place kexec_buf randomly
Date: Fri, 29 Nov 2024 09:38:58 +0800 [thread overview]
Message-ID: <Z0kbMm0HCZQcD2bI@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20241029055223.210039-2-coxu@redhat.com>
On 10/29/24 at 01:52pm, Coiby Xu wrote:
> Currently, kexec_buf is placed in order which means for the same
> machine, the info in the kexec_buf is always located at the same
> position each time the machine is booted. This may cause a risk for
> sensitive information like LUKS volume key. Now struct kexec_buf has a
> new field random which indicates it's supposed to be placed in a random
> position.
This change the generic code, but you don't mention this only takes
effect in kdump case, won't impact kexec reboot case. I got this from
code, while this should be mentioned in log.
>
> Suggested-by: Jan Pazdziora <jpazdziora@redhat.com>
> Signed-off-by: Coiby Xu <coxu@redhat.com>
> ---
> include/linux/kexec.h | 28 ++++++++++++++++++++++++++++
> kernel/kexec_file.c | 3 +++
> 2 files changed, 31 insertions(+)
>
> diff --git a/include/linux/kexec.h b/include/linux/kexec.h
> index f0e9f8eda7a3..0dc66ca2506a 100644
> --- a/include/linux/kexec.h
> +++ b/include/linux/kexec.h
> @@ -25,6 +25,10 @@
>
> extern note_buf_t __percpu *crash_notes;
>
> +#ifdef CONFIG_CRASH_DUMP
> +#include <linux/prandom.h>
> +#endif
> +
> #ifdef CONFIG_KEXEC_CORE
> #include <linux/list.h>
> #include <linux/compat.h>
> @@ -171,6 +175,7 @@ int kexec_image_post_load_cleanup_default(struct kimage *image);
> * @buf_min: The buffer can't be placed below this address.
> * @buf_max: The buffer can't be placed above this address.
> * @top_down: Allocate from top of memory.
> + * @random: Place the buffer at a random position.
> */
> struct kexec_buf {
> struct kimage *image;
> @@ -182,8 +187,31 @@ struct kexec_buf {
> unsigned long buf_min;
> unsigned long buf_max;
> bool top_down;
> +#ifdef CONFIG_CRASH_DUMP
> + bool random;
> +#endif
> };
>
> +
> +#ifdef CONFIG_CRASH_DUMP
> +static inline void kexec_random_start(unsigned long start, unsigned long end,
~~~~~~~~~~~~~~~~~~
This function name is very confusing. I thought it's a starting to
randomize at the first glance, then realized it's to randomize the
starting position of range.
> + struct kexec_buf *kbuf,
> + unsigned long *temp_start)
> +{
> + unsigned short i;
> +
> + if (kbuf->random) {
> + get_random_bytes(&i, sizeof(unsigned short));
> + *temp_start = start + (end - start) / USHRT_MAX * i;
> + }
> +}
> +#else
> +static inline void kexec_random_start(unsigned long start, unsigned long end,
> + struct kexec_buf *kbuf,
> + unsigned long *temp_start)
> +{}
> +#endif
> +
> int kexec_load_purgatory(struct kimage *image, struct kexec_buf *kbuf);
> int kexec_purgatory_get_set_symbol(struct kimage *image, const char *name,
> void *buf, unsigned int size,
> diff --git a/kernel/kexec_file.c b/kernel/kexec_file.c
> index 3eedb8c226ad..06565d867b69 100644
> --- a/kernel/kexec_file.c
> +++ b/kernel/kexec_file.c
> @@ -445,6 +445,7 @@ static int locate_mem_hole_top_down(unsigned long start, unsigned long end,
>
> temp_end = min(end, kbuf->buf_max);
> temp_start = temp_end - kbuf->memsz + 1;
> + kexec_random_start(temp_start, temp_end, kbuf, &temp_start);
>
> do {
> /* align down start */
> @@ -483,6 +484,8 @@ static int locate_mem_hole_bottom_up(unsigned long start, unsigned long end,
>
> temp_start = max(start, kbuf->buf_min);
>
> + kexec_random_start(temp_start, end, kbuf, &temp_start);
> +
> do {
> temp_start = ALIGN(temp_start, kbuf->buf_align);
> temp_end = temp_start + kbuf->memsz - 1;
> --
> 2.47.0
>
next prev parent reply other threads:[~2024-11-29 1:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 5:52 [PATCH v6 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys Coiby Xu
2024-10-29 5:52 ` [PATCH v6 1/7] kexec_file: allow to place kexec_buf randomly Coiby Xu
2024-11-29 1:38 ` Baoquan He [this message]
2024-12-02 10:04 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 2/7] crash_dump: make dm crypt keys persist for the kdump kernel Coiby Xu
2024-10-29 5:52 ` [PATCH v6 3/7] crash_dump: store dm crypt keys in kdump reserved memory Coiby Xu
2024-10-29 14:41 ` kernel test robot
2024-11-01 7:16 ` Coiby Xu
2024-12-11 12:58 ` Baoquan He
2024-12-23 1:05 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 4/7] crash_dump: reuse saved dm crypt keys for CPU/memory hot-plugging Coiby Xu
2024-12-11 13:08 ` Baoquan He
2024-12-23 0:41 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 5/7] crash_dump: retrieve dm crypt keys in kdump kernel Coiby Xu
2024-10-29 5:52 ` [PATCH v6 6/7] x86/crash: pass dm crypt keys to " Coiby Xu
2024-12-11 12:55 ` Baoquan He
2024-12-23 1:16 ` Coiby Xu
2024-12-26 3:48 ` Baoquan He
2025-01-03 2:24 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 7/7] x86/crash: make the page that stores the dm crypt keys inaccessible Coiby Xu
2024-11-04 6:17 ` [PATCH v6 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys Baoquan He
2024-12-03 17:53 ` David Woodhouse
2024-12-11 1:33 ` Baoquan He
2024-12-14 2:24 ` Baoquan He
2024-12-23 1:19 ` Coiby Xu
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=Z0kbMm0HCZQcD2bI@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=berrange@redhat.com \
--cc=coxu@redhat.com \
--cc=dave.hansen@intel.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gmazyland@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jpazdziora@redhat.com \
--cc=kernelfans@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okozina@redhat.com \
--cc=ryncsn@gmail.com \
--cc=tstaudt@de.ibm.com \
--cc=vkuznets@redhat.com \
--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