Fix some minor invalid URLs

modify validate_markdown_links.py a little

Signed-off-by: Dongliang Mu <[email protected]>

Author: mudongliang

Diff for: CONTRIBUTORS.md

@@ -36,7 +36,7 @@
 
 [@woodpenker](http://github.com/woodpenker)
 
-[@tjm-1990](http://github.com/tjm-1990)
+@tjm-1990
 
 [@up2wing](https://github.com/up2wing)
 
@@ -48,4 +48,4 @@
 
 [@Albertchamberlain](https://github.com/Albertchamberlain)
 
-[@nannxnann](https://github.com/nannxnann)
+@nannxnann

Diff for: Cgroups/linux-cgroups-1.md

@@ -435,7 +435,7 @@ struct cgroup_subsys cpuset_cgrp_subsys = {
 
 * [control groups](https://en.wikipedia.org/wiki/Cgroups)
 * [PID](https://en.wikipedia.org/wiki/Process_identifier)
-* [cpuset](http://man7.org/linux/man-pages/man7/cpuset.7.html)
+* [cpuset](https://man7.org/linux/man-pages/man7/cpuset.7.html)
 * [block devices](https://en.wikipedia.org/wiki/Device_file)
 * [huge pages](https://www.kernel.org/doc/Documentation/vm/hugetlbpage.txt)
 * [sysfs](https://en.wikipedia.org/wiki/Sysfs)

Diff for: Concepts/linux-cpu-4.md

@@ -331,7 +331,7 @@ static struct notifier_block tracepoint_module_nb = {
 };
 ```
 
-When one of the `MODULE_STATE_LIVE`, `MODULE_STATE_COMING` or `MODULE_STATE_GOING` events occurred. For example the `MODULE_STATE_LIVE` the `MODULE_STATE_COMING` notifications will be sent during execution of the [init_module](http://man7.org/linux/man-pages/man2/init_module.2.html) [system call](/SysCall/linux-syscall-1.md). Or for example `MODULE_STATE_GOING` will be sent during execution of the [delete_module](http://man7.org/linux/man-pages/man2/delete_module.2.html) `system call`:
+When one of the `MODULE_STATE_LIVE`, `MODULE_STATE_COMING` or `MODULE_STATE_GOING` events occurred. For example the `MODULE_STATE_LIVE` the `MODULE_STATE_COMING` notifications will be sent during execution of the [init_module](https://man7.org/linux/man-pages/man2/init_module.2.html) [system call](/SysCall/linux-syscall-1.md). Or for example `MODULE_STATE_GOING` will be sent during execution of the [delete_module](https://man7.org/linux/man-pages/man2/delete_module.2.html) `system call`:
 
 ```C
 SYSCALL_DEFINE2(delete_module, const char __user *, name_user,
@@ -364,6 +364,6 @@ Links
 * [semaphore](/SyncPrim/linux-sync-3.md)
 * [tracepoints](https://www.kernel.org/doc/Documentation/trace/tracepoints.txt)
 * [system call](/SysCall/linux-syscall-1.md)
-* [init_module system call](http://man7.org/linux/man-pages/man2/init_module.2.html)
-* [delete_module](http://man7.org/linux/man-pages/man2/delete_module.2.html)
+* [init_module system call](https://man7.org/linux/man-pages/man2/init_module.2.html)
+* [delete_module](https://man7.org/linux/man-pages/man2/delete_module.2.html)
 * [previous part](/Concepts/linux-cpu-3.md)

Diff for: DataStructures/linux-datastructures-1.md

@@ -14,7 +14,7 @@ struct list_head {
 };
 ```
 
-你可能注意到这和你以前见过的双向链表的实现方法是不同的。举个例子来说，在 [glib](http://www.gnu.org/software/libc/)  库里是这样实现的：
+你可能注意到这和你以前见过的双向链表的实现方法是不同的。举个例子来说，在 [glib](https://www.gnu.org/software/libc/)  库里是这样实现的：
 
 ```C
 struct GList {

Diff for: DataStructures/linux-datastructures-3.md

@@ -340,7 +340,7 @@ static inline void bitmap_zero(unsigned long *dst, unsigned int nbits)
 	(__builtin_constant_p(nbits) && (nbits) <= BITS_PER_LONG)
 ```
 
-正如我们可以看到的，它检查 `nbits` 是否为编译期已知常量，并且其值不超过 `BITS_PER_LONG` 或 `64`。如果位数目没有超过一个 `long` 变量的位数，我们可以仅仅设置为 0。在其他情况，我们需要计算有多少个需要填充位数组的 `long` 变量并且使用 [memset](http://man7.org/linux/man-pages/man3/memset.3.html) 进行填充。
+正如我们可以看到的，它检查 `nbits` 是否为编译期已知常量，并且其值不超过 `BITS_PER_LONG` 或 `64`。如果位数目没有超过一个 `long` 变量的位数，我们可以仅仅设置为 0。在其他情况，我们需要计算有多少个需要填充位数组的 `long` 变量并且使用 [memset](https://man7.org/linux/man-pages/man3/memset.3.html) 进行填充。
 
 `bitmap_fill` 函数的实现和 `biramp_zero` 函数很相似，除了我们需要在给定的位数组中填写 `0xff` 或 `0b11111111`：
 
@@ -356,7 +356,7 @@ static inline void bitmap_fill(unsigned long *dst, unsigned int nbits)
 }
 ```
 
-除了 `bitmap_fill` 和 `bitmap_zero`，[include/linux/bitmap.h](https://github.com/torvalds/linux/blob/master/include/linux/bitmap.h) 头文件也提供了和 `bitmap_zero` 很相似的 `bitmap_copy`，只是仅仅使用 [memcpy](http://man7.org/linux/man-pages/man3/memcpy.3.html) 而不是  [memset](http://man7.org/linux/man-pages/man3/memset.3.html) 这点差异而已。它也提供了位数组的按位操作，像 `bitmap_and`, `bitmap_or`, `bitamp_xor`等等。我们不会探讨这些函数的实现了，因为如果你理解了本部分的所有内容，这些函数的实现是很容易理解的。无论如何，如果你对这些函数是如何实现的感兴趣，你可以打开并研究 [include/linux/bitmap.h](https://github.com/torvalds/linux/blob/master/include/linux/bitmap.h) 头文件。
+除了 `bitmap_fill` 和 `bitmap_zero`，[include/linux/bitmap.h](https://github.com/torvalds/linux/blob/master/include/linux/bitmap.h) 头文件也提供了和 `bitmap_zero` 很相似的 `bitmap_copy`，只是仅仅使用 [memcpy](https://man7.org/linux/man-pages/man3/memcpy.3.html) 而不是  [memset](https://man7.org/linux/man-pages/man3/memset.3.html) 这点差异而已。它也提供了位数组的按位操作，像 `bitmap_and`, `bitmap_or`, `bitamp_xor`等等。我们不会探讨这些函数的实现了，因为如果你理解了本部分的所有内容，这些函数的实现是很容易理解的。无论如何，如果你对这些函数是如何实现的感兴趣，你可以打开并研究 [include/linux/bitmap.h](https://github.com/torvalds/linux/blob/master/include/linux/bitmap.h) 头文件。
 
 本部分到此为止。
 
@@ -381,8 +381,8 @@ static inline void bitmap_fill(unsigned long *dst, unsigned int nbits)
 * [bt instruction](http://x86.renejeschke.de/html/file_module_x86_id_22.html)
 * [sbb instruction](http://x86.renejeschke.de/html/file_module_x86_id_286.html)
 * [btc instruction](http://x86.renejeschke.de/html/file_module_x86_id_23.html)
-* [man memcpy](http://man7.org/linux/man-pages/man3/memcpy.3.html) 
-* [man memset](http://man7.org/linux/man-pages/man3/memset.3.html)
+* [man memcpy](https://man7.org/linux/man-pages/man3/memcpy.3.html) 
+* [man memset](https://man7.org/linux/man-pages/man3/memset.3.html)
 * [CF](https://en.wikipedia.org/wiki/FLAGS_register)
 * [inline assembler](https://en.wikipedia.org/wiki/Inline_assembler)
 * [gcc](https://en.wikipedia.org/wiki/GNU_Compiler_Collection)

Diff for: Initialization/linux-initialization-10.md

@@ -97,7 +97,7 @@ void arch_task_cache_init(void)
 }
 ```
 
-The `arch_task_cache_init` does initialization of the architecture-specific caches. In our case it is `x86_64`, so as we can see, the `arch_task_cache_init` allocates cache for the `task_xstate` which represents [FPU](http://en.wikipedia.org/wiki/Floating-point_unit) state and sets up offsets and sizes of all extended states in [xsave](http://www.felixcloutier.com/x86/XSAVES.html) area with the call of the `setup_xstate_comp` function. After the `arch_task_cache_init` we calculate default maximum number of threads with the:
+The `arch_task_cache_init` does initialization of the architecture-specific caches. In our case it is `x86_64`, so as we can see, the `arch_task_cache_init` allocates cache for the `task_xstate` which represents [FPU](http://en.wikipedia.org/wiki/Floating-point_unit) state and sets up offsets and sizes of all extended states in [xsave](https://www.felixcloutier.com/x86/XSAVES.html) area with the call of the `setup_xstate_comp` function. After the `arch_task_cache_init` we calculate default maximum number of threads with the:
 
 ```C
 set_max_threads(MAX_THREADS);
@@ -338,7 +338,7 @@ More about it will be in the chapter about scheduler. So for this moment the `st
 wait_for_completion(&kthreadd_done);
 ```
 
-After this we set `gfp_allowed_mask` to `__GFP_BITS_MASK` which means that system is already running, set allowed [cpus/mems](https://www.kernel.org/doc/Documentation/cgroups/cpusets.txt) to all CPUs and [NUMA](http://en.wikipedia.org/wiki/Non-uniform_memory_access) nodes with the `set_mems_allowed` function, allow `init` process to run on any CPU with the `set_cpus_allowed_ptr`, set pid for the `cad` or `Ctrl-Alt-Delete`, do preparation for booting of the other CPUs with the call of the `smp_prepare_cpus`, call early [initcalls](http://kernelnewbies.org/Documents/InitcallMechanism) with the `do_pre_smp_initcalls`, initialize `SMP` with the `smp_init` and initialize [lockup_detector](https://www.kernel.org/doc/Documentation/lockup-watchdogs.txt) with the call of the `lockup_detector_init` and initialize scheduler with the `sched_init_smp`.
+After this we set `gfp_allowed_mask` to `__GFP_BITS_MASK` which means that system is already running, set allowed [cpus/mems](https://www.kernel.org/doc/Documentation/cgroups/cpusets.txt) to all CPUs and [NUMA](http://en.wikipedia.org/wiki/Non-uniform_memory_access) nodes with the `set_mems_allowed` function, allow `init` process to run on any CPU with the `set_cpus_allowed_ptr`, set pid for the `cad` or `Ctrl-Alt-Delete`, do preparation for booting of the other CPUs with the call of the `smp_prepare_cpus`, call early [initcalls](https://kernelnewbies.org/Documents/InitcallMechanism) with the `do_pre_smp_initcalls`, initialize `SMP` with the `smp_init` and initialize [lockup_detector](https://www.kernel.org/doc/Documentation/lockup-watchdogs.txt) with the call of the `lockup_detector_init` and initialize scheduler with the `sched_init_smp`.
 
 After this we can see the call of the following functions - `do_basic_setup`. Before we will call the `do_basic_setup` function, our kernel already initialized for this moment. As comment says:
 
@@ -450,7 +450,7 @@ Links
 --------------------------------------------------------------------------------
 
 * [SLAB](http://en.wikipedia.org/wiki/Slab_allocation)
-* [xsave](http://www.felixcloutier.com/x86/XSAVES.html)
+* [xsave](https://www.felixcloutier.com/x86/XSAVES.html)
 * [FPU](http://en.wikipedia.org/wiki/Floating-point_unit)
 * [Documentation/security/credentials.txt](https://github.com/torvalds/linux/blob/master/Documentation/security/credentials.rst)
 * [Documentation/x86/x86_64/mm](https://github.com/torvalds/linux/blob/16f73eb02d7e1765ccab3d2018e0bd98eb93d973/Documentation/x86/x86_64/mm.txt)

Diff for: Interrupts/linux-interrupts-10.md

@@ -34,7 +34,7 @@ module_exit(serial21285_exit);
         void cleanup_module(void) __attribute__((alias(#exitfn)));
 ```
 
-并被 [initcall](http://kernelnewbies.org/Documents/InitcallMechanism) 函数调用：
+并被 [initcall](https://kernelnewbies.org/Documents/InitcallMechanism) 函数调用：
 
 * `early_initcall`
 * `pure_initcall`
@@ -456,7 +456,7 @@ native_irq_return_iret:
 * [StrongARM** SA-110/21285 评估板](http://netwinder.osuosl.org/pub/netwinder/docs/intel/datashts/27813501.pdf)
 * [IRQ](https://en.wikipedia.org/wiki/Interrupt_request_%28PC_architecture%29)
 * [模块](https://en.wikipedia.org/wiki/Loadable_kernel_module)
-* [initcall](http://kernelnewbies.org/Documents/InitcallMechanism)
+* [initcall](https://kernelnewbies.org/Documents/InitcallMechanism)
 * [uart](https://en.wikipedia.org/wiki/Universal_asynchronous_receiver/transmitter) 
 * [ISA](https://en.wikipedia.org/wiki/Industry_Standard_Architecture) 
 * [内存管理](/MM/)

Diff for: Interrupts/linux-interrupts-3.md

@@ -214,7 +214,7 @@ But unfortunately this method does not give a 100% guarantee. As described in th
 > stack but before we executed SWAPGS, then the only safe way to check
 > for GS is the slower method: the RDMSR.
 
-In other words for example `NMI` could happen inside the critical section of a [swapgs](http://www.felixcloutier.com/x86/SWAPGS.html) instruction. In this way we should check value of the `MSR_GS_BASE` [model specific register](https://en.wikipedia.org/wiki/Model-specific_register) which stores pointer to the start of per-cpu area. So to check if we did come from userspace or not, we should to check value of the `MSR_GS_BASE` model specific register and if it is negative we came from kernel space, in other way we came from userspace:
+In other words for example `NMI` could happen inside the critical section of a [swapgs](https://www.felixcloutier.com/x86/SWAPGS.html) instruction. In this way we should check value of the `MSR_GS_BASE` [model specific register](https://en.wikipedia.org/wiki/Model-specific_register) which stores pointer to the start of per-cpu area. So to check if we did come from userspace or not, we should to check value of the `MSR_GS_BASE` model specific register and if it is negative we came from kernel space, in other way we came from userspace:
 
 ```assembly
 movl $MSR_GS_BASE,%ecx
@@ -351,7 +351,7 @@ testb	$3, CS+8(%rsp)
 jz	.Lerror_kernelspace
 ```
 
-because we may have potentially fault if as described in documentation truncated `%RIP` was reported. Anyway, in both cases the [SWAPGS](http://www.felixcloutier.com/x86/SWAPGS.html) instruction will be executed and values from `MSR_KERNEL_GS_BASE` and `MSR_GS_BASE` will be swapped. From this moment the `%gs` register will point to the base address of kernel structures. So, the `SWAPGS` instruction is called and it was main point of the `error_entry` routing.
+because we may have potentially fault if as described in documentation truncated `%RIP` was reported. Anyway, in both cases the [SWAPGS](https://www.felixcloutier.com/x86/SWAPGS.html) instruction will be executed and values from `MSR_KERNEL_GS_BASE` and `MSR_GS_BASE` will be swapped. From this moment the `%gs` register will point to the base address of kernel structures. So, the `SWAPGS` instruction is called and it was main point of the `error_entry` routing.
 
 Now we can back to the `idtentry` macro. We may see following assembler code after the call of `error_entry`:
 
@@ -515,7 +515,7 @@ Links
 * [CFI directives](https://sourceware.org/binutils/docs/as/CFI-directives.html)
 * [IRQ](http://en.wikipedia.org/wiki/Interrupt_request_%28PC_architecture%29)
 * [system call](http://en.wikipedia.org/wiki/System_call)
-* [swapgs](http://www.felixcloutier.com/x86/SWAPGS.html)
+* [swapgs](https://www.felixcloutier.com/x86/SWAPGS.html)
 * [SIGTRAP](https://en.wikipedia.org/wiki/Unix_signal#SIGTRAP)
 * [Per-CPU variables](https://0xax.gitbook.io/linux-insides/summary/concepts/linux-cpu-1)
 * [kgdb](https://en.wikipedia.org/wiki/KGDB)

Diff for: Interrupts/linux-interrupts-4.md

@@ -150,7 +150,7 @@ if (kmemcheck_active(regs))
 	prefetchw(&mm->mmap_sem);
 ```
 
-After this we can see the call of the `prefetchw` which executes instruction with the same [name](http://www.felixcloutier.com/x86/PREFETCHW.html) which fetches [X86_FEATURE_3DNOW](https://en.wikipedia.org/?title=3DNow!) to get exclusive [cache line](https://en.wikipedia.org/wiki/CPU_cache). The main purpose of prefetching is to hide the latency of a memory access. In the next step we check that we got page fault not in the kernel space with the following condition:
+After this we can see the call of the `prefetchw` which executes instruction with the same [name](https://www.felixcloutier.com/x86/PREFETCHW.html) which fetches [X86_FEATURE_3DNOW](https://en.wikipedia.org/?title=3DNow!) to get exclusive [cache line](https://en.wikipedia.org/wiki/CPU_cache). The main purpose of prefetching is to hide the latency of a memory access. In the next step we check that we got page fault not in the kernel space with the following condition:
 
 ```C
 if (unlikely(fault_in_kernel_space(address))) {
@@ -444,7 +444,7 @@ Links
 * [RCU](https://en.wikipedia.org/wiki/Read-copy-update)
 * [this_cpu_* operations](https://github.com/torvalds/linux/blob/16f73eb02d7e1765ccab3d2018e0bd98eb93d973/Documentation/this_cpu_ops.txt)
 * [kmemcheck](https://www.kernel.org/doc/Documentation/kmemcheck.txt)
-* [prefetchw](http://www.felixcloutier.com/x86/PREFETCHW.html)
+* [prefetchw](https://www.felixcloutier.com/x86/PREFETCHW.html)
 * [3DNow](https://en.wikipedia.org/?title=3DNow!)
 * [CPU caches](https://en.wikipedia.org/wiki/CPU_cache)
 * [VFS](https://en.wikipedia.org/wiki/Virtual_file_system)

Diff for: LINKS.md

@@ -16,7 +16,7 @@ Linux 启动
 ------------------------
 
 * [8250 UART Programming](http://en.wikibooks.org/wiki/Serial_Programming/8250_UART_Programming#UART_Registers)
-* [Serial ports on OSDEV](http://wiki.osdev.org/Serial_Ports)
+* [Serial ports on OSDEV](https://wiki.osdev.org/Serial_Ports)
 
 VGA
 ------------------------

Diff for: Misc/linux-misc-1.md

@@ -485,5 +485,5 @@ Happy Hacking!
 * [Linux kernel mail listing archive](https://lkml.org/)
 * [Linux kernel coding style guide](https://github.com/torvalds/linux/blob/master/Documentation/CodingStyle)
 * [How to Get Your Change Into the Linux Kernel](https://github.com/torvalds/linux/blob/master/Documentation/SubmittingPatches)
-* [Linux Kernel Newbies](http://kernelnewbies.org/)
+* [Linux Kernel Newbies](https://kernelnewbies.org/)
 * [plain text](https://en.wikipedia.org/wiki/Plain_text)

Diff for: Misc/linux-misc-2.md

@@ -676,7 +676,7 @@ Kernel: arch/x86/boot/bzImage is ready  (#5)
 * [uname](https://en.wikipedia.org/wiki/Uname)
 * [shell](https://en.wikipedia.org/wiki/Shell_%28computing%29)
 * [Kbuild](https://github.com/torvalds/linux/blob/master/Documentation/kbuild/kbuild.txt)
-* [binutils](http://www.gnu.org/software/binutils/)
+* [binutils](https://www.gnu.org/software/binutils/)
 * [gcc](https://gcc.gnu.org/)
 * [Documentation](https://github.com/torvalds/linux/blob/master/Documentation/kbuild/makefiles.txt)
 * [System.map](https://en.wikipedia.org/wiki/System.map)

Diff for: Misc/linux-misc-4.md

@@ -119,7 +119,7 @@ $ ./sum
 x + y + z = 6
 ```
 
-好的，直到现在所有事情看起来听挺好。你可能已经知道一个特殊的[系统调用](https://zh.wikipedia.org/wiki/%E7%B3%BB%E7%BB%9F%E8%B0%83%E7%94%A8)家族 - [exec*](http://man7.org/linux/man-pages/man3/execl.3.html) 系统调用。正如我们从帮助手册中读到的：
+好的，直到现在所有事情看起来听挺好。你可能已经知道一个特殊的[系统调用](https://zh.wikipedia.org/wiki/%E7%B3%BB%E7%BB%9F%E8%B0%83%E7%94%A8)家族 - [exec*](https://man7.org/linux/man-pages/man3/execl.3.html) 系统调用。正如我们从帮助手册中读到的：
 
 > The exec() family of functions replaces the current process image with a new process image.
 
@@ -368,7 +368,7 @@ $ readelf -e test | grep fini
   [15] .fini             PROGBITS         0000000000400504  00000504
 ```
 
-这两个将被替换为二进制镜像的开始和结尾，包含分别被称为构造函数和析构函数的例程。这些例程的要点是在程序的真正代码执行之前，做一些初始化/终结，像全局变量如 [errno](http://man7.org/linux/man-pages/man3/errno.3.html) ，为系统例程分配和释放内存等等。
+这两个将被替换为二进制镜像的开始和结尾，包含分别被称为构造函数和析构函数的例程。这些例程的要点是在程序的真正代码执行之前，做一些初始化/终结，像全局变量如 [errno](https://man7.org/linux/man-pages/man3/errno.3.html) ，为系统例程分配和释放内存等等。
 
 你可能可以从这些函数的名字推测，这两个会在 `main` 函数之前和之后被调用。`.init` 和 `.fini` 段的定义在 `/lib64/crti.o` 中。如果我们添加这个目标文件：
 

Diff for: README.md

@@ -41,4 +41,4 @@
 
 ## 许可证
 
-本项目使用 [BY-NC-SA Creative Commons](http://creativecommons.org/licenses/by-nc-sa/4.0/) 许可证。
+本项目使用 [BY-NC-SA Creative Commons](https://creativecommons.org/licenses/by-nc-sa/4.0/) 许可证。

Diff for: Scripts/validate_markdown_links.py

@@ -17,7 +17,7 @@ def check_live_url(url):
 
     result = False
     try:
-        ret = urlopen(url, timeout=2)
+        ret = urlopen(url, timeout=5)
         result = (ret.code == 200)
     except HTTPError as e:
         print(e, file=sys.stderr)
@@ -55,14 +55,14 @@ def main(path):
             print("markdown file name: " + url)
             continue
         if check_live_url(url):
-            print(url)
+            print(url, ": Success")
         else:
-            print(url, file=sys.stderr)
+            print(url, ": Failure")
 
 
 if __name__ == '__main__':
 
     if len(sys.argv) == 2:
         main(sys.argv[1])
     else:
-        print("Choose one path as argument one")
+        print("Choose one path as the argument")