[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5649FCA1.1000600@intel.com>
Date: Mon, 16 Nov 2015 07:56:17 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Matt Fleming <matt@...eblueprint.co.uk>,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H . Peter Anvin" <hpa@...or.com>
Cc: Toshi Kani <toshi.kani@...com>, linux-kernel@...r.kernel.org,
linux-efi@...r.kernel.org,
Sai Praneeth Prakhya <sai.praneeth.prakhya@...el.com>,
Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH v2 1/5] x86/mm/pageattr: Ensure cpa->pfn only contains
page frame numbers
I'm glad you're looking at this. It obviously needed some love. :)
On 11/14/2015 02:00 PM, Matt Fleming wrote:
> + npages = (_end - _text) >> PAGE_SHIFT;
> + text = __pa(_text);
> + pfn = text >> PAGE_SHIFT;
> +
> + if (kernel_map_pages_in_pgd(pgd, pfn, text, npages, 0)) {
> + pr_err("Failed to map kernel text 1:1\n");
> + return 1;
> + }
Are _end and _text guaranteed to be aligned? If not, I think the
calculation might be wrong. Just for fun, imagine that _end=0xfff and
_text=0x1001. npages would be 0.
Some other code like set_kernel_text_rw() does alignment on _text.
One nit is that there's quite a bit going on here, like rearranging the
phys_stack arithmetic ordering that is far beyond just simplifying the
paddr vs. pfn issue, but that isn't called out in the changelog at all.
Your fixes all look correct to me, fwiw.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists