Skip to content

Commit

Permalink
docs: process: Add cross-link to security-bugs
Browse files Browse the repository at this point in the history
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.

Signed-off-by: Krzysztof Kozlowski <[email protected]>
Reviewed-by: Greg Kroah-Hartman <[email protected]>
Reviewed-by: Felipe Balbi <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Kees Cook <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jonathan Corbet <[email protected]>
  • Loading branch information
krzk authored and Jonathan Corbet committed Aug 31, 2020
1 parent 4680af6 commit eb45fb2
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion Documentation/process/submitting-patches.rst
Original file line number Diff line number Diff line change
Expand Up @@ -299,7 +299,8 @@ sending him e-mail.
If you have a patch that fixes an exploitable security bug, send that patch
to [email protected]. 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::
Expand Down

0 comments on commit eb45fb2

Please sign in to comment.