linux-kernel - Re: [PATCH] x86/kexec: fix incorrect end address passed to kernel_ident_mapping

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20231222150227.95193-1-ytcoode@gmail.com>
Date: Fri, 22 Dec 2023 23:02:27 +0800
From: Yuntao Wang <ytcoode@...il.com>
To: akpm@...ux-foundation.org
Cc: bhe@...hat.com,
	bhelgaas@...gle.com,
	bp@...en8.de,
	dave.hansen@...ux.intel.com,
	horms@...nel.org,
	hpa@...or.com,
	linux-kernel@...r.kernel.org,
	mingo@...hat.com,
	tglx@...utronix.de,
	x86@...nel.org,
	ytcoode@...il.com
Subject: Re: [PATCH] x86/kexec: fix incorrect end address passed to kernel_ident_mapping_init()

On Thu, 21 Dec 2023 14:03:00 -0800, Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Thu, 21 Dec 2023 18:17:02 +0800 Yuntao Wang <ytcoode@...il.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?

Passing [start, end] rather than [start, end+1) to kernel_ident_mapping_init()
may result in the identity mapping for the end address not being set up.

For example, when res->start is equal to res->end, kernel_ident_mapping_init()
will not establish any identity mapping. Similarly, when the value of res->end
is a multiple of 2M and the page table maps 2M pages, kernel_ident_mapping_init()
will also not set up identity mapping for res->end.