From: Ingo Molnar <mingo@elte.hu>
To: mingo@redhat.com, hpa@zytor.com, sliakh.lkml@gmail.com,
jmorris@namei.org, linux-kernel@vger.kernel.org,
arjan@linux.intel.com, tglx@linutronix.de, jiang@cs.ncsu.edu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/mm] x86, mm: NX protection for kernel data
Date: Mon, 22 Feb 2010 12:01:06 +0100 [thread overview]
Message-ID: <20100222110106.GA7206@elte.hu> (raw)
In-Reply-To: <20100222105457.GA31148@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
>
> * tip-bot for Siarhei Liakh <sliakh.lkml@gmail.com> wrote:
>
> > Commit-ID: 01ab31371da90a795b774d87edf2c21bb3a64dda
> > Gitweb: http://git.kernel.org/tip/01ab31371da90a795b774d87edf2c21bb3a64dda
> > Author: Siarhei Liakh <sliakh.lkml@gmail.com>
> > AuthorDate: Sun, 31 Jan 2010 18:27:55 -0500
> > Committer: H. Peter Anvin <hpa@zytor.com>
> > CommitDate: Wed, 17 Feb 2010 10:11:24 -0800
> >
> > x86, mm: NX protection for kernel data
> >
> > This patch expands functionality of CONFIG_DEBUG_RODATA to set main
> > (static) kernel data area as NX.
>
> -tip testing is seeing boot hangs along the lines of:
>
> [ 15.568108] EXT3-fs (sda1): recovery complete
> [ 15.573064] EXT3-fs (sda1): mounted filesystem with ordered data mode
> [ 15.580313] VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
> [ 15.584021] async_waiting @ 1
> [ 15.588008] async_continuing @ 1 after 0 usec
> [ 15.592163] Freeing unused kernel memory: 540k freed
> [ 15.600126] NX-protecting the kernel data: c15ab000, 2919 pages
>
> which i suspect could be due to the commit above.
Yep, that's confirmed now, applying these 3 reverts makes it boot fine:
833e0ca: Revert "x86, mm: NX protection for kernel data"
ce4b6b4: Revert "x86: RO/NX protection for loadable kernel modules"
e357312: Revert "module: fix () used as prototype in include/linux/module.h"
Ingo
next prev parent reply other threads:[~2010-02-22 11:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 23:27 [PATCH V6] x86: NX protection for kernel data Siarhei Liakh
2010-02-01 21:40 ` James Morris
2010-02-17 19:51 ` [tip:x86/mm] x86, mm: " tip-bot for Siarhei Liakh
2010-02-22 10:54 ` Ingo Molnar
2010-02-22 11:01 ` Ingo Molnar [this message]
2010-02-22 17:19 ` H. Peter Anvin
2010-02-22 17:21 ` Ingo Molnar
2010-03-06 19:44 ` Siarhei Liakh
2010-03-10 13:32 ` Ingo Molnar
2010-03-10 15:06 ` Siarhei Liakh
2010-03-12 3:12 ` Siarhei Liakh
2010-03-02 15:13 ` Siarhei Liakh
-- strict thread matches above, loose matches on Subject: below --
2010-03-02 16:23 castet.matthieu
2010-03-02 17:51 ` Siarhei Liakh
2010-03-02 18:03 ` Siarhei Liakh
2010-03-13 12:12 matthieu castet
2010-03-15 18:20 ` Siarhei Liakh
2010-03-15 21:40 ` Siarhei Liakh
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=20100222110106.GA7206@elte.hu \
--to=mingo@elte.hu \
--cc=arjan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jiang@cs.ncsu.edu \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sliakh.lkml@gmail.com \
--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