From: Kees Cook <keescook@chromium.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stefano Zacchiroli <zack@upsilon.cc>,
Steven Rostedt <rostedt@goodmis.org>,
Laura Abbott <labbott@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>,
Wenwen Wang <wenwen@cs.uga.edu>,
Thorsten Leemhuis <linux@leemhuis.info>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] Documentation/process: Add Researcher Guidelines
Date: Fri, 25 Feb 2022 11:14:44 -0800 [thread overview]
Message-ID: <202202251114.058F4EB3@keescook> (raw)
In-Reply-To: <20220224010030.GA1282918@embeddedor>
On Wed, Feb 23, 2022 at 07:00:30PM -0600, Gustavo A. R. Silva wrote:
> On Wed, Feb 23, 2022 at 04:14:03PM -0800, Kees Cook wrote:
> > As a follow-up to the UMN incident[1], the TAB took the responsibility
> > to document Researcher Guidelines so there would be a common place to
> > point for describing our expectations as a developer community.
> >
> > Document best practices researchers should follow to participate
> > successfully with the Linux developer community.
> >
> > [1] https://lore.kernel.org/lkml/202105051005.49BFABCE@keescook/
> >
> > Co-developed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Co-developed-by: Jonathan Corbet <corbet@lwn.net>
> > Signed-off-by: Jonathan Corbet <corbet@lwn.net>
> > Co-developed-by: Stefano Zacchiroli <zack@upsilon.cc>
> > Signed-off-by: Stefano Zacchiroli <zack@upsilon.cc>
> > Co-developed-by: Steven Rostedt <rostedt@goodmis.org>
> > Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> > Acked-by: Steve Rostedt <rostedt@goodmis.org>
> > Acked-by: Laura Abbott <labbott@kernel.org>
> > Reviewed-by: Julia Lawall <julia.lawall@inria.fr>
> > Reviewed-by: Wenwen Wang <wenwen@cs.uga.edu>
> > Signed-off-by: Kees Cook <keescook@chromium.org>
>
> Acked-by: Gustavo A. R. Silva <gustavoars@kernel.org>
>
> See a comment below...
>
> > ---
> > Documentation/admin-guide/index.rst | 1 +
> > .../admin-guide/researcher-guidelines.rst | 141 ++++++++++++++++++
> > 2 files changed, 142 insertions(+)
> > create mode 100644 Documentation/admin-guide/researcher-guidelines.rst
>
> [..]
>
> > +* What is the specific problem that has been found?
> > +* How could the problem be reached on a running system?
> > +* What effect would encountering the problem have on the system?
> > +* How was the problem found? Specifically include details about any
> > + testing, static or dynamic analysis programs, and any other tools or
> > + methods used to perform the work.
> > +* Which version of Linux was the problem was found on? Using the most
>
> I think there is an extra "was" in the question above.
Oops! Thanks; I'll fix it. :)
--
Kees Cook
next prev parent reply other threads:[~2022-02-25 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 0:14 [PATCH] Documentation/process: Add Researcher Guidelines Kees Cook
2022-02-24 1:00 ` Gustavo A. R. Silva
2022-02-25 19:14 ` Kees Cook [this message]
2022-02-24 8:19 ` Thorsten Leemhuis
2022-02-24 9:56 ` Alexander Dahl
2022-02-24 10:10 ` Thorsten Leemhuis
2022-02-25 18:55 ` Kees Cook
2022-03-04 17:16 ` Jonathan Corbet
2022-03-04 17:20 ` Randy Dunlap
2022-03-04 18:15 ` Kees Cook
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=202202251114.058F4EB3@keescook \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=julia.lawall@inria.fr \
--cc=labbott@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=rostedt@goodmis.org \
--cc=wenwen@cs.uga.edu \
--cc=zack@upsilon.cc \
/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;
as well as URLs for NNTP newsgroup(s).