From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: linux-kernel@vger.kernel.org, patches@x86-64.org
Subject: Re: [PATCH] x86: tighten kernel image page access rights
Date: Thu, 29 Mar 2007 11:53:07 +0200 [thread overview]
Message-ID: <200703291153.07557.ak@suse.de> (raw)
In-Reply-To: <460B843C.76E4.0078.0@novell.com>
On Thursday 29 March 2007 09:17, Jan Beulich wrote:
> >>> Andi Kleen <ak@suse.de> 28.03.07 21:07 >>>
> >
> >> +#ifdef CONFIG_HOTPLUG_CPU
> >> + /* It must still be possible to apply SMP alternatives. */
> >> + if (num_possible_cpus() <= 1)
> >
> >It would be better to temporarily change the pages where the alternatives
> >are applied while that is done and keep it otherwise ro
>
> I had considered that, but not done so due to the larger resulting patch.
> Are you okay with doing this as a follow-up step?
Yes. I tried to apply the original patch, but gots lots of rejects.
Can you please resubmit that one against the latest firstfloor tree?
-Andi
prev parent reply other threads:[~2007-03-29 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 14:14 [PATCH] x86: tighten kernel image page access rights Jan Beulich
2007-03-28 19:07 ` Andi Kleen
2007-03-29 7:17 ` Jan Beulich
2007-03-29 9:53 ` Andi Kleen [this message]
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=200703291153.07557.ak@suse.de \
--to=ak@suse.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.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