From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Willy Tarreau <w@1wt.eu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [GIT PULL] Updating the security-bugs document
Date: Fri, 15 May 2026 07:35:38 -0600 [thread overview]
Message-ID: <87lddksslx.fsf@trenco.lwn.net> (raw)
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/docs/linux.git tags/docs-7.1-fixes
for you to fetch changes up to f2e65e4e5b4b4b9ecf43f03c3fdbe8c9a8a43a9e:
docs: threat-model: don't limit root capabilities to CAP_SYS_ADMIN (2026-05-14 06:23:44 -0600)
----------------------------------------------------------------
This is Willy Tarreau's new document clarifying the definition and handling
of security-related bugs, which we're trying to get out there quickly on
the theory that some of the bug reporters might actually read and pay
attention to it.
----------------------------------------------------------------
Jonathan Corbet (2):
docs: security-bugs: add a link to the threat-model documentation
docs: threat-model: don't limit root capabilities to CAP_SYS_ADMIN
Willy Tarreau (3):
Documentation: security-bugs: do not systematically Cc the security team
Documentation: security-bugs: explain what is and is not a security bug
Documentation: security-bugs: clarify requirements for AI-assisted reports
Documentation/process/index.rst | 1 +
Documentation/process/security-bugs.rst | 106 +++++++++++++-
Documentation/process/threat-model.rst | 235 ++++++++++++++++++++++++++++++++
3 files changed, 340 insertions(+), 2 deletions(-)
create mode 100644 Documentation/process/threat-model.rst
reply other threads:[~2026-05-15 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87lddksslx.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linuxfoundation.org \
--cc=w@1wt.eu \
/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