]> git-server-git.apps.pok.os.sepia.ceph.com Git - ceph-client.git/commit
Documentation: clarify the mandatory and desirable info for security reports
authorWilly Tarreau <w@1wt.eu>
Fri, 3 Apr 2026 06:20:18 +0000 (08:20 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 3 Apr 2026 11:11:23 +0000 (13:11 +0200)
commit496fa1befba1e8ff149af5120cd9c9616bb05120
treec97a19f6bce9d09d7212b0d9e3edf706375a4b96
parenta72b832a482372001a158c8014d116b053089b5d
Documentation: clarify the mandatory and desirable info for security reports

A significant part of the effort of the security team consists in begging
reporters for patch proposals, or asking them to provide them in regular
format, and most of the time they're willing to provide this, they just
didn't know that it would help. So let's add a section detailing the
required and desirable contents in a security report to help reporters
write more actionable reports which do not require round trips.

Cc: Eric Dumazet <edumazet@google.com>
Cc: Greg KH <greg@kroah.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
Link: https://patch.msgid.link/20260403062018.31080-4-w@1wt.eu
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Documentation/process/security-bugs.rst