Hi, On Thu, Aug 27, 2020 at 1:54 PM Krzysztof Kozlowski <k...@kernel.org> wrote: > > The submitting patches mentions criteria for a fix to be called > "security fix". Add a link to document explaining the entire process > of handling security bugs. > > Cc: Greg KH <gre...@linuxfoundation.org> > Cc: Marek Szyprowski <m.szyprow...@samsung.com> > Cc: Linus Torvalds <torva...@linux-foundation.org> > Cc: Kees Cook <keesc...@chromium.org> > Signed-off-by: Krzysztof Kozlowski <k...@kernel.org> > --- > Documentation/process/submitting-patches.rst | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/Documentation/process/submitting-patches.rst > b/Documentation/process/submitting-patches.rst > index 5219bf3cddfc..d5b3c5a74d5d 100644 > --- a/Documentation/process/submitting-patches.rst > +++ b/Documentation/process/submitting-patches.rst > @@ -299,7 +299,8 @@ sending him e-mail. > If you have a patch that fixes an exploitable security bug, send that patch > to secur...@kernel.org. For severe bugs, a short embargo may be considered > to allow distributors to get the patch out to users; in such cases, > -obviously, the patch should not be sent to any public lists. > +obviously, the patch should not be sent to any public lists. See also > +:ref:`Documentation/admin-guide/security-bugs.rst <security-bugs>`. > > Patches that fix a severe bug in a released kernel should be directed > toward the stable maintainers by putting a line like this:: > -- > 2.17.1
Reviewed-by: Felipe Balbi <ba...@kernel.org> -- balbi
