From: Mark Rutland <mark.rutland@arm.com>
To: David Windsor <dwindsor@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
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: Re: [kernel-hardening] Re: HARDENED_ATOMIC documentation
Date: Mon, 6 Feb 2017 16:09:45 +0000 [thread overview]
Message-ID: <20170206160945.GB4190@leverpostej> (raw)
In-Reply-To: <CAEXv5_iD0k-mxqOgT9W_mf1_Xo46qePFXvTX2wd32xG0gPzSUw@mail.gmail.com>
On Mon, Feb 06, 2017 at 11:02:56AM -0500, David Windsor wrote:
> > Why not put the documentation right into the kernel tree? That way it
> > is always up to date with the code (well, hopefully), it will get built
> > and hosted all over the internet at different sites (including
> > kernel.org) and is much easier to search and people can modify easier.
> >
>
> Fair enough, I'll re-submit as a patch against something in
> Documentation/. It doesn't appear that there's currently a good
> landing spot for this, as Documentation/security/self-protection.txt
> already looks fairly crowded. Individual KSPP sub-project details
> would impossibly complicate this file. Maybe a kspp/ or
> self-protection/ sub-directory with files for individual KSPP
> features?
It would be better to mirror our documentation of atomics; i.e. place
this in Documentation/core-api/refcount_ops.rst.
Developers don't care if this is part of KSPP, they care about the API.
Thanks,
Mark.
next prev parent reply other threads:[~2017-02-06 16:09 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 ` [kernel-hardening] " Greg KH
2017-02-06 15:19 ` David Windsor
2017-02-06 15:30 ` Greg KH
2017-02-06 16:02 ` David Windsor
2017-02-06 16:09 ` Mark Rutland [this message]
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=20170206160945.GB4190@leverpostej \
--to=mark.rutland@arm.com \
--cc=dwindsor@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=gregkh@linuxfoundation.org \
--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.