From: "tip-bot2 for Alexander A. Klimov" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [tip: locking/core] docs: locking: Replace HTTP links with HTTPS ones
Date: Fri, 17 Jul 2020 11:22:05 -0000 [thread overview]
Message-ID: <159498492557.4006.1686830928434874554.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200713115728.33905-1-grandmaster@al2klimov.de>
The following commit has been merged into the locking/core branch of tip:
Commit-ID: 482cbb6cc33dca60091048631cd0a8dde72c3da7
Gitweb: https://git.kernel.org/tip/482cbb6cc33dca60091048631cd0a8dde72c3da7
Author: Alexander A. Klimov <grandmaster@al2klimov.de>
AuthorDate: Mon, 13 Jul 2020 13:57:28 +02:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Thu, 16 Jul 2020 23:19:51 +02:00
docs: locking: Replace HTTP links with HTTPS ones
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
If neither `\bgnu\.org/license`, nor `\bmozilla\.org/MPL\b`:
If both the HTTP and HTTPS versions
return 200 OK and serve the same content:
Replace HTTP with HTTPS.
Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20200713115728.33905-1-grandmaster@al2klimov.de
---
Documentation/locking/mutex-design.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/locking/mutex-design.rst b/Documentation/locking/mutex-design.rst
index 4d8236b..8f3e9a5 100644
--- a/Documentation/locking/mutex-design.rst
+++ b/Documentation/locking/mutex-design.rst
@@ -18,7 +18,7 @@ as an alternative to these. This new data structure provided a number
of advantages, including simpler interfaces, and at that time smaller
code (see Disadvantages).
-[1] http://lwn.net/Articles/164802/
+[1] https://lwn.net/Articles/164802/
Implementation
--------------
prev parent reply other threads:[~2020-07-17 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 11:57 [PATCH] " Alexander A. Klimov
2020-07-13 15:35 ` Jonathan Corbet
2020-07-17 11:22 ` tip-bot2 for Alexander A. Klimov [this message]
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=159498492557.4006.1686830928434874554.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=grandmaster@al2klimov.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®