public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
	arjan@infradead.org, mingo@elte.hu, tglx@linutronix.de
Subject: 4.10 kernel on thinkpad x220: rodata_test: test data was not read only
Date: Tue, 21 Feb 2017 23:14:25 +0100	[thread overview]
Message-ID: <20170221221425.GB6918@amd> (raw)

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

Hi!

I'm getting

[    3.822386] VFS: Mounted root (ext4 filesystem) readonly on device
8:4.
[    3.840420] devtmpfs: mounted
[    3.842346] Freeing unused kernel memory: 536K
[    3.844081] Write protecting the kernel text: 11764k
[    3.845753] Write protecting the kernel read-only data: 4780k
[    3.847326] rodata_test: test data was not read only
[    3.848906] NX-protecting the kernel data: 6668k
[    3.850662] x86/mm: Checked W+X mappings: passed, no W+X pages
found.

I guess that means that kernel hardening does not work as
expected... 32bit kernel on thinkpad x220.

Git blame points to

commit edeed30589f5defe63ce6aaae56f2b7c855e4520
Author: Arjan van de Ven <arjan@infradead.org>
Date:   Wed Jan 30 13:34:08 2008 +0100

    x86: add testcases for RODATA and NX protections/attributes

Any ideas?
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2017-02-21 22:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 22:14 Pavel Machek [this message]
     [not found] ` <CADyApD3UMZaSwBSDVvx1=NLfE14r-zspty=9EDJ7YXs8Oejz8Q@mail.gmail.com>
2017-02-23 22:16   ` 4.10 kernel on thinkpad x220: rodata_test: test data was not read only Pavel Machek

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=20170221221425.GB6918@amd \
    --to=pavel@ucw.cz \
    --cc=arjan@infradead.org \
    --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