From: Greg KH <gregkh@linuxfoundation.org>
To: David Windsor <dwindsor@gmail.com>
Cc: kernel-hardening@lists.openwall.com, "Reshetova,
Elena" <elena.reshetova@intel.com>,
Kees Cook <keescook@chromium.org>,
Hans Liljestrand <ishkamiel@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: [kernel-hardening] Re: HARDENED_ATOMIC documentation
Date: Mon, 6 Feb 2017 16:13:41 +0100 [thread overview]
Message-ID: <20170206151341.GA13383@kroah.com> (raw)
In-Reply-To: <CAEXv5_ivEPDJSaJwmx+oLiUYRZsAa9ZPWH6oWZy-Rkoa3ZHRZg@mail.gmail.com>
On Mon, Feb 06, 2017 at 09:55:41AM -0500, David Windsor wrote:
> Hi,
>
> I've put together some preliminary documentation for HARDENED_ATOMIC. This
> will be in addition to the in-tree documentation earlier submitted for review.
> This documentation contains only an API definition and examples. Justification
> and background info for HARDENED_ATOMIC are included in the in-tree
> documentation, so I didn't recreate this info in the kernsec.org
> documentation. Thoughts about this?
>
> You can find this documentation at http://kernsec.org/wiki/index.php/
> Kernel_Protections/HARDENED_ATOMIC.
>
> Please take a look and let me know your comments.
Please just send it as a patch so that we can comment on it, as well as
don't send html email because the mailing lists reject it!
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-06 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 14:55 [kernel-hardening] HARDENED_ATOMIC documentation David Windsor
2017-02-06 15:13 ` Greg KH [this message]
2017-02-06 15:19 ` [kernel-hardening] " David Windsor
2017-02-06 15:30 ` Greg KH
2017-02-06 16:02 ` David Windsor
2017-02-06 16:09 ` Mark Rutland
2017-02-06 20:08 ` Kees Cook
2017-02-06 20:36 ` David Windsor
2017-02-06 20:51 ` Jonathan Corbet
2017-02-06 21:05 ` David Windsor
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=20170206151341.GA13383@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dwindsor@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=ishkamiel@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=peterz@infradead.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 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.