From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Borislav Petkov <bp@alien8.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:00:42 +0200 [thread overview]
Message-ID: <fa6086e6-5f89-ec11-d14c-78f8f761b8b7@molgen.mpg.de> (raw)
In-Reply-To: <20181004105443.GH1864@zn.tnic>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
Dear Borislav,
On 10/04/18 12:54, Borislav Petkov wrote:
> On Thu, Oct 04, 2018 at 10:59:18AM +0200, Paul Menzel wrote:
>> I meant just the test you did.
>
> https://lkml.kernel.org/r/20181003212255.GB28361@zn.tnic
I see. But there you write, the machine does boot.
While here you write, it did not.
> and I did try marking the ISA range RO in mark_rodata_ro() but the
> machine wouldn't boot after.
>> The SSD is also used in the Lenovo X60 and T60, which are
>> 32-bit systems.
>
> And what exactly is the problem when you access it on a 64-bit OS?
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.
Kind regards,
Paul
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2018-10-04 11:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 6:55 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 [this message]
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=fa6086e6-5f89-ec11-d14c-78f8f761b8b7@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=bp@alien8.de \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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