linux-kernel - Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160915091828.4ae347e9@gandalf.local.home>
Date:   Thu, 15 Sep 2016 09:18:28 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Michael Opdenacker <michael.opdenacker@...e-electrons.com>
Cc:     corbet@....net, paulmck@...ux.vnet.ibm.com, josh@...htriplett.org,
        mathieu.desnoyers@...icios.com, jiangshanlai@...il.com,
        linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH] documentation: fix broken lkml archive links in RCU
 requirements

On Thu, 15 Sep 2016 14:17:06 +0200
Michael Opdenacker <michael.opdenacker@...e-electrons.com> wrote:

> Fix 4 LKML archive links that became broken
> (issue with https://lkml.kernel.org/g/ redirection links)
> 
> Signed-off-by: Michael Opdenacker <michael.opdenacker@...e-electrons.com>
> ---
>  Documentation/RCU/Design/Requirements/Requirements.html | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html
> index ece410f40436..1c39a2362911 100644
> --- a/Documentation/RCU/Design/Requirements/Requirements.html
> +++ b/Documentation/RCU/Design/Requirements/Requirements.html
> @@ -1527,7 +1527,7 @@ However, as I learned from Matt Mackall's
>  <a href="http://elinux.org/Linux_Tiny-FAQ">bloatwatch</a>
>  efforts, memory footprint is critically important on single-CPU systems with
>  non-preemptible (<tt>CONFIG_PREEMPT=n</tt>) kernels, and thus
> -<a href="https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a>
> +<a href="https://lkml.kernel.org/r/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a>
>  was born.
>  Josh Triplett has since taken over the small-memory banner with his
>  <a href="https://tiny.wiki.kernel.org/">Linux kernel tinification</a>
> @@ -1975,7 +1975,7 @@ guard against mishaps and misuse:
>  	and cleaned up with <tt>destroy_rcu_head()</tt>.
>  	Mathieu Desnoyers made me aware of this requirement, and also
>  	supplied the needed
> -	<a href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal">patch</a>.
> +	<a href="https://lkml.kernel.org/r/20100319013024.GA28456@Krystal">patch</a>.
>  <li>	An infinite loop in an RCU read-side critical section will
>  	eventually trigger an RCU CPU stall warning splat, with
>  	the duration of &ldquo;eventually&rdquo; being controlled by the
> @@ -2088,7 +2088,7 @@ be hidden behind a <tt>CONFIG_RCU_EXPERT</tt> <tt>Kconfig</tt> option.
>  <p>
>  This all should be quite obvious, but the fact remains that
>  Linus Torvalds recently had to
> -<a href="https://lkml.kernel.org/g/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">remind</a>
> +<a href="https://lkml.kernel.org/r/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">remind</a>
>  me of this requirement.
>  
>  <h3><a name="Firmware Interface">Firmware Interface</a></h3>
> @@ -2229,7 +2229,7 @@ Thankfully, RCU update-side primitives, including
>  The name notwithstanding, some Linux-kernel architectures
>  can have nested NMIs, which RCU must handle correctly.
>  Andy Lutomirski
> -<a href="https://lkml.kernel.org/g/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">surprised me</a>
> +<a href="https://lkml.kernel.org/r/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">surprised me</a>
>  with this requirement;
>  he also kindly surprised me with
>  <a href="https://lkml.kernel.org/g/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g@mail.gmail.com">an algorithm</a>

Strange that this one still works. Anyway...


Acked-by: Steven Rostedt <rostedt@...dmis.org>

-- Steve