From: Borislav Petkov <bp@alien8.de>
To: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
Cc: linux-efi@vger.kernel.org, matt.fleming@intel.com,
linux-kernel@vger.kernel.org,
Ricardo Neri <ricardo.neri@intel.com>,
Glenn P Williamson <glenn.p.williamson@intel.com>,
Ravi Shankar <ravi.v.shankar@intel.com>
Subject: Re: [PATCH] x86/efi: Fix kernel panic when CONFIG_DEBUG_VIRTUAL is enabled
Date: Wed, 14 Oct 2015 16:41:34 +0200 [thread overview]
Message-ID: <20151014144134.GA8263@pd.tnic> (raw)
In-Reply-To: <1444765377-29303-1-git-send-email-sai.praneeth.prakhya@intel.com>
On Tue, Oct 13, 2015 at 12:42:57PM -0700, Sai Praneeth Prakhya wrote:
> From: Sai Praneeth <sai.praneeth.prakhya@intel.com>
>
> When CONFIG_DEBUG_VIRTUAL is turned on, all accesses to __pa(address)
> are monitored to see whether address falls in direct mapping or kernel
> mapping,
make that
"... or kernel text mapping (see Documentation/x86/x86_64/mm.txt for
details)"
for more clarity please. It just took mfleming and me a while to figure
out what what is.
> if it does not kernel panics. During 1:1 mapping of EFI runtime
> services we access addresses which are below 4G and hence when passed as
not "below 4G" but "we access virtual adresses which are == physical
addresses, thus the 1:1 mapping" - on a box with more than 4G, physical
addresses can be above 4G too :)
> arguments to __pa() kernel panics as reported by Dave Hansen here
> https://lkml.org/lkml/2015/1/27/742.
Please quote this mail with the k.org redirector:
https://lkml.kernel.org/r/5462999A.7090706@intel.com
lkml.org is unreliable.
> So, before calling __pa() virtual
> addresses should be validated which results in skipping call to
> split_page_count() and that should be fine because it is used to keep
> track of direct kernel mappings and not 1:1 mappings.
I think that should say:
"to keep track of everything *but* 1:1 mappings."
The 1:1 mappings are EFI-specific thing and the physaddr.c checkers
aren't aware of them.
Again, IMHO.
> Signed-off-by: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
> Reported-by: Dave Hansen <dave.hansen@intel.com>
> Cc: Matt Fleming <matt.fleming@intel.com>
> Cc: Ricardo Neri <ricardo.neri@intel.com>
> Cc: Glenn P Williamson <glenn.p.williamson@intel.com>
> Cc: Ravi Shankar <ravi.v.shankar@intel.com>
> ---
> arch/x86/mm/pageattr.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/mm/pageattr.c b/arch/x86/mm/pageattr.c
> index 727158cb3b3c..3a603830503a 100644
> --- a/arch/x86/mm/pageattr.c
> +++ b/arch/x86/mm/pageattr.c
> @@ -648,9 +648,11 @@ __split_large_page(struct cpa_data *cpa, pte_t *kpte, unsigned long address,
> for (i = 0; i < PTRS_PER_PTE; i++, pfn += pfninc)
> set_pte(&pbase[i], pfn_pte(pfn, canon_pgprot(ref_prot)));
>
> - if (pfn_range_is_mapped(PFN_DOWN(__pa(address)),
> - PFN_DOWN(__pa(address)) + 1))
> - split_page_count(level);
> + if (virt_addr_valid(address)) {
> + if (pfn_range_is_mapped(PFN_DOWN(__pa(address)),
> + PFN_DOWN(__pa(address)) + 1))
> + split_page_count(level);
Maybe make it a bit more readable:
if (virt_addr_valid(address)) {
unsigned long pfn = PFN_DOWN(__pa(address));
if (pfn_range_is_mapped(pfn, pfn + 1))
split_page_count(level);
}
But yeah, patch makes sense to me.
Thanks for fixing that!
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2015-10-14 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 19:42 [PATCH] x86/efi: Fix kernel panic when CONFIG_DEBUG_VIRTUAL is enabled Sai Praneeth Prakhya
2015-10-14 14:41 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-25 10:49 [GIT PULL] EFI changes for v4.4 Matt Fleming
2015-10-25 10:49 ` [PATCH] x86/efi: Fix kernel panic when CONFIG_DEBUG_VIRTUAL is enabled Matt Fleming
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=20151014144134.GA8263@pd.tnic \
--to=bp@alien8.de \
--cc=glenn.p.williamson@intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri@intel.com \
--cc=sai.praneeth.prakhya@intel.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