linux-kernel - Re: [PATCH] locking/qspinlock: Fix inaccessible URL of MCS lock paper

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: <20200107125824.GA2844@hirez.programming.kicks-ass.net>
Date:   Tue, 7 Jan 2020 13:58:24 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Waiman Long <longman@...hat.com>
Cc:     Ingo Molnar <mingo@...hat.com>, Will Deacon <will.deacon@....com>,
        linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Subject: Re: [PATCH] locking/qspinlock: Fix inaccessible URL of MCS lock paper

On Sun, Dec 22, 2019 at 09:25:32PM -0500, Waiman Long wrote:
> It turns out that the URL of the MCS lock paper listed in the source
> code is no longer accessible. I did got question about where the paper
> was. This patch updates the URL to one that is still accessible.
> 
> Signed-off-by: Waiman Long <longman@...hat.com>
> ---
>  kernel/locking/qspinlock.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c
> index 2473f10c6956..1d008d2333c0 100644
> --- a/kernel/locking/qspinlock.c
> +++ b/kernel/locking/qspinlock.c
> @@ -34,7 +34,7 @@
>   * MCS lock. The paper below provides a good description for this kind
>   * of lock.
>   *
> - * http://www.cise.ufl.edu/tr/DOC/REP-1992-71.pdf
> + * https://www.cs.rochester.edu/u/scott/papers/1991_TOCS_synch.pdf

Do we want to stick a copy of the paper in our bugzilla and link that
instead? ISTR we do something similar elsewhere, but I'm having trouble
finding it.

Thomas, Konstantin?