From: Piotr Gregor <piotrgregor@rsyncme.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [BUG] x86/mm: Found insecure W+X mapping at address ffff88000005f000/0xffff88000005f000
Date: Tue, 18 Jul 2017 19:19:00 +0100 [thread overview]
Message-ID: <20170718181859.GA13340@westernst> (raw)
In-Reply-To: <alpine.DEB.2.20.1707181410390.1945@nanos>
On Tue, Jul 18, 2017 at 02:11:35PM +0200, Thomas Gleixner wrote:
> On Tue, 18 Jul 2017, Piotr Gregor wrote:
> >
> > Dmesg reports insecure W+X mapping found at address
> > ffff88000005f000/0xffff88000005f000
> >
> > on 4.4.70 kernel patched with -rt83 patch:
>
> Does the same problem happen with a plain 4.4.70? as well?
>
> Thanks,
>
> tglx
>
Hi Thomas,
No. I will tell if I spot this.
cheers,
Piotr
prev parent reply other threads:[~2017-07-18 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 8:50 [BUG] x86/mm: Found insecure W+X mapping at address ffff88000005f000/0xffff88000005f000 Piotr Gregor
2017-07-18 12:11 ` Thomas Gleixner
2017-07-18 18:19 ` Piotr Gregor [this message]
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=20170718181859.GA13340@westernst \
--to=piotrgregor@rsyncme.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).