public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Juergen Gross <jgross@suse.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86: consider effective protection attributes in W+X check
Date: Wed, 21 Feb 2018 17:53:44 +0100	[thread overview]
Message-ID: <20180221165344.ioxrxbsd6kkrhr2v@gmail.com> (raw)
In-Reply-To: <5A8D917302000078001AA055@prv-mh.provo.novell.com>


* Jan Beulich <JBeulich@suse.com> wrote:

> Using just the leaf page table entry flags would cause a false warning
> in case _PAGE_RW is clear or _PAGE_NX is set in a higher level entry.
> Hand through both the current entry's flags as well as the accumulated
> effective value (the latter as pgprotval_t instead of pgprot_t, as it's
> not an actual entry's value).
> 
> This in particular eliminates the false W+X warning when running under
> Xen, as commit 2cc42bac1c ("x86-64/Xen: eliminate W+X mappings") has to
> make the necessary adjustment in L2 rather than L1 (the reason is
> explained there). I.e. _PAGE_RW is clear there in L1, but _PAGE_NX is
> set in L2.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Reviewed-by: Juergen Gross <jgross@suse.com>
> ---
> v2: Re-base onto tip tree. Add Xen related paragraph to description.
> ---
>  arch/x86/mm/dump_pagetables.c |   92 ++++++++++++++++++++++++++----------------
>  1 file changed, 57 insertions(+), 35 deletions(-)

There's a build failure with CONFIG_KASAN=y enabled:

 arch/x86/mm/dump_pagetables.c: In function ‘kasan_page_table’:
 arch/x86/mm/dump_pagetables.c:365:3: error: too few arguments to function ‘note_page’
 arch/x86/mm/dump_pagetables.c:238:13: note: declared here

Thanks,

	Ingo

  reply	other threads:[~2018-02-21 16:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 14:34 [PATCH v2] x86: consider effective protection attributes in W+X check Jan Beulich
2018-02-21 16:53 ` Ingo Molnar [this message]
2018-02-22 10:13   ` Jan Beulich
2018-02-23  7:49     ` Ingo Molnar
2018-02-23  7:57       ` Jan Beulich
2018-02-23  8:27 ` [PATCH v3] " Jan Beulich
2018-02-23 10:13   ` [tip:x86/mm] x86/mm: Consider " tip-bot for Jan Beulich
2018-02-26  8:48   ` tip-bot for Jan Beulich
2018-02-26 10:00     ` Andrey Ryabinin
2018-02-26 10:08       ` Jan Beulich
2018-02-26 10:47         ` Andrey Ryabinin
2018-02-26 10:54           ` Jan Beulich
2018-02-26 12:46             ` Andrey Ryabinin

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=20180221165344.ioxrxbsd6kkrhr2v@gmail.com \
    --to=mingo@kernel.org \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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