From: Greg KH <gregkh@linuxfoundation.org>
To: kernel-hardening@lists.openwall.com
Cc: Kees Cook <keescook@chromium.org>
Subject: Re: [kernel-hardening] patches for __write_rarely section
Date: Wed, 16 Nov 2016 17:14:46 +0100 [thread overview]
Message-ID: <20161116161446.GA22095@kroah.com> (raw)
In-Reply-To: <CAAseMr6Fae=4otZZX9HmO1YgehjsVmd+44G5RN7Wu8iF2+fruA@mail.gmail.com>
On Wed, Nov 16, 2016 at 10:39:38PM +0800, Gengjia Chen wrote:
> From: chengengjia <chengjia4574@gmail.com>
> Date: Wed, 16 Nov 2016 21:46:49 +0800
> Subject: [PATCH] arch: introduce write-rarely memory section
>
> This introduces __write_rarely section as a way
> to mark those memory that read only in most case,
> but also need to be written to sometimes.
>
> Signed-off-by: chengengjia <chengjia4574@gmail.com>
Minor nit, please use your full/real name for From: and signed-off-by:
lines.
thanks,
greg k-h
prev parent reply other threads:[~2016-11-16 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 14:39 [kernel-hardening] patches for __write_rarely section Gengjia Chen
2016-11-16 15:16 ` Mark Rutland
2016-11-17 23:47 ` Kees Cook
2016-11-18 11:10 ` Mark Rutland
2016-11-18 11:42 ` Mark Rutland
2016-11-16 15:22 ` Rik van Riel
2016-11-16 16:14 ` Greg KH [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=20161116161446.GA22095@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.