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]

Date:   Thu, 15 Sep 2016 14:00:55 +0200
From:   Michael Opdenacker <michael.opdenacker@...e-electrons.com>
To:     paulmck@...ux.vnet.ibm.com,
        Richard Weinberger <richard.weinberger@...il.com>
Cc:     Jonathan Corbet <corbet@....net>,
        Josh Triplett <josh@...htriplett.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        mathieu.desnoyers@...icios.com, jiangshanlai@...il.com,
        LKML <linux-kernel@...r.kernel.org>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        Michael Opdenacker <michael.opdenacker@...e-electrons.com>
Subject: Re: [PATCH] documentation: fix broken lkml archive links in RCU
 requirements

Richard, Paul,

Thank you for your replies!

On 09/09/2016 16:33, Paul E. McKenney wrote:
> On Fri, Sep 09, 2016 at 04:17:14PM +0200, Richard Weinberger wrote:
> Please don't add lkml.org. It does not use message ids for indexing.
> With knowing the message id you can query any other archive.
> e.g. http://marc.info/?i=20100319013024.GA28456@Krystal
> By adding lkml.org you kill that information. Archives come and go,
> the message id is the only common query id we have.
>
> IMHO kernel.org admins should fix/improve their redirection service to
> point to a working service.
> There has been some instability in the kernel.org redirection.  Right
> now, the /r/ services seems to work, though as noted the /g/ does not.
> Please report this to the Kernel.org administrators:
>
> 	https://kernel.org/category/contact-us.html
>
> 							Thanx, Paul

Done. I reported this issue to them and will keep an eye on it. I 
definitely agree that we shouldn't use the message ids. Otherwise, 
that's really a lot of detective work to find out which message was 
referred to. That's very good advise.

Thanks,

Michael.

-- 
Michael Opdenacker, CEO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com