public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Siarhei Liakh <sliakh.lkml@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Arjan van de Ven <arjan@infradead.org>,
	James Morris <jmorris@namei.org>,
	Andrew Morton <akpm@linux-foundation.org>, Andi Kleen <ak@muc.de>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH V2] x86: NX protection for kernel data
Date: Mon, 31 Aug 2009 12:39:49 +0200	[thread overview]
Message-ID: <20090831103948.GA1353@ucw.cz> (raw)
In-Reply-To: <817ecb6f0908261020y2267218h8f435e8dc392f69a@mail.gmail.com>

Hi!

> --- a/init/main.c
> +++ b/init/main.c
> @@ -7,6 +7,8 @@
>   *  Added initrd & change_root: Werner Almesberger & Hans Lermen, Feb '96
>   *  Moan early if gcc is old, avoiding bogus kernels - Paul Gortmaker, May '96
>   *  Simplified starting of init:  Michael A. Griffith <grif@acm.org>
> + *  Data NX protection by Siarhei Liakh <sliakh.lkml@gmail.com>
> + *  and Xuxian Jiang <jiang@cs.ncsu.edu>
>   */

Better delete the changelog and add yourself to credits. Changelogs in
.c files are considered bad these days. (Feel free to kill the old
entries, too.)

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

  parent reply	other threads:[~2009-08-31 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 17:20 [PATCH V2] x86: NX protection for kernel data Siarhei Liakh
2009-08-28  8:52 ` Amerigo Wang
2009-08-31 10:39 ` Pavel Machek [this message]
2009-08-31 11:44   ` James Morris

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=20090831103948.GA1353@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ak@muc.de \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --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