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@xxxxxxxxxxxxxxxxxxx> > Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > Co-developed-by: Jonathan Corbet <corbet@xxxxxxx> > Signed-off-by: Jonathan Corbet <corbet@xxxxxxx> > Co-developed-by: Stefano Zacchiroli <zack@xxxxxxxxxx> > Signed-off-by: Stefano Zacchiroli <zack@xxxxxxxxxx> > Co-developed-by: Steven Rostedt <rostedt@xxxxxxxxxxx> > Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx> > Acked-by: Steve Rostedt <rostedt@xxxxxxxxxxx> > Acked-by: Laura Abbott <labbott@xxxxxxxxxx> > Reviewed-by: Julia Lawall <julia.lawall@xxxxxxxx> > Reviewed-by: Wenwen Wang <wenwen@xxxxxxxxxx> > Signed-off-by: Kees Cook <keescook@xxxxxxxxxxxx> Acked-by: Gustavo A. R. Silva <gustavoars@xxxxxxxxxx> 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. Thanks -- Gustavo
