mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Yuntao Wang <ytcoode@gmail.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	Baoquan He <bhe@redhat.com>, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Simon Horman <horms@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] x86/kexec: fix incorrect end address passed to kernel_ident_mapping_init()
Date: Thu, 21 Dec 2023 14:03:00 -0800	[thread overview]
Message-ID: <20231221140300.4fcfd4945eeb3b6c145a969c@linux-foundation.org> (raw)
In-Reply-To: <20231221101702.20956-1-ytcoode@gmail.com>

On Thu, 21 Dec 2023 18:17:02 +0800 Yuntao Wang <ytcoode@gmail.com> wrote:

> kernel_ident_mapping_init() takes an exclusive memory range [pstart, pend)
> where pend is not included in the range, while res represents an inclusive
> memory range [start, end] where end is considered part of the range.
> 
> Therefore, passing res->end directly to kernel_ident_mapping_init() is
> incorrect, the correct end address should be `res->end + 1`.
> 
> ...
>
> --- a/arch/x86/kernel/machine_kexec_64.c
> +++ b/arch/x86/kernel/machine_kexec_64.c
> @@ -44,7 +44,7 @@ static int mem_region_callback(struct resource *res, void *arg)
>  	struct init_pgtable_data *data = arg;
>  
>  	return kernel_ident_mapping_init(data->info, data->level4p,
> -					 res->start, res->end);
> +					 res->start, res->end + 1);
>  }

Thanks.  When fixing a bug, please always full describe the
userspace-visible effects of that bug.

In this case I'm assuming "none", due to kernel_ident_mapping_init()'s
upward rounding of the address?

  reply	other threads:[~2023-12-21 22:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 10:17 Yuntao Wang
2023-12-21 22:03 ` Andrew Morton [this message]
2023-12-22 15:02   ` Yuntao Wang

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=20231221140300.4fcfd4945eeb3b6c145a969c@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=horms@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=ytcoode@gmail.com \
    /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®