From: Borislav Petkov <bp@alien8.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Jörg Rödel" <joro@8bytes.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-mm@kvack.org, x86@kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a0000
Date: Thu, 4 Oct 2018 13:12:58 +0200 [thread overview]
Message-ID: <20181004111258.GJ1864@zn.tnic> (raw)
In-Reply-To: <fa6086e6-5f89-ec11-d14c-78f8f761b8b7@molgen.mpg.de>
On Thu, Oct 04, 2018 at 01:00:42PM +0200, Paul Menzel wrote:
> While here you write, it did not.
Read again what I said:
> and I did try marking the ISA range RO in mark_rodata_ro() but the
> machine wouldn't boot after.
and the code I pasted has this:
// init_memory_mapping(0, ISA_END_ADDRESS);
which is disabling the direct mapping of the ISA range.
Two very different things.
And you don't absolutely need to try it because it would simply move the
warning to another address, just like it happened on my system. Because
looking at your dmesg, that E350M1 machine is very similar to the laptop
I have. But feel free if you have time on your hands... :)
> Sorry I do not understand the question. I carry the SSD drive with
> me, and connect it to the ASRock E350M1 (64-bit) or to the Lenovo
> X60 laptop and boot from it from both systems.
So it is an OS installation which you swap between two machines. I
admit, it is the first time I hear of such a use case. In that case,
yes, bitness does matter.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-10-04 11:13 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
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 [this message]
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=20181004111258.GJ1864@zn.tnic \
--to=bp@alien8.de \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pmenzel@molgen.mpg.de \
--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 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.