From: Ben Hutchings <ben@decadent.org.uk>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>, Yinghai Lu <yinghai@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH][v3.2] Revert: x86, 64bit, mm: Mark data/bss/brk to nx
Date: Mon, 19 Jan 2015 22:07:11 +0000 [thread overview]
Message-ID: <1421705231.31046.191.camel@decadent.org.uk> (raw)
In-Reply-To: <20150119164926.168e8101@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 2461 bytes --]
On Mon, 2015-01-19 at 16:49 -0500, Steven Rostedt wrote:
> Testing v3.2-rt I found that after merging the latest v3.2 stable tree,
> hotplug stopped working. I tested the latest v3.2 stable, and it was
> not working there either. I bisected it down to:
>
> commit e105c8187b7101e8a8a54ac0218c9d9c9463c636
> Author: Yinghai Lu <yinghai@kernel.org>
> Date: Thu Jan 24 12:20:13 2013 -0800
>
> x86, 64bit, mm: Mark data/bss/brk to nx
>
> commit 72212675d1c96f5db8ec6fb35701879911193158 upstream.
>
> Simply doing:
>
> # echo 0 > /sys/devices/system/cpu/cpu1/online
> # echo 1 > /sys/devices/system/cpu/cpu1/online
>
> caused the system to reboot.
>
> After reverting that commit, hotplug works again on the v3.2 stable
> tree.
Yes, I know this needs fixing. It also broke suspend/resume on SMP
machines since that involves offlining and onlining CPUs 1-n.
Ben.
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
> diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
> index 266f71719e42..783eba48d00c 100644
> --- a/arch/x86/mm/init_64.c
> +++ b/arch/x86/mm/init_64.c
> @@ -778,7 +778,6 @@ void mark_rodata_ro(void)
> unsigned long text_end = PAGE_ALIGN((unsigned long) &__stop___ex_table);
> unsigned long rodata_end = PAGE_ALIGN((unsigned long) &__end_rodata);
> unsigned long data_start = (unsigned long) &_sdata;
> - unsigned long all_end;
>
> printk(KERN_INFO "Write protecting the kernel read-only data: %luk\n",
> (end - start) >> 10);
> @@ -787,8 +786,8 @@ void mark_rodata_ro(void)
> kernel_set_to_readonly = 1;
>
> /*
> - * The rodata/data/bss/brk section (but not the kernel text!)
> - * should also be not-executable.
> + * The rodata section (but not the kernel text!) should also be
> + * not-executable.
> *
> * We align all_end to PMD_SIZE because the existing mapping
> * is a full PMD. If we would align _brk_end to PAGE_SIZE we
> @@ -798,8 +797,7 @@ void mark_rodata_ro(void)
> * Any PMD which was setup after the one which covers _brk_end
> * has been zapped already via cleanup_highmem().
> */
> - all_end = roundup((unsigned long)_brk_end, PMD_SIZE);
> - set_memory_nx(rodata_start, (all_end - rodata_start) >> PAGE_SHIFT);
> + set_memory_nx(rodata_start, (end - rodata_start) >> PAGE_SHIFT);
>
> rodata_test();
>
--
Ben Hutchings
Larkinson's Law: All laws are basically false.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-01-19 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 21:49 [PATCH][v3.2] Revert: x86, 64bit, mm: Mark data/bss/brk to nx Steven Rostedt
2015-01-19 22:07 ` Ben Hutchings [this message]
2015-01-19 22:19 ` Steven Rostedt
2015-01-20 16:06 ` Ben Hutchings
2015-01-20 16:12 ` Steven Rostedt
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=1421705231.31046.191.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=yinghai@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