Replace HTTP links with HTTPS ones: documentation
Subsystems (4)
PATCH 1/1 Replace HTTP links with HTTPS ones: documentation
Rationale: Reduces attack surface on kernel devs for MITM.
Deterministic algorithm:
For each file:
For each line:
If doesn't contain \bxmlns\b:
For each link, \bhttp://[^# \t\r\n]*(?:\w|/):
If both the HTTP and HTTPS versions return 200 OK and serve the same content:
Replace HTTP with HTTPS.
--- Documentation/COPYING-logo | 2 +- Documentation/admin-guide/LSM/tomoyo.rst | 16 ++++++++-------- .../admin-guide/acpi/initrd_table_override.rst | 2 +- Documentation/admin-guide/bcache.rst | 4 ++-- Documentation/admin-guide/devices.rst | 2 +- Documentation/admin-guide/initrd.rst | 2 +- Documentation/admin-guide/md.rst | 2 +- Documentation/admin-guide/mono.rst | 4 ++-- Documentation/admin-guide/reporting-bugs.rst | 2 +- Documentation/admin-guide/unicode.rst | 4 ++-- Documentation/conf.py | 2 +- Documentation/dev-tools/gdb-kernel-debugging.rst | 2 +- Documentation/doc-guide/parse-headers.rst | 2 +- .../driver-api/acpi/linuxized-acpica.rst | 6 +++--- Documentation/driver-api/usb/bulk-streams.rst | 4 ++-- .../driver-api/usb/writing_musb_glue_layer.rst | 6 +++--- Documentation/filesystems/path-lookup.txt | 2 +- Documentation/filesystems/seq_file.txt | 4 ++-- Documentation/misc-devices/c2port.txt | 6 +++--- Documentation/process/3.Early-stage.rst | 2 +- Documentation/process/7.AdvancedTopics.rst | 8 ++++---- Documentation/process/8.Conclusion.rst | 14 +++++++------- Documentation/process/adding-syscalls.rst | 4 ++-- Documentation/process/applying-patches.rst | 4 ++-- .../process/volatile-considered-harmful.rst | 4 ++-- Documentation/rbtree.txt | 4 ++-- Documentation/security/SCTP.rst | 2 +- Documentation/sphinx/kfigure.py | 6 +++--- Documentation/static-keys.txt | 2 +- Documentation/trace/events-msr.rst | 2 +- Documentation/trace/mmiotrace.rst | 2 +- Documentation/vm/ksm.rst | 2 +- Documentation/xz.txt | 6 +++--- scripts/kernel-doc | 2 +- 34 files changed, 69 insertions(+), 69 deletions(-)
Documentation/COPYING-logo +1 -1
@@ -9,5 +9,5 @@ scale down to smaller sizes and are better for letterheads or whatever you want to use it for: for the full range of logos take a look at Larry's web-page: - http://www.isc.tamu.edu/~lewing/linux/ + https://www.isc.tamu.edu/~lewing/linux/
Documentation/admin-guide/LSM/tomoyo.rst +8 -8
@@ -27,29 +27,29 @@ Where is documentation? ======================= User <-> Kernel interface documentation is available at -http://tomoyo.osdn.jp/2.5/policy-specification/index.html . +https://tomoyo.osdn.jp/2.5/policy-specification/index.html . Materials we prepared for seminars and symposiums are available at -http://osdn.jp/projects/tomoyo/docs/?category_id=532&language_id=1 . +https://osdn.jp/projects/tomoyo/docs/?category_id=532&language_id=1 . Below lists are chosen from three aspects. What is TOMOYO? TOMOYO Linux Overview - http://osdn.jp/projects/tomoyo/docs/lca2009-takeda.pdf + https://osdn.jp/projects/tomoyo/docs/lca2009-takeda.pdf TOMOYO Linux: pragmatic and manageable security for Linux - http://osdn.jp/projects/tomoyo/docs/freedomhectaipei-tomoyo.pdf + https://osdn.jp/projects/tomoyo/docs/freedomhectaipei-tomoyo.pdf TOMOYO Linux: A Practical Method to Understand and Protect Your Own Linux Box - http://osdn.jp/projects/tomoyo/docs/PacSec2007-en-no-demo.pdf + https://osdn.jp/projects/tomoyo/docs/PacSec2007-en-no-demo.pdf What can TOMOYO do? Deep inside TOMOYO Linux - http://osdn.jp/projects/tomoyo/docs/lca2009-kumaneko.pdf + https://osdn.jp/projects/tomoyo/docs/lca2009-kumaneko.pdf The role of "pathname based access control" in security. - http://osdn.jp/projects/tomoyo/docs/lfj2008-bof.pdf + https://osdn.jp/projects/tomoyo/docs/lfj2008-bof.pdf History of TOMOYO? Realities of Mainlining - http://osdn.jp/projects/tomoyo/docs/lfj2008.pdf + https://osdn.jp/projects/tomoyo/docs/lfj2008.pdf What is future plan? ====================
Documentation/admin-guide/acpi/initrd_table_override.rst +1 -1
@@ -102,7 +102,7 @@ Where to retrieve userspace tools ================================= iasl and acpixtract are part of Intel's ACPICA project: -http://acpica.org/ +https://acpica.org/ and should be packaged by distributions (for example in the acpica package on SUSE).
Documentation/admin-guide/bcache.rst +2 -2
@@ -7,9 +7,9 @@ nice if you could use them as cache... Hence bcache. Wiki and git repositories are at: - - http://bcache.evilpiepirate.org + - https://bcache.evilpiepirate.org - http://evilpiepirate.org/git/linux-bcache.git - - http://evilpiepirate.org/git/bcache-tools.git + - https://evilpiepirate.org/git/bcache-tools.git It's designed around the performance characteristics of SSDs - it only allocates in erase block sized buckets, and it uses a hybrid btree/log to track cached
Documentation/admin-guide/devices.rst +1 -1
@@ -17,7 +17,7 @@ Specifically explore the sections titled "CHAR and MISC DRIVERS", and to involve for character and block devices. This document is included by reference into the Filesystem Hierarchy -Standard (FHS). The FHS is available from http://www.pathname.com/fhs/. +Standard (FHS). The FHS is available from https://www.pathname.com/fhs/. Allocations marked (68k/Amiga) apply to Linux/68k on the Amiga platform only. Allocations marked (68k/Atari) apply to Linux/68k on
Documentation/admin-guide/initrd.rst +1 -1
@@ -376,7 +376,7 @@ Resources --------- .. [#f1] Almesberger, Werner; "Booting Linux: The History and the Future" - http://www.almesberger.net/cv/papers/ols2k-9.ps.gz + https://www.almesberger.net/cv/papers/ols2k-9.ps.gz .. [#f2] newlib package (experimental), with initrd example https://www.sourceware.org/newlib/ .. [#f3] util-linux: Miscellaneous utilities for Linux
Documentation/admin-guide/md.rst +1 -1
@@ -5,7 +5,7 @@ Boot time assembly of RAID arrays --------------------------------- Tools that manage md devices can be found at - http://www.kernel.org/pub/linux/utils/raid/ + https://www.kernel.org/pub/linux/utils/raid/ You can boot with your md device with the following kernel command
Documentation/admin-guide/mono.rst +2 -2
@@ -12,11 +12,11 @@ other program after you have done the following: a binary package, a source tarball or by installing from Git. Binary packages for several distributions can be found at: - http://www.mono-project.com/download/ + https://www.mono-project.com/download/ Instructions for compiling Mono can be found at: - http://www.mono-project.com/docs/compiling-mono/linux/ + https://www.mono-project.com/docs/compiling-mono/linux/ Once the Mono CLR support has been installed, just check that ``/usr/bin/mono`` (which could be located elsewhere, for example
Documentation/admin-guide/reporting-bugs.rst +1 -1
@@ -75,7 +75,7 @@ Tips for reporting bugs If you haven't reported a bug before, please read: - http://www.chiark.greenend.org.uk/~sgtatham/bugs.html + https://www.chiark.greenend.org.uk/~sgtatham/bugs.html http://www.catb.org/esr/faqs/smart-questions.html
Documentation/admin-guide/unicode.rst +2 -2
@@ -114,7 +114,7 @@ Unicode practice. This range is now officially managed by the ConScript Unicode Registry. The normative reference is at: - http://www.evertype.com/standards/csur/klingon.html + https://www.evertype.com/standards/csur/klingon.html Klingon has an alphabet of 26 characters, a positional numeric writing system with 10 digits, and is written left-to-right, top-to-bottom.
@@ -178,7 +178,7 @@ fictional and artificial scripts has been established by John Cowan <[email protected]> and Michael Everson <[email protected]>. The ConScript Unicode Registry is accessible at: - http://www.evertype.com/standards/csur/ + https://www.evertype.com/standards/csur/ The ranges used fall at the low end of the End User Zone and can hence not be normatively assigned, but it is recommended that people who
Documentation/conf.py +1 -1
@@ -576,7 +576,7 @@ epub_exclude_files = ['search.html'] # Grouping the document tree into PDF files. List of tuples # (source start file, target name, title, author, options). # -# See the Sphinx chapter of http://ralsina.me/static/manual.pdf +# See the Sphinx chapter of https://ralsina.me/static/manual.pdf # # FIXME: Do not add the index file here; the result will be too big. Adding # multiple PDF files here actually tries to get the cross-referencing right
Documentation/dev-tools/gdb-kernel-debugging.rst +1 -1
@@ -24,7 +24,7 @@ Setup - Create a virtual Linux machine for QEMU/KVM (see www.linux-kvm.org and www.qemu.org for more details). For cross-development, - http://landley.net/aboriginal/bin keeps a pool of machine images and + https://landley.net/aboriginal/bin keeps a pool of machine images and toolchains that can be helpful to start from. - Build the kernel with CONFIG_GDB_SCRIPTS enabled, but leave
Documentation/doc-guide/parse-headers.rst +1 -1
@@ -186,7 +186,7 @@ COPYRIGHT Copyright (c) 2016 by Mauro Carvalho Chehab <[email protected]>. -License GPLv2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>. +License GPLv2: GNU GPL version 2 <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
Documentation/driver-api/acpi/linuxized-acpica.rst +3 -3
@@ -175,9 +175,9 @@ illustrated in the following figure:: B. acpica / master - "master" branch of the git repository at <https://github.com/acpica/acpica.git>. C. linux-pm / linux-next - "linux-next" branch of the git repository at - <http://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git>. + <https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git>. D. linux / master - "master" branch of the git repository at - <http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git>. + <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git>. Before the linuxized ACPICA patches are sent to the Linux ACPI community for review, there is a quality assurance build test process to reduce
@@ -274,6 +274,6 @@ before they become available from the ACPICA release process. a diff file indicating the state of the current divergences:: # git clone https://github.com/acpica/acpica - # git clone http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git + # git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git # cd acpica # generate/linux/divergences.sh -s ../linux
Documentation/driver-api/usb/bulk-streams.rst +2 -2
@@ -9,9 +9,9 @@ device driver to overload a bulk endpoint so that multiple transfers can be queued at once. Streams are defined in sections 4.4.6.4 and 8.12.1.4 of the Universal Serial Bus -3.0 specification at http://www.usb.org/developers/docs/ The USB Attached SCSI +3.0 specification at https://www.usb.org/developers/docs/ The USB Attached SCSI Protocol, which uses streams to queue multiple SCSI commands, can be found on -the T10 website (http://t10.org/). +the T10 website (https://t10.org/). Device-side implications
Documentation/driver-api/usb/writing_musb_glue_layer.rst +3 -3
@@ -707,12 +707,12 @@ cheerful guidance and support. Resources ========= -USB Home Page: http://www.usb.org +USB Home Page: https://www.usb.org -linux-usb Mailing List Archives: http://marc.info/?l=linux-usb +linux-usb Mailing List Archives: https://marc.info/?l=linux-usb USB On-the-Go Basics: -http://www.maximintegrated.com/app-notes/index.mvp/id/1822 +https://www.maximintegrated.com/app-notes/index.mvp/id/1822 :ref:`Writing USB Device Drivers <writing-usb-driver>`
Documentation/filesystems/path-lookup.txt +1 -1
@@ -375,7 +375,7 @@ common path elements, the more likely they will exist in dentry cache. Papers and other documentation on dcache locking ================================================ -1. Scaling dcache with RCU (http://linuxjournal.com/article.php?sid=7124). +1. Scaling dcache with RCU (https://linuxjournal.com/article.php?sid=7124). 2. http://lse.sourceforge.net/locking/dcache/dcache.html
Documentation/filesystems/seq_file.txt +2 -2
@@ -2,7 +2,7 @@ The seq_file interface Copyright 2003 Jonathan Corbet <[email protected]> This file is originally from the LWN.net Driver Porting series at - http://lwn.net/Articles/driver-porting/ + https://lwn.net/Articles/driver-porting/ There are numerous ways for a device driver (or other kernel component) to
@@ -52,7 +52,7 @@ Then concatenate the output files out1 and out2 and get the right result. Yes, it is a thoroughly useless module, but the point is to show how the mechanism works without getting lost in other details. (Those wanting to see the full source for this module can find it at -http://lwn.net/Articles/22359/). +https://lwn.net/Articles/22359/). Deprecated create_proc_entry
Documentation/misc-devices/c2port.txt +3 -3
@@ -28,14 +28,14 @@ where the micro controller is connected via special GPIOs pins. References ---------- -The C2 Interface main references are at (http://www.silabs.com) +The C2 Interface main references are at (https://www.silabs.com) Silicon Laboratories site], see: - AN127: FLASH Programming via the C2 Interface at -http://www.silabs.com/Support Documents/TechnicalDocs/an127.pdf +https://www.silabs.com/Support Documents/TechnicalDocs/an127.pdf - C2 Specification at -http://www.silabs.com/pages/DownloadDoc.aspx?FILEURL=Support%20Documents/TechnicalDocs/an127.pdf&src=SearchResults +https://www.silabs.com/pages/DownloadDoc.aspx?FILEURL=Support%20Documents/TechnicalDocs/an127.pdf&src=SearchResults however it implements a two wire serial communication protocol (bit banging) designed to enable in-system programming, debugging, and
Documentation/process/3.Early-stage.rst +1 -1
@@ -46,7 +46,7 @@ and posted this: to communicate user requirements to these people is a waste of time. They are much too "intelligent" to listen to lesser mortals. -(http://lwn.net/Articles/131776/). +(https://lwn.net/Articles/131776/). The reality of the situation was different; the kernel developers were far more concerned about system stability, long-term maintenance, and finding
Documentation/process/7.AdvancedTopics.rst +4 -4
@@ -29,9 +29,9 @@ long document in its own right. Instead, the focus here will be on how git fits into the kernel development process in particular. Developers who wish to come up to speed with git will find more information at: - http://git-scm.com/ + https://git-scm.com/ - http://www.kernel.org/pub/software/scm/git/docs/user-manual.html + https://www.kernel.org/pub/software/scm/git/docs/user-manual.html and on various tutorials found on the web.
@@ -55,7 +55,7 @@ server with git-daemon is relatively straightforward if you have a system which is accessible to the Internet. Otherwise, free, public hosting sites (Github, for example) are starting to appear on the net. Established developers can get an account on kernel.org, but those are not easy to come -by; see http://kernel.org/faq/ for more information. +by; see https://kernel.org/faq/ for more information. The normal git workflow involves the use of a lot of branches. Each line of development can be separated into a separate "topic branch" and
@@ -125,7 +125,7 @@ can affect your ability to get trees pulled in the future. Quoting Linus: to trust things *without* then having to go and check every individual change by hand. -(http://lwn.net/Articles/224135/). +(https://lwn.net/Articles/224135/). To avoid this kind of situation, ensure that all patches within a given branch stick closely to the associated topic; a "driver fixes" branch
Documentation/process/8.Conclusion.rst +7 -7
@@ -16,24 +16,24 @@ distributions runs into internal limits and fails to process the documents properly). Various web sites discuss kernel development at all levels of detail. Your -author would like to humbly suggest http://lwn.net/ as a source; +author would like to humbly suggest https://lwn.net/ as a source; information on many specific kernel topics can be found via the LWN kernel index at: - http://lwn.net/Kernel/Index/ + https://lwn.net/Kernel/Index/ Beyond that, a valuable resource for kernel developers is: - http://kernelnewbies.org/ + https://kernelnewbies.org/ -And, of course, one should not forget http://kernel.org/, the definitive +And, of course, one should not forget https://kernel.org/, the definitive location for kernel release information. There are a number of books on kernel development: Linux Device Drivers, 3rd Edition (Jonathan Corbet, Alessandro Rubini, and Greg Kroah-Hartman). Online at - http://lwn.net/Kernel/LDD3/. + https://lwn.net/Kernel/LDD3/. Linux Kernel Development (Robert Love).
@@ -46,9 +46,9 @@ information to be found there. Documentation for git can be found at: - http://www.kernel.org/pub/software/scm/git/docs/ + https://www.kernel.org/pub/software/scm/git/docs/ - http://www.kernel.org/pub/software/scm/git/docs/user-manual.html + https://www.kernel.org/pub/software/scm/git/docs/user-manual.html Conclusion
Documentation/process/adding-syscalls.rst +2 -2
@@ -541,9 +541,9 @@ References and Sources :manpage:`syscall(2)` man-page: http://man7.org/linux/man-pages/man2/syscall.2.html#NOTES - Collated emails from Linus Torvalds discussing the problems with ``ioctl()``: - http://yarchive.net/comp/linux/ioctl.html + https://yarchive.net/comp/linux/ioctl.html - "How to not invent kernel interfaces", Arnd Bergmann, - http://www.ukuug.org/events/linux2007/2007/papers/Bergmann.pdf + https://www.ukuug.org/events/linux2007/2007/papers/Bergmann.pdf - LWN article from Michael Kerrisk on avoiding new uses of CAP_SYS_ADMIN: https://lwn.net/Articles/486306/ - Recommendation from Andrew Morton that all related information for a new
Documentation/process/applying-patches.rst +2 -2
@@ -229,7 +229,7 @@ Although interdiff may save you a step or two you are generally advised to do the additional steps since interdiff can get things wrong in some cases. Another alternative is ``ketchup``, which is a python script for automatic -downloading and applying of patches (http://www.selenic.com/ketchup/). +downloading and applying of patches (https://www.selenic.com/ketchup/). Other nice tools are diffstat, which shows a summary of changes made by a patch; lsdiff, which displays a short listing of affected files in a patch
@@ -241,7 +241,7 @@ the patch contains a given regular expression. Where can I download the patches? ================================= -The patches are available at http://kernel.org/ +The patches are available at https://kernel.org/ Most recent patches are linked from the front page, but they also have specific homes.
Documentation/process/volatile-considered-harmful.rst +2 -2
@@ -109,9 +109,9 @@ been properly thought through. References ========== -[1] http://lwn.net/Articles/233481/ +[1] https://lwn.net/Articles/233481/ -[2] http://lwn.net/Articles/233482/ +[2] https://lwn.net/Articles/233482/ Credits =======
Documentation/rbtree.txt +2 -2
@@ -36,10 +36,10 @@ This document covers use of the Linux rbtree implementation. For more information on the nature and implementation of Red Black Trees, see: Linux Weekly News article on red-black trees - http://lwn.net/Articles/184495/ + https://lwn.net/Articles/184495/ Wikipedia entry on red-black trees - http://en.wikipedia.org/wiki/Red-black_tree + https://en.wikipedia.org/wiki/Red-black_tree Linux implementation of red-black trees ---------------------------------------
Documentation/security/SCTP.rst +1 -1
@@ -328,7 +328,7 @@ NOTES: label (see **netlabel-config**\(8) helper script for details). 5) The NetLabel SCTP peer labeling rules apply as discussed in the following - set of posts tagged "netlabel" at: http://www.paul-moore.com/blog/t. + set of posts tagged "netlabel" at: https://www.paul-moore.com/blog/t. 6) CIPSO is only supported for IPv4 addressing: ``socket(AF_INET, ...)`` CALIPSO is only supported for IPv6 addressing: ``socket(AF_INET6, ...)``
Documentation/sphinx/kfigure.py +3 -3
@@ -29,7 +29,7 @@ u""" Used tools: - * ``dot(1)``: Graphviz (http://www.graphviz.org). If Graphviz is not + * ``dot(1)``: Graphviz (https://www.graphviz.org). If Graphviz is not available, the DOT language is inserted as literal-block. * SVG to PDF: To generate PDF, you need at least one of this tools:
@@ -41,7 +41,7 @@ u""" * generate PDF from SVG / used by PDF (LaTeX) builder * generate SVG (html-builder) and PDF (latex-builder) from DOT files. - DOT: see http://www.graphviz.org/content/dot-language + DOT: see https://www.graphviz.org/content/dot-language """
@@ -182,7 +182,7 @@ def setupTools(app): kernellog.verbose(app, "use dot(1) from: " + dot_cmd) else: kernellog.warn(app, "dot(1) not found, for better output quality install " - "graphviz from http://www.graphviz.org") + "graphviz from https://www.graphviz.org") if convert_cmd: kernellog.verbose(app, "use convert(1) from: " + convert_cmd) else:
Documentation/static-keys.txt +1 -1
@@ -71,7 +71,7 @@ Solution gcc (v4.5) adds a new 'asm goto' statement that allows branching to a label: -http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01556.html +https://gcc.gnu.org/ml/gcc-patches/2009-07/msg01556.html Using the 'asm goto', we can create branches that are either taken or not taken by default, without the need to check memory. Then, at run-time, we can patch
Documentation/trace/events-msr.rst +1 -1
@@ -4,7 +4,7 @@ MSR Trace Events The x86 kernel supports tracing most MSR (Model Specific Register) accesses. To see the definition of the MSRs on Intel systems please see the SDM -at http://www.intel.com/sdm (Volume 3) +at https://www.intel.com/sdm (Volume 3) Available trace points:
Documentation/trace/mmiotrace.rst +1 -1
@@ -5,7 +5,7 @@ In-kernel memory-mapped I/O tracing Home page and links to optional user space tools: - http://nouveau.freedesktop.org/wiki/MmioTrace + https://nouveau.freedesktop.org/wiki/MmioTrace MMIO tracing was originally developed by Intel around 2003 for their Fault Injection Test Harness. In Dec 2006 - Jan 2007, using the code from Intel,
Documentation/vm/ksm.rst +1 -1
@@ -6,7 +6,7 @@ Kernel Samepage Merging KSM is a memory-saving de-duplication feature, enabled by CONFIG_KSM=y, added to the Linux kernel in 2.6.32. See ``mm/ksm.c`` for its implementation, -and http://lwn.net/Articles/306704/ and http://lwn.net/Articles/330589/ +and http://lwn.net/Articles/306704/ and https://lwn.net/Articles/330589/ The userspace interface of KSM is described in :ref:`Documentation/admin-guide/mm/ksm.rst <admin_guide_ksm>`
Documentation/xz.txt +3 -3
@@ -14,13 +14,13 @@ improve compression ratio of executable data. The XZ decompressor in Linux is called XZ Embedded. It supports the LZMA2 filter and optionally also BCJ filters. CRC32 is supported for integrity checking. The home page of XZ Embedded is at -<http://tukaani.org/xz/embedded.html>, where you can find the +<https://tukaani.org/xz/embedded.html>, where you can find the latest version and also information about using the code outside the Linux kernel. For userspace, XZ Utils provide a zlib-like compression library and a gzip-like command line tool. XZ Utils can be downloaded from -<http://tukaani.org/xz/>. +<https://tukaani.org/xz/>. XZ related components in the kernel ===================================
@@ -113,7 +113,7 @@ Reporting bugs ============== Before reporting a bug, please check that it's not fixed already -at upstream. See <http://tukaani.org/xz/embedded.html> to get the +at upstream. See <https://tukaani.org/xz/embedded.html> to get the latest code. Report bugs to <[email protected]> or visit #tukaani on
scripts/kernel-doc +1 -1
@@ -317,7 +317,7 @@ if (defined($ENV{'KBUILD_VERBOSE'})) { # Generated docbook code is inserted in a template at a point where # docbook v3.1 requires a non-zero sequence of RefEntry's; see: -# http://www.oasis-open.org/docbook/documentation/reference/html/refentry.html +# https://www.oasis-open.org/docbook/documentation/reference/html/refentry.html # We keep track of number of generated entries and generate a dummy # if needs be to ensure the expanded template can be postprocessed # into html.
Signature · 1 line
2.26.2
A message that is not in the archive (sent off-list or not yet received): CAHZk5We1y7o+s7LG=7Q4mVynj5CvJ7RdXLx6WFd-k0yyk=DyPw@mail.gmail.com
Am 22.05.20 um 09:50 schrieb Sanjeev Gupta:
Quoted 3 lines
Alexander,
Back in Mar 2018, I had sent in some patches to convert links from http to https. This stalled, as questions of what security threat I was addressing could not be articulated by me (apart from "https is
Now *I* tried to articulate the rationale. I'm waiting for Jon to eventually complain. Maybe I'll have to write a bit more, so what.
Quoted 1 line
better!"). I had eyeballed each link manually to ensure that the same content was (humanly) visible.
Each $%&/ing link of about 3033 (this patch + my Git working directory)? o.O
FYI, the "Deterministic algorithm" I mentioned is not just an algorithm, it's the algorithm I actually implemented as a software to avoid human mistakes and to save some time, especially for the case Jon futher restricts the criteria for links to be changed.
@Jon Really, if you have anything to complain about, just complain. I'll throw away my current patch, pull torvalds/master, adjust my algotithm and let it run for 1-2 days.
Quoted 2 lines
In some cases, the original link had disappeared, and I had replaced it with a link via archive.org <http://archive.org> ; the question Jonathan had was "if the link is dead, apart from historical preciseness, what is it doing in Documentation?" I did not have an answer for that, too.
1. If a link is actually dead, IMAO Jon was right that I shall not change it.
2. But IMAO he's wrong that the links shall not be included. E.g.:
Copyright (C) 2012 Texas Instruments Incorporated - https://www.ti.com/
Let's say that link is broken.
a) Is it actually broken? Or can't *just you* access it for whatever technical reason? Or is it actually broken for everyone, but just temporarily due to (let's say) a NS failure?
b) If it's actually broken, shall we really just drop it? IMAO you're absolutely right by falling back to archive.org not to loose information. After all the link was likely added one nice day for a reason.
c) If (let's say) archive.org didn't store it and it's actually dead, may we remove it? For the example I've given above I'd cleary say no as that link is part of a code author attribution.
@Jon Did a) and c) answer "what is it doing in Documentation?"? Also please consider b) and tell your opinion.
Quoted 2 lines
There were *some* patches accepted, but in general, I think it would be better to feed them in by directory/maintainer, and in some cases work with the original author of the Doc to see how it could be rewritten, etc, to address these concerns.
1. I'm already splitting by maintainer.
2. What exactly to annoy the original authors for? IMAO I've adressed the security concern well enough with my patch and you and me have adressed the broken link concern well enough with a), b) and c) (above).
Quoted 2 lines
If this seems viable, I would be happy to work with you to feed patches in small chunks for review. I have done this for some other projects, eg, ntp, NTPsec, and gpsd.
I have already done all changes I'd like to contribute in my Git working directory (so IMAO there isn't anymore to do in this construction area ex. waiting) and I'm just waiting for Jon to merge my first patch as a precedent for the next ones.
@Jon Btw.: Into which branch? Not that I'll be pulling one branch to check whether the stuff has been merged, but it's been merged into another one.
Quoted 809 lines
Signature · 3 lines
-- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghaneOn Thu, May 21, 2020 at 4:04 AM Alexander A. Klimov <[email protected] <mailto:[email protected]>> wrote:
Rationale: Reduces attack surface on kernel devs for MITM.
Deterministic algorithm:
For each file:
For each line:
If doesn't contain\bxmlns\b:
For each link,\bhttp://[^# \t\r\n]*(?:\w|/):
If both the HTTP and HTTPS versions
return 200 OK and serve the same content:
Replace HTTP with HTTPS.
---
Documentation/COPYING-logo | 2 +- Documentation/admin-guide/LSM/tomoyo.rst | 16 ++++++++-------- .../admin-guide/acpi/initrd_table_override.rst | 2 +- Documentation/admin-guide/bcache.rst | 4 ++-- Documentation/admin-guide/devices.rst | 2 +- Documentation/admin-guide/initrd.rst | 2 +- Documentation/admin-guide/md.rst | 2 +- Documentation/admin-guide/mono.rst | 4 ++-- Documentation/admin-guide/reporting-bugs.rst | 2 +- Documentation/admin-guide/unicode.rst | 4 ++-- Documentation/conf.py | 2 +-Documentation/dev-tools/gdb-kernel-debugging.rst| 2 +- Documentation/doc-guide/parse-headers.rst | 2 +- .../driver-api/acpi/linuxized-acpica.rst | 6 +++--- Documentation/driver-api/usb/bulk-streams.rst | 4 ++-- .../driver-api/usb/writing_musb_glue_layer.rst | 6 +++--- Documentation/filesystems/path-lookup.txt | 2 +- Documentation/filesystems/seq_file.txt | 4 ++-- Documentation/misc-devices/c2port.txt | 6 +++--- Documentation/process/3.Early-stage.rst | 2 +- Documentation/process/7.AdvancedTopics.rst | 8 ++++---- Documentation/process/8.Conclusion.rst | 14 +++++++------- Documentation/process/adding-syscalls.rst | 4 ++-- Documentation/process/applying-patches.rst | 4 ++-- .../process/volatile-considered-harmful.rst | 4 ++-- Documentation/rbtree.txt | 4 ++-- Documentation/security/SCTP.rst | 2 +- Documentation/sphinx/kfigure.py | 6 +++--- Documentation/static-keys.txt | 2 +- Documentation/trace/events-msr.rst | 2 +- Documentation/trace/mmiotrace.rst | 2 +- Documentation/vm/ksm.rst | 2 +- Documentation/xz.txt | 6 +++--- scripts/kernel-doc | 2 +- 34 files changed, 69 insertions(+), 69 deletions(-)diff --git a/Documentation/COPYING-logo b/Documentation/COPYING-logo index
296f0f7f67eb..b21c7cf7d9f6100644
--- a/Documentation/COPYING-logo
+++ b/Documentation/COPYING-logo
@@ -9,5 +9,5 @@ scale down to smaller sizes and are better for letterheads or whatever
you want to use it for: for the full range of logos take a look at Larry's web-page:- http://www.isc.tamu.edu/~lewing/linux/
+ https://www.isc.tamu.edu/~lewing/linux/diff --git
a/Documentation/admin-guide/LSM/tomoyo.rstb/Documentation/admin-guide/LSM/tomoyo.rstindexe2d6b6e15082..4bc9c2b4da6f100644
---a/Documentation/admin-guide/LSM/tomoyo.rst+++b/Documentation/admin-guide/LSM/tomoyo.rst@@ -27,29 +27,29 @@ Where is documentation?
=======================User <-> Kernel interface documentation is available at
-http://tomoyo.osdn.jp/2.5/policy-specification/index.html . +https://tomoyo.osdn.jp/2.5/policy-specification/index.html .Materials we prepared for seminars and symposiums are available at
-http://osdn.jp/projects/tomoyo/docs/?category_id=532&language_id=1 . +https://osdn.jp/projects/tomoyo/docs/?category_id=532&language_id=1 .
Below lists are chosen from three aspects.What is TOMOYO?
TOMOYO Linux Overview
- http://osdn.jp/projects/tomoyo/docs/lca2009-takeda.pdf
+ https://osdn.jp/projects/tomoyo/docs/lca2009-takeda.pdf
TOMOYO Linux: pragmatic and manageable security for Linux
- http://osdn.jp/projects/tomoyo/docs/freedomhectaipei-tomoyo.pdf
+ https://osdn.jp/projects/tomoyo/docs/freedomhectaipei-tomoyo.pdf
TOMOYO Linux: A Practical Method to Understand and Protect Your
Own Linux Box
- http://osdn.jp/projects/tomoyo/docs/PacSec2007-en-no-demo.pdf
+ https://osdn.jp/projects/tomoyo/docs/PacSec2007-en-no-demo.pdfWhat can TOMOYO do?
Deep inside TOMOYO Linux
- http://osdn.jp/projects/tomoyo/docs/lca2009-kumaneko.pdf
+ https://osdn.jp/projects/tomoyo/docs/lca2009-kumaneko.pdf
The role of "pathname based access control" in security.
- http://osdn.jp/projects/tomoyo/docs/lfj2008-bof.pdf
+ https://osdn.jp/projects/tomoyo/docs/lfj2008-bof.pdfHistory of TOMOYO?
Realities of Mainlining
- http://osdn.jp/projects/tomoyo/docs/lfj2008.pdf
+ https://osdn.jp/projects/tomoyo/docs/lfj2008.pdfWhat is future plan?
====================
diff --gita/Documentation/admin-guide/acpi/initrd_table_override.rstb/Documentation/admin-guide/acpi/initrd_table_override.rstindexcbd768207631..bb24fa6b5fbe100644
---a/Documentation/admin-guide/acpi/initrd_table_override.rst+++b/Documentation/admin-guide/acpi/initrd_table_override.rst@@ -102,7 +102,7 @@ Where to retrieve userspace tools
=================================iasl and acpixtract are part of Intel's ACPICA project:
-http://acpica.org/
+https://acpica.org/and should be packaged by distributions (for example in the acpica
package
on SUSE).
diff --gita/Documentation/admin-guide/bcache.rstb/Documentation/admin-guide/bcache.rst
indexc0ce64d75bbf..1eccf952876d100644
---a/Documentation/admin-guide/bcache.rst
+++b/Documentation/admin-guide/bcache.rst
@@ -7,9 +7,9 @@ nice if you could use them as cache... Hence bcache.Wiki and git repositories are at:
- - http://bcache.evilpiepirate.org
+ - https://bcache.evilpiepirate.org
- http://evilpiepirate.org/git/linux-bcache.git
- - http://evilpiepirate.org/git/bcache-tools.git
+ - https://evilpiepirate.org/git/bcache-tools.gitIt's designed around the performance characteristics of SSDs - it
only allocates
in erase block sized buckets, and it uses a hybrid btree/log to
track cached
diff --gita/Documentation/admin-guide/devices.rstb/Documentation/admin-guide/devices.rst
indexd41671aeaef0..035275fedbdd100644
---a/Documentation/admin-guide/devices.rst
+++b/Documentation/admin-guide/devices.rst
@@ -17,7 +17,7 @@ Specifically explore the sections titled "CHAR and MISC DRIVERS", and
to involve for character and block devices.This document is included by reference into the Filesystem Hierarchy
-Standard (FHS). The FHS is available from
http://www.pathname.com/fhs/.
+Standard (FHS). The FHS is available from
https://www.pathname.com/fhs/.Allocations marked (68k/Amiga) apply to Linux/68k on the Amiga platform only. Allocations marked (68k/Atari) apply to Linux/68k on
diff --gita/Documentation/admin-guide/initrd.rstb/Documentation/admin-guide/initrd.rst
indexa03dabaaf3a3..67bbad8806e8100644
---a/Documentation/admin-guide/initrd.rst
+++b/Documentation/admin-guide/initrd.rst
@@ -376,7 +376,7 @@ Resources
---------.. [#f1] Almesberger, Werner; "Booting Linux: The History and the
Future"
- http://www.almesberger.net/cv/papers/ols2k-9.ps.gz
+ https://www.almesberger.net/cv/papers/ols2k-9.ps.gz
.. [#f2] newlib package (experimental), with initrd example
https://www.sourceware.org/newlib/
.. [#f3] util-linux: Miscellaneous utilities for Linux
diff --gita/Documentation/admin-guide/md.rstb/Documentation/admin-guide/md.rst
index3c51084ffd37..d973d469ffc4100644
---a/Documentation/admin-guide/md.rst
+++b/Documentation/admin-guide/md.rst
@@ -5,7 +5,7 @@ Boot time assembly of RAID arrays
---------------------------------Tools that manage md devices can be found at
- http://www.kernel.org/pub/linux/utils/raid/
+ https://www.kernel.org/pub/linux/utils/raid/You can boot with your md device with the following kernel command
diff --gita/Documentation/admin-guide/mono.rstb/Documentation/admin-guide/mono.rst
index59e6d59f0ed9..c6dab5680065100644
---a/Documentation/admin-guide/mono.rst
+++b/Documentation/admin-guide/mono.rst
@@ -12,11 +12,11 @@ other program after you have done the following:
a binary package, a source tarball or by installing from Git.
Binary
packages for several distributions can be found at:- http://www.mono-project.com/download/
+ https://www.mono-project.com/download/Instructions for compiling Mono can be found at:
- http://www.mono-project.com/docs/compiling-mono/linux/
+ https://www.mono-project.com/docs/compiling-mono/linux/Once the Mono CLR support has been installed, just check that ``/usr/bin/mono`` (which could be located elsewhere, for example
diff --gita/Documentation/admin-guide/reporting-bugs.rstb/Documentation/admin-guide/reporting-bugs.rst
index49ac8dc3594d..42481ea7b41d100644
---a/Documentation/admin-guide/reporting-bugs.rst
+++b/Documentation/admin-guide/reporting-bugs.rst
@@ -75,7 +75,7 @@ Tips for reporting bugsIf you haven't reported a bug before, please read:
- http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
+ https://www.chiark.greenend.org.uk/~sgtatham/bugs.htmlhttp://www.catb.org/esr/faqs/smart-questions.html
diff --git
a/Documentation/admin-guide/unicode.rstb/Documentation/admin-guide/unicode.rst
index7425a3351321..290fe83ebe82100644
---a/Documentation/admin-guide/unicode.rst
+++b/Documentation/admin-guide/unicode.rst
@@ -114,7 +114,7 @@ Unicode practice.
This range is now officially managed by the ConScript Unicode Registry. The normative reference is at:- http://www.evertype.com/standards/csur/klingon.html
+ https://www.evertype.com/standards/csur/klingon.htmlKlingon has an alphabet of 26 characters, a positional numeric writing system with 10 digits, and is written left-to-right, top-to-bottom.
@@ -178,7 +178,7 @@ fictional and artificial scripts has been established by John Cowan
<[email protected] <mailto:[email protected]>> and
Michael Everson <[email protected] <mailto:[email protected]>>.
The ConScript Unicode Registry is accessible at:- http://www.evertype.com/standards/csur/
+ https://www.evertype.com/standards/csur/The ranges used fall at the low end of the End User Zone and can hence not be normatively assigned, but it is recommended that people who
diff --gita/Documentation/conf.pyb/Documentation/conf.pyindex9ae8e9abf846..361e038c5474100644
---a/Documentation/conf.py
+++b/Documentation/conf.py
@@ -576,7 +576,7 @@epub_exclude_files= ['search.html']
# Grouping the document tree into PDF files. List of tuples # (source start file, target name, title, author, options). #
-# See the Sphinx chapter of http://ralsina.me/static/manual.pdf
+# See the Sphinx chapter of https://ralsina.me/static/manual.pdf
#
# FIXME: Do not add the index file here; the result will be too
big. Adding
# multiple PDF files here actually tries to get the
cross-referencing right
diff --gita/Documentation/dev-tools/gdb-kernel-debugging.rstb/Documentation/dev-tools/gdb-kernel-debugging.rst
index19df79286f00..4756f6b3a04e100644
---a/Documentation/dev-tools/gdb-kernel-debugging.rst
+++b/Documentation/dev-tools/gdb-kernel-debugging.rst
@@ -24,7 +24,7 @@ Setup- Create a virtual Linux machine for QEMU/KVM (see
www.linux-kvm.org <http://www.linux-kvm.org> and www.qemu.org <http://www.qemu.org> for more details). For cross-development,
- http://landley.net/aboriginal/bin keeps a pool of machine images and
+ https://landley.net/aboriginal/bin keeps a pool of machine images and toolchains that can be helpful to start from.- Build the kernel with
CONFIG_GDB_SCRIPTSenabled, but leave
diff --gita/Documentation/doc-guide/parse-headers.rstb/Documentation/doc-guide/parse-headers.rst
index24cfaa15dd81..ac5d9304a918100644
---a/Documentation/doc-guide/parse-headers.rst
+++b/Documentation/doc-guide/parse-headers.rst
@@ -186,7 +186,7 @@ COPYRIGHTCopyright (c) 2016 by Mauro Carvalho Chehab
<[email protected] <mailto:mchehab%[email protected]>>.-License GPLv2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>.
+License GPLv2: GNU GPL version 2 <https://gnu.org/licenses/gpl.html>.This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
diff --gita/Documentation/driver-api/acpi/linuxized-acpica.rstb/Documentation/driver-api/acpi/linuxized-acpica.rstindex0ca8f1538519..6bee03383225100644
---a/Documentation/driver-api/acpi/linuxized-acpica.rst+++b/Documentation/driver-api/acpi/linuxized-acpica.rst@@ -175,9 +175,9 @@ illustrated in the following figure::
B. acpica / master - "master" branch of the git repository at
<https://github.com/acpica/acpica.git>.
C. linux-pm / linux-next - "linux-next" branch of the git
repository at
-
<http://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git>.
+
<https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git>.
D. linux / master - "master" branch of the git repository at
-
<http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git>.
+
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git>.Before the linuxized ACPICA patches are sent to the Linux ACPI
community
for review, there is a quality assurance build test process to
reduce
@@ -274,6 +274,6 @@ before they become available from the ACPICA release process.
a diff file indicating the state of the current divergences::# git clone https://github.com/acpica/acpica
- # git clone
http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
+ # git clone
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
# cd acpica
#generate/linux/divergences.sh-s ../linux
diff --gita/Documentation/driver-api/usb/bulk-streams.rstb/Documentation/driver-api/usb/bulk-streams.rst
index99b515babdeb..eeefe582f8ff100644
---a/Documentation/driver-api/usb/bulk-streams.rst+++b/Documentation/driver-api/usb/bulk-streams.rst
@@ -9,9 +9,9 @@ device driver to overload a bulk endpoint so that multiple transfers can be
queued at once.Streams are defined in sections 4.4.6.4 and 8.12.1.4 of the
Universal Serial Bus
-3.0 specification at http://www.usb.org/developers/docs/ The USB Attached SCSI
+3.0 specification at https://www.usb.org/developers/docs/ The USB Attached SCSI
Protocol, which uses streams to queue multiple SCSI commands, can
be found on
-the T10 website (http://t10.org/).
+the T10 website (https://t10.org/).Device-side implications
diff --gita/Documentation/driver-api/usb/writing_musb_glue_layer.rstb/Documentation/driver-api/usb/writing_musb_glue_layer.rstindex5bf7152fd76f..10416cc11cd5100644
---a/Documentation/driver-api/usb/writing_musb_glue_layer.rst+++b/Documentation/driver-api/usb/writing_musb_glue_layer.rst@@ -707,12 +707,12 @@ cheerful guidance and support.
Resources
=========-USB Home Page: http://www.usb.org
+USB Home Page: https://www.usb.org-linux-usb Mailing List Archives: http://marc.info/?l=linux-usb
+linux-usb Mailing List Archives: https://marc.info/?l=linux-usbUSB On-the-Go Basics:
-http://www.maximintegrated.com/app-notes/index.mvp/id/1822 +https://www.maximintegrated.com/app-notes/index.mvp/id/1822:ref:
Writing USB Device Drivers <writing-usb-driver>diff --git
a/Documentation/filesystems/path-lookup.txtb/Documentation/filesystems/path-lookup.txt
index9b8930f589d9..1aa7ce099f6f100644
---a/Documentation/filesystems/path-lookup.txt
+++b/Documentation/filesystems/path-lookup.txt
@@ -375,7 +375,7 @@ common path elements, the more likely they will exist in dentry cache.
Papers and other documentation on dcache locking
================================================-1. Scaling dcache with RCU
(http://linuxjournal.com/article.php?sid=7124).
+1. Scaling dcache with RCU
(https://linuxjournal.com/article.php?sid=7124).2. http://lse.sourceforge.net/locking/dcache/dcache.html
diff --git
a/Documentation/filesystems/seq_file.txtb/Documentation/filesystems/seq_file.txtindexd412b236a9d6..361ff0ebf17a100644 ---a/Documentation/filesystems/seq_file.txt+++b/Documentation/filesystems/seq_file.txt@@ -2,7 +2,7 @@ Theseq_fileinterfaceCopyright 2003 Jonathan Corbet <[email protected]
<mailto:[email protected]>>
This file is originally from the LWN.net Driver Porting
series at
- http://lwn.net/Articles/driver-porting/
+ https://lwn.net/Articles/driver-porting/There are numerous ways for a device driver (or other kernel
component) to
@@ -52,7 +52,7 @@ Then concatenate the output files out1 and out2 and get the right
result. Yes, it is a thoroughly useless module, but the point is
to show
how the mechanism works without getting lost in other details. (Those wanting to see the full source for this module can find it at
-http://lwn.net/Articles/22359/). +https://lwn.net/Articles/22359/).Deprecated
create_proc_entrydiff --git
a/Documentation/misc-devices/c2port.txtb/Documentation/misc-devices/c2port.txt
indexea7344465610..31351b1a5a1f100644
---a/Documentation/misc-devices/c2port.txt
+++b/Documentation/misc-devices/c2port.txt
@@ -28,14 +28,14 @@ where the micro controller is connected via special GPIOs pins.
References
-----------The C2 Interface main references are at (http://www.silabs.com)
+The C2 Interface main references are at (https://www.silabs.com)
Silicon Laboratories site], see:- AN127: FLASH Programming via the C2 Interface at
-http://www.silabs.com/Support Documents/TechnicalDocs/an127.pdf +https://www.silabs.com/Support Documents/TechnicalDocs/an127.pdf- C2 Specification at
-http://www.silabs.com/pages/DownloadDoc.aspx?FILEURL=Support%20Documents/TechnicalDocs/an127.pdf&src=SearchResults +https://www.silabs.com/pages/DownloadDoc.aspx?FILEURL=Support%20Documents/TechnicalDocs/an127.pdf&src=SearchResultshowever it implements a two wire serial communication protocol (bit banging) designed to enable in-system programming, debugging, and
diff --gita/Documentation/process/3.Early-stage.rstb/Documentation/process/3.Early-stage.rst
indexbe00716071d4..eaafb4b22f33100644
---a/Documentation/process/3.Early-stage.rst
+++b/Documentation/process/3.Early-stage.rst
@@ -46,7 +46,7 @@ and posted this:
to communicate user requirements to these people is a waste of time. They are much too "intelligent" to listen to lesser
mortals.-(http://lwn.net/Articles/131776/).
+(https://lwn.net/Articles/131776/).The reality of the situation was different; the kernel developers
were far
more concerned about system stability, long-term maintenance, and
finding
diff --gita/Documentation/process/7.AdvancedTopics.rstb/Documentation/process/7.AdvancedTopics.rst
index172733cff097..bf7cbfb4caa5100644
---a/Documentation/process/7.AdvancedTopics.rst
+++b/Documentation/process/7.AdvancedTopics.rst
@@ -29,9 +29,9 @@ long document in its own right. Instead, the focus here will be on how git
fits into the kernel development process in particular.
Developers who
wish to come up to speed with git will find more information at:- http://git-scm.com/
+ https://git-scm.com/- http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
+ https://www.kernel.org/pub/software/scm/git/docs/user-manual.htmland on various tutorials found on the web.
@@ -55,7 +55,7 @@ server with git-daemon is relatively straightforward if you have a system
which is accessible to the Internet. Otherwise, free, public
hosting sites
(Github, for example) are starting to appear on the net. Established developers can get an account on kernel.org <http://kernel.org>,
but those are not easy to come
-by; see http://kernel.org/faq/ for more information.
+by; see https://kernel.org/faq/ for more information.The normal git workflow involves the use of a lot of branches.
Each line
of development can be separated into a separate "topic branch" and
@@ -125,7 +125,7 @@ can affect your ability to get trees pulled in the future. Quoting Linus:
to trust things *without* then having to go and check every individual change by hand.-(http://lwn.net/Articles/224135/).
+(https://lwn.net/Articles/224135/).To avoid this kind of situation, ensure that all patches within a
given
branch stick closely to the associated topic; a "driver fixes" branch
diff --gita/Documentation/process/8.Conclusion.rstb/Documentation/process/8.Conclusion.rst
index8395aa2c1f3a..b32a40215858100644
---a/Documentation/process/8.Conclusion.rst
+++b/Documentation/process/8.Conclusion.rst
@@ -16,24 +16,24 @@ distributions runs into internal limits and fails to process the documents
properly).Various web sites discuss kernel development at all levels of
detail. Your
-author would like to humbly suggest http://lwn.net/ as a source; +author would like to humbly suggest https://lwn.net/ as a source;
information on many specific kernel topics can be found via the
LWN kernel
index at:- http://lwn.net/Kernel/Index/
+ https://lwn.net/Kernel/Index/Beyond that, a valuable resource for kernel developers is:
- http://kernelnewbies.org/
+ https://kernelnewbies.org/-And, of course, one should not forget http://kernel.org/, the definitive
+And, of course, one should not forget https://kernel.org/, the definitive
location for kernel release information.There are a number of books on kernel development:
Linux Device Drivers, 3rd Edition (Jonathan Corbet, Alessandro Rubini, and Greg Kroah-Hartman). Online at
- http://lwn.net/Kernel/LDD3/.
+ https://lwn.net/Kernel/LDD3/.Linux Kernel Development (Robert Love).
@@ -46,9 +46,9 @@ information to be found there.
Documentation for git can be found at:
- http://www.kernel.org/pub/software/scm/git/docs/
+ https://www.kernel.org/pub/software/scm/git/docs/- http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
+ https://www.kernel.org/pub/software/scm/git/docs/user-manual.htmlConclusion
diff --gita/Documentation/process/adding-syscalls.rstb/Documentation/process/adding-syscalls.rst
index1c3a840d06b9..d25a1d34dd1d100644
---a/Documentation/process/adding-syscalls.rst
+++b/Documentation/process/adding-syscalls.rst
@@ -541,9 +541,9 @@ References and Sources
:manpage:syscall(2)man-page:
http://man7.org/linux/man-pages/man2/syscall.2.html#NOTES
- Collated emails from Linus Torvalds discussing the problems
with ``ioctl()``:
- http://yarchive.net/comp/linux/ioctl.html
+ https://yarchive.net/comp/linux/ioctl.html
- "How to not invent kernel interfaces", Arnd Bergmann,
- http://www.ukuug.org/events/linux2007/2007/papers/Bergmann.pdf
+ https://www.ukuug.org/events/linux2007/2007/papers/Bergmann.pdf
- LWN article from Michael Kerrisk on avoiding new uses of
CAP_SYS_ADMIN:
https://lwn.net/Articles/486306/
- Recommendation from Andrew Morton that all related information
for a new
diff --gita/Documentation/process/applying-patches.rstb/Documentation/process/applying-patches.rst
indexfbb9297e6360..2e7017bef4b8100644
---a/Documentation/process/applying-patches.rst
+++b/Documentation/process/applying-patches.rst
@@ -229,7 +229,7 @@ Although interdiff may save you a step or two you are generally advised to
do the additional steps since interdiff can get things wrong in
some cases.Another alternative is ``ketchup``, which is a python script for
automatic
-downloading and applying of patches (http://www.selenic.com/ketchup/).
+downloading and applying of patches (https://www.selenic.com/ketchup/).Other nice tools are diffstat, which shows a summary of changes
made by a
patch; lsdiff, which displays a short listing of affected files in
a patch
@@ -241,7 +241,7 @@ the patch contains a given regular expression.
Where can I download the patches?
=================================-The patches are available at http://kernel.org/
+The patches are available at https://kernel.org/
Most recent patches are linked from the front page, but they also have specific homes.diff --git
a/Documentation/process/volatile-considered-harmful.rstb/Documentation/process/volatile-considered-harmful.rstindex4934e656a6f3..7eb6bd7c9214100644
---a/Documentation/process/volatile-considered-harmful.rst+++b/Documentation/process/volatile-considered-harmful.rst@@ -109,9 +109,9 @@ been properly thought through.
References
==========-[1] http://lwn.net/Articles/233481/
+[1] https://lwn.net/Articles/233481/-[2] http://lwn.net/Articles/233482/
+[2] https://lwn.net/Articles/233482/Credits
=======
diff --gita/Documentation/rbtree.txtb/Documentation/rbtree.txtindex523d54b60087..6b88837fbf82100644
---a/Documentation/rbtree.txt
+++b/Documentation/rbtree.txt
@@ -36,10 +36,10 @@ This document covers use of the Linux rbtree implementation. For more
information on the nature and implementation of Red Black Trees, see:Linux Weekly News article on red-black trees
- http://lwn.net/Articles/184495/
+ https://lwn.net/Articles/184495/Wikipedia entry on red-black trees
- http://en.wikipedia.org/wiki/Red-black_tree
+ https://en.wikipedia.org/wiki/Red-black_treeLinux implementation of red-black trees
---------------------------------------
diff --gita/Documentation/security/SCTP.rstb/Documentation/security/SCTP.rst
indexd903eb97fcf3..0bcf6c1245ee100644
---a/Documentation/security/SCTP.rst
+++b/Documentation/security/SCTP.rst
@@ -328,7 +328,7 @@ NOTES:
label (see **netlabel-config**\(8) helper script for details).5) The NetLabel SCTP peer labeling rules apply as discussed in
the following
- set of posts tagged "netlabel" at:
http://www.paul-moore.com/blog/t.
+ set of posts tagged "netlabel" at:
https://www.paul-moore.com/blog/t.6) CIPSO is only supported for IPv4 addressing:
``socket(AF_INET, ...)``
CALIPSO is only supported for IPv6 addressing:
``socket(AF_INET6, ...)``
diff --gita/Documentation/sphinx/kfigure.pyb/Documentation/sphinx/kfigure.py
indexfbfe6693bb60..788704886eec100644
---a/Documentation/sphinx/kfigure.py
+++b/Documentation/sphinx/kfigure.py
@@ -29,7 +29,7 @@ u"""Used tools:
- * ``dot(1)``: Graphviz (http://www.graphviz.org). If Graphviz is not
+ * ``dot(1)``: Graphviz (https://www.graphviz.org). If Graphviz is not
available, the DOT language is inserted as literal-block.* SVG to PDF: To generate PDF, you need at least one of this
tools:
@@ -41,7 +41,7 @@ u"""
* generate PDF from SVG / used by PDF (LaTeX) builder* generate SVG (html-builder) and PDF (latex-builder) from DOT
files.
- DOT: see http://www.graphviz.org/content/dot-language
+ DOT: see https://www.graphviz.org/content/dot-language"""
@@ -182,7 +182,7 @@ def setupTools(app):
kernellog.verbose(app, "use dot(1) from: " +dot_cmd) else:
kernellog.warn(app, "dot(1) not found, for better output
quality install "
- "graphviz from http://www.graphviz.org")
+ "graphviz from https://www.graphviz.org")
ifconvert_cmd:
kernellog.verbose(app, "use convert(1) from: " +convert_cmd) else:
diff --gita/Documentation/static-keys.txtb/Documentation/static-keys.txt
index9803e14639bf..38290b9f25eb100644
---a/Documentation/static-keys.txt
+++b/Documentation/static-keys.txt
@@ -71,7 +71,7 @@ Solutiongcc (v4.5) adds a new 'asm goto' statement that allows branching
to a label:-http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01556.html +https://gcc.gnu.org/ml/gcc-patches/2009-07/msg01556.html
Using the 'asm goto', we can create branches that are either taken
or not taken
by default, without the need to check memory. Then, at run-time,
we can patch
diff --gita/Documentation/trace/events-msr.rstb/Documentation/trace/events-msr.rst
indexe938aa0b6f4f..810481e530b6100644
---a/Documentation/trace/events-msr.rst
+++b/Documentation/trace/events-msr.rst
@@ -4,7 +4,7 @@ MSR Trace EventsThe x86 kernel supports tracing most MSR (Model Specific Register)
accesses.
To see the definition of the MSRs on Intel systems please see the SDM
-at http://www.intel.com/sdm (Volume 3)
+at https://www.intel.com/sdm (Volume 3)Available trace points:
diff --git
a/Documentation/trace/mmiotrace.rstb/Documentation/trace/mmiotrace.rst
index5116e8ca27b4..fed13eaead89100644 ---a/Documentation/trace/mmiotrace.rst+++b/Documentation/trace/mmiotrace.rst
@@ -5,7 +5,7 @@ In-kernel memory-mapped I/O tracingHome page and links to optional user space tools:
- http://nouveau.freedesktop.org/wiki/MmioTrace
+ https://nouveau.freedesktop.org/wiki/MmioTraceMMIO tracing was originally developed by Intel around 2003 for
their Fault
Injection Test Harness. In Dec 2006 - Jan 2007, using the code
from Intel,
diff --gita/Documentation/vm/ksm.rstb/Documentation/vm/ksm.rstindexd32016d9be2c..d1b7270ad55c100644
---a/Documentation/vm/ksm.rst
+++b/Documentation/vm/ksm.rst
@@ -6,7 +6,7 @@ Kernel Samepage MergingKSM is a memory-saving de-duplication feature, enabled by
CONFIG_KSM=y,
added to the Linux kernel in 2.6.32. See ``mm/ksm.c`` for its
implementation,
-and http://lwn.net/Articles/306704/ and http://lwn.net/Articles/330589/
+and http://lwn.net/Articles/306704/ and
https://lwn.net/Articles/330589/The userspace interface of KSM is described in
:ref:Documentation/admin-guide/mm/ksm.rst <admin_guide_ksm>diff --git
a/Documentation/xz.txtb/Documentation/xz.txtindexb2220d03aa50..b2f5ff12a161100644
---a/Documentation/xz.txt
+++b/Documentation/xz.txt
@@ -14,13 +14,13 @@ improve compression ratio of executable data.
The XZ decompressor in Linux is called XZ Embedded. It supports the LZMA2 filter and optionally also BCJ filters. CRC32 is supported for integrity checking. The home page of XZ Embedded is at
-<http://tukaani.org/xz/embedded.html>, where you can find the +<https://tukaani.org/xz/embedded.html>, where you can find the
latest version and also information about using the code outside the Linux kernel.For userspace, XZ Utils provide a zlib-like compression library and a gzip-like command line tool. XZ Utils can be downloaded from
-<http://tukaani.org/xz/>.
+<https://tukaani.org/xz/>.XZ related components in the kernel
===================================
@@ -113,7 +113,7 @@ Reporting bugs
==============Before reporting a bug, please check that it's not fixed already
-at upstream. See <http://tukaani.org/xz/embedded.html> to get the +at upstream. See <https://tukaani.org/xz/embedded.html> to get the
latest code.Report bugs to <[email protected]
<mailto:[email protected]>> or visit #tukaani on diff --git a/scripts/kernel-doc b/scripts/kernel-doc indexf746ca8fa403..b04d395ca894100755
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -317,7 +317,7 @@ if (defined($ENV{'KBUILD_VERBOSE'})) {# Generated docbook code is inserted in a template at a point where # docbook v3.1 requires a non-zero sequence of RefEntry's; see:
-#
http://www.oasis-open.org/docbook/documentation/reference/html/refentry.html
+#
https://www.oasis-open.org/docbook/documentation/reference/html/refentry.html
# We keep track of number of generated entries and generate a dummy # if needs be to ensure the expanded template can be postprocessed # into html.
--
2.26.2
Jonathan Corbet
maintainerQuoted 38 lines · On Wed, 20 May 2020 22:00:37 +0200 "Alexander A. Klimov"…
Rationale: Reduces attack surface on kernel devs for MITM.
Deterministic algorithm:
For each file:
For each line:
If doesn't contain\bxmlns\b:
For each link,\bhttp://[^# \t\r\n]*(?:\w|/):
If both the HTTP and HTTPS versions return 200 OK and serve the same content:
Replace HTTP with HTTPS.--- Documentation/COPYING-logo | 2 +- Documentation/admin-guide/LSM/tomoyo.rst | 16 ++++++++-------- .../admin-guide/acpi/initrd_table_override.rst | 2 +- Documentation/admin-guide/bcache.rst | 4 ++-- Documentation/admin-guide/devices.rst | 2 +- Documentation/admin-guide/initrd.rst | 2 +- Documentation/admin-guide/md.rst | 2 +- Documentation/admin-guide/mono.rst | 4 ++-- Documentation/admin-guide/reporting-bugs.rst | 2 +- Documentation/admin-guide/unicode.rst | 4 ++-- Documentation/conf.py | 2 +- Documentation/dev-tools/gdb-kernel-debugging.rst | 2 +- Documentation/doc-guide/parse-headers.rst | 2 +- .../driver-api/acpi/linuxized-acpica.rst | 6 +++--- Documentation/driver-api/usb/bulk-streams.rst | 4 ++-- .../driver-api/usb/writing_musb_glue_layer.rst | 6 +++--- Documentation/filesystems/path-lookup.txt | 2 +- Documentation/filesystems/seq_file.txt | 4 ++-- Documentation/misc-devices/c2port.txt | 6 +++--- Documentation/process/3.Early-stage.rst | 2 +- Documentation/process/7.AdvancedTopics.rst | 8 ++++---- Documentation/process/8.Conclusion.rst | 14 +++++++------- Documentation/process/adding-syscalls.rst | 4 ++-- Documentation/process/applying-patches.rst | 4 ++-- .../process/volatile-considered-harmful.rst | 4 ++-- Documentation/rbtree.txt | 4 ++-- Documentation/security/SCTP.rst | 2 +-
Quoted 8 lines
Documentation/sphinx/kfigure.py | 6 +++--- Documentation/static-keys.txt | 2 +- Documentation/trace/events-msr.rst | 2 +- Documentation/trace/mmiotrace.rst | 2 +- Documentation/vm/ksm.rst | 2 +- Documentation/xz.txt | 6 +++--- scripts/kernel-doc | 2 +- 34 files changed, 69 insertions(+), 69 deletions(-)
OK, so this is still pretty large; I had asked you to narrow things further. And the rationale is still pretty thin. And I would *really* rather see the docs updated in a more thoughtful way that considers the value of the links rather than just the protocol used.
But this does not seem to do harm at this point, so I have gone ahead and applied it.
If you proceed with this work, I'd encourage you to be narrow in your focus, be sure to copy the right people, and to justify the changes well, or you may well run into pushback.
Thanks,
jon
Am 25.05.20 um 18:28 schrieb Jonathan Corbet:
Quoted 50 lines
Quoted 38 lines · On Wed, 20 May 2020 22:00:37 +0200 "Alexander A. Klimov"…
Rationale: Reduces attack surface on kernel devs for MITM.
Deterministic algorithm:
For each file:
For each line:
If doesn't contain\bxmlns\b:
For each link,\bhttp://[^# \t\r\n]*(?:\w|/):
If both the HTTP and HTTPS versions return 200 OK and serve the same content:
Replace HTTP with HTTPS.--- Documentation/COPYING-logo | 2 +- Documentation/admin-guide/LSM/tomoyo.rst | 16 ++++++++-------- .../admin-guide/acpi/initrd_table_override.rst | 2 +- Documentation/admin-guide/bcache.rst | 4 ++-- Documentation/admin-guide/devices.rst | 2 +- Documentation/admin-guide/initrd.rst | 2 +- Documentation/admin-guide/md.rst | 2 +- Documentation/admin-guide/mono.rst | 4 ++-- Documentation/admin-guide/reporting-bugs.rst | 2 +- Documentation/admin-guide/unicode.rst | 4 ++-- Documentation/conf.py | 2 +- Documentation/dev-tools/gdb-kernel-debugging.rst | 2 +- Documentation/doc-guide/parse-headers.rst | 2 +- .../driver-api/acpi/linuxized-acpica.rst | 6 +++--- Documentation/driver-api/usb/bulk-streams.rst | 4 ++-- .../driver-api/usb/writing_musb_glue_layer.rst | 6 +++--- Documentation/filesystems/path-lookup.txt | 2 +- Documentation/filesystems/seq_file.txt | 4 ++-- Documentation/misc-devices/c2port.txt | 6 +++--- Documentation/process/3.Early-stage.rst | 2 +- Documentation/process/7.AdvancedTopics.rst | 8 ++++---- Documentation/process/8.Conclusion.rst | 14 +++++++------- Documentation/process/adding-syscalls.rst | 4 ++-- Documentation/process/applying-patches.rst | 4 ++-- .../process/volatile-considered-harmful.rst | 4 ++-- Documentation/rbtree.txt | 4 ++-- Documentation/security/SCTP.rst | 2 +-Quoted 8 lines
Documentation/sphinx/kfigure.py | 6 +++--- Documentation/static-keys.txt | 2 +- Documentation/trace/events-msr.rst | 2 +- Documentation/trace/mmiotrace.rst | 2 +- Documentation/vm/ksm.rst | 2 +- Documentation/xz.txt | 6 +++--- scripts/kernel-doc | 2 +- 34 files changed, 69 insertions(+), 69 deletions(-)
Quoted 4 lines
OK, so this is still pretty large; I had asked you to narrow things further. And the rationale is still pretty thin. And I would *really* rather see the docs updated in a more thoughtful way that considers the value of the links rather than just the protocol used.
OK, I'll keep that size rating in mind.
Also I'll try to reason a bit verbosely. (Not my skill #1, sorry.)
I have already one more enhancement idea, but I'd like not to have > 1 open kernel construction areas of mine in parallel (to reduce merge conflicts).
Quoted 3 lines
But this does not seem to do harm at this point, so I have gone ahead and applied it.
What does this mean? Is there a kernel.org repo/branch with my patch?
Quoted 4 lines
If you proceed with this work, I'd encourage you to be narrow in your focus, be sure to copy the right people, and to justify the changes well, or you may well run into pushback.
I try my best while CCing, but some mailing lists seem to have (silently!) rejected my patch (see discussion on a previous version of my patch).
Does it matter whether I just feed the output of ...
perl scripts/get_maintainer.pl --separator , --norolestats 0001-Replace-HTTP-links-with-HTTPS-ones-documentation.patch
... into Git send-email To: prompt or actually CC: (not To:) mailing lists?
Quoted 5 lines
Thanks,
jon
Quoted 6 lines · Alexander A. Klimov
Does it matter whether I just feed the output of ...
perl
scripts/get_maintainer.pl--separator , --norolestats 0001-Replace-HTTP-links-with-HTTPS-ones-documentation.patch... into Git send-email To: prompt or actually CC: (not To:) mailing lists?
Yes. vger mailing lists drop emails with large to:/cc:
headers (It was >1024 chars, it may be different now)
It's generally better to add --nogit --nogit-fallback to get_maintainer to avoid the git lookup addition of people that have modified files that aren't listed in MAINTAINERS.
You could add a --bcc with those dropped names if you really want to have those people receive the emails.
Am 25.05.20 um 20:24 schrieb Joe Perches:
Quoted 10 lines · Alexander A. Klimov
Quoted 6 lines
Does it matter whether I just feed the output of ...
perl
scripts/get_maintainer.pl--separator , --norolestats 0001-Replace-HTTP-links-with-HTTPS-ones-documentation.patch... into Git send-email To: prompt or actually CC: (not To:) mailing lists?
Yes. vger mailing lists drop emails with large to:/cc:
headers (It was >1024 chars, it may be different now)
Good to know.
Quoted 4 lines
It's generally better to add --nogit --nogit-fallback to
get_maintainerto avoid the git lookup addition of people that have modified files that aren't listed inMAINTAINERS.
Really? I used them for a previous version of my patch, but Jon (who didn't use that params) complained about too many people not being CCed.
As Jon now applied (whatever branch on...) my patch, I assume that not using those params is better.
After all not using them doesn't enlarge the set of recipients per patch (of mine), but reduces patch size as I group changed files per set of recipients.
Quoted 4 lines
You could add a --bcc with those dropped names if you really want to have those people receive the emails.
Jonathan Corbet
maintainerQuoted 3 lines · On Mon, 25 May 2020 20:01:45 +0200 "Alexander A. Klimov"…
Quoted 2 lines
But this does not seem to do harm at this point, so I have gone ahead and applied it.
What does this mean? Is there a kernel.org repo/branch with my patch?
That means it's in the docs-next tree.
jon