All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-mm@kvack.org, x86@kernel.org
Subject: Re: x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a0000
Date: Wed, 19 Sep 2018 10:09:24 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1809191004580.1468@nanos.tec.linutronix.de> (raw)
In-Reply-To: <e75fa739-4bcc-dc30-2606-25d2539d2653@molgen.mpg.de>

Paul,

On Wed, 19 Sep 2018, Paul Menzel wrote:
> 
> With Linux 4.19-rc4+ and `CONFIG_DEBUG_WX=y`, I see the message below on
> the ASRock E350M1.
> 
> > [    1.813378] Freeing unused kernel image memory: 1112K
> > [    1.818662] Write protecting the kernel text: 8708k
> > [    1.818987] Write protecting the kernel read-only data: 2864k
> > [    1.818989] NX-protecting the kernel data: 5628k
> > [    1.819265] ------------[ cut here ]------------
> > [    1.819272] x86/mm: Found insecure W+X mapping at address
> > (ptrval)/0xc00a0000
> 
> I do not notice any problems with the system, but maybe something can be done
> to get rid of these.

Can you please enable CONFIG_X86_PTDUMP and provide the output of the files
in /sys/kernel/debug/page_tables/ ?

Thanks,

	tglx

  reply	other threads:[~2018-09-19  8:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  6:55 x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a0000 Paul Menzel
2018-09-19  8:09 ` Thomas Gleixner [this message]
2018-09-20  7:07   ` Paul Menzel
2018-09-20 22:51     ` Thomas Gleixner
2018-09-24 21:47       ` Paul Menzel
2018-09-28 14:55         ` Thomas Gleixner
2018-10-03 21:22           ` Borislav Petkov
2018-10-04  3:11             ` Paul Menzel
2018-10-04  7:48               ` Borislav Petkov
2018-10-04  8:03             ` Joerg Roedel
2018-10-04  8:14               ` Borislav Petkov
2018-10-04  8:40                 ` Paul Menzel
2018-10-04  8:49                   ` Borislav Petkov
2018-10-04  8:59                     ` Paul Menzel
2018-10-04 10:54                       ` Borislav Petkov
2018-10-04 11:00                         ` Paul Menzel
2018-10-04 11:12                           ` Borislav Petkov
2018-10-04  8:43                 ` Joerg Roedel
2018-10-04  8:48                   ` Borislav Petkov
2018-10-05  9:27               ` Thomas Gleixner
2018-10-05  9:39                 ` Paul Menzel
2018-10-08 19:37                   ` Thomas Gleixner
2018-10-08 20:08                     ` Bjorn Helgaas

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=alpine.DEB.2.21.1809191004580.1468@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-mm@kvack.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.