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 (re-diff against firstfloor tree)
Date: Thu, 29 Mar 2007 15:54:07 +0200 [thread overview]
Message-ID: <200703291554.08017.ak@suse.de> (raw)
In-Reply-To: <460BDFF9.76E4.0078.0@novell.com>
On Thursday 29 March 2007 15:49, Jan Beulich wrote:
> >>> Andi Kleen <ak@suse.de> 29.03.07 14:22 >>>
> >On Thursday 29 March 2007 14:01, Jan Beulich wrote:
> >> On x86-64, kernel memory freed after init can be entirely unmapped instead
> >> of just getting 'poisoned' by overwriting with a debug pattern.
> >>
> >> On i386 and x86-64 (under CONFIG_DEBUG_RODATA), kernel text and bug table
> >> can also be write-protected.
> >>
> >> (Not sure what the symbol 'stext' is good for; can it be removed?)
> >
> >I see you remove it already
>
> I don't think I do - I just move _stext (on x86-64), but leave stext alone.
Ok i removed it now
-Andi
prev parent reply other threads:[~2007-03-29 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 12:01 [PATCH] x86: tighten kernel image page access rights (re-diff against firstfloor tree) Jan Beulich
2007-03-29 12:22 ` Andi Kleen
2007-03-29 13:49 ` Jan Beulich
2007-03-29 13:54 ` 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=200703291554.08017.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