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

2016-09-15 Thread Paul E. McKenney 
On Thu, Sep 15, 2016 at 09:18:28AM -0400, Steven Rostedt wrote:
> On Thu, 15 Sep 2016 14:17:06 +0200
> Michael Opdenacker  wrote:
> 
> > Fix 4 LKML archive links that became broken
> > (issue with https://lkml.kernel.org/g/ redirection links)
> > 
> > Signed-off-by: Michael Opdenacker 
> > ---
> >  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
> >  http://elinux.org/Linux_Tiny-FAQ;>bloatwatch
> >  efforts, memory footprint is critically important on single-CPU systems 
> > with
> >  non-preemptible (CONFIG_PREEMPT=n) kernels, and thus
> > - > href="https://lkml.kernel.org/g/20090113221724.ga15...@linux.vnet.ibm.com;>tiny
> >  RCU
> > + > href="https://lkml.kernel.org/r/20090113221724.ga15...@linux.vnet.ibm.com;>tiny
> >  RCU
> >  was born.
> >  Josh Triplett has since taken over the small-memory banner with his
> >  https://tiny.wiki.kernel.org/;>Linux kernel tinification
> > @@ -1975,7 +1975,7 @@ guard against mishaps and misuse:
> > and cleaned up with destroy_rcu_head().
> > Mathieu Desnoyers made me aware of this requirement, and also
> > supplied the needed
> > -> href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal;>patch.
> > +> href="https://lkml.kernel.org/r/20100319013024.GA28456@Krystal;>patch.
> > An infinite loop in an RCU read-side critical section will
> > eventually trigger an RCU CPU stall warning splat, with
> > the duration of eventually being controlled by the
> > @@ -2088,7 +2088,7 @@ be hidden behind a CONFIG_RCU_EXPERT 
> > Kconfig option.
> >  
> >  This all should be quite obvious, but the fact remains that
> >  Linus Torvalds recently had to
> > - > href="https://lkml.kernel.org/g/ca+55afy4wccwal4okts8wxhgz5h-ibecy_meg9c4mnqrunw...@mail.gmail.com;>remind
> > + > href="https://lkml.kernel.org/r/ca+55afy4wccwal4okts8wxhgz5h-ibecy_meg9c4mnqrunw...@mail.gmail.com;>remind
> >  me of this requirement.
> >  
> >  Firmware Interface
> > @@ -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
> > - > href="https://lkml.kernel.org/g/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anb...@mail.gmail.com;>surprised
> >  me
> > + > href="https://lkml.kernel.org/r/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anb...@mail.gmail.com;>surprised
> >  me
> >  with this requirement;
> >  he also kindly surprised me with
> >   > href="https://lkml.kernel.org/g/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g...@mail.gmail.com;>an
> >  algorithm
> 
> Strange that this one still works. Anyway...
> 
> 
> Acked-by: Steven Rostedt 

So we are confident that these links won't be fixed by the next merge
window?

Thanx, Paul

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

2016-09-15 Thread Steven Rostedt 
On Thu, 15 Sep 2016 14:17:06 +0200
Michael Opdenacker  wrote:

> Fix 4 LKML archive links that became broken
> (issue with https://lkml.kernel.org/g/ redirection links)
> 
> Signed-off-by: Michael Opdenacker 
> ---
>  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
>  http://elinux.org/Linux_Tiny-FAQ;>bloatwatch
>  efforts, memory footprint is critically important on single-CPU systems with
>  non-preemptible (CONFIG_PREEMPT=n) kernels, and thus
> - href="https://lkml.kernel.org/g/20090113221724.ga15...@linux.vnet.ibm.com;>tiny
>  RCU
> + href="https://lkml.kernel.org/r/20090113221724.ga15...@linux.vnet.ibm.com;>tiny
>  RCU
>  was born.
>  Josh Triplett has since taken over the small-memory banner with his
>  https://tiny.wiki.kernel.org/;>Linux kernel tinification
> @@ -1975,7 +1975,7 @@ guard against mishaps and misuse:
>   and cleaned up with destroy_rcu_head().
>   Mathieu Desnoyers made me aware of this requirement, and also
>   supplied the needed
> -  href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal;>patch.
> +  href="https://lkml.kernel.org/r/20100319013024.GA28456@Krystal;>patch.
>   An infinite loop in an RCU read-side critical section will
>   eventually trigger an RCU CPU stall warning splat, with
>   the duration of eventually being controlled by the
> @@ -2088,7 +2088,7 @@ be hidden behind a CONFIG_RCU_EXPERT 
> Kconfig option.
>  
>  This all should be quite obvious, but the fact remains that
>  Linus Torvalds recently had to
> - href="https://lkml.kernel.org/g/ca+55afy4wccwal4okts8wxhgz5h-ibecy_meg9c4mnqrunw...@mail.gmail.com;>remind
> + href="https://lkml.kernel.org/r/ca+55afy4wccwal4okts8wxhgz5h-ibecy_meg9c4mnqrunw...@mail.gmail.com;>remind
>  me of this requirement.
>  
>  Firmware Interface
> @@ -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
> - href="https://lkml.kernel.org/g/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anb...@mail.gmail.com;>surprised
>  me
> + href="https://lkml.kernel.org/r/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anb...@mail.gmail.com;>surprised
>  me
>  with this requirement;
>  he also kindly surprised me with
>   href="https://lkml.kernel.org/g/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g...@mail.gmail.com;>an
>  algorithm

Strange that this one still works. Anyway...


Acked-by: Steven Rostedt 

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

2016-09-15 Thread Michael Opdenacker 

Hi Steve,

On 09/09/2016 16:34, Steven Rostedt wrote:

Correct, we avoid any links to lkml.org at all costs. Simple do a

s,/g/,/r/, and all your links should work. For example, using the above
mentioned link:

  https://lkml.kernel.org/r/20100319013024.GA28456@Krystal

Works as expected.


I confirm that all the links work indeed. I'm sending a patch update 
right away.


Thanks!

Michael.

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

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

2016-09-15 Thread Michael Opdenacker 

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

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

2016-09-09 Thread Steven Rostedt 
On Fri, 9 Sep 2016 16:17:14 +0200
Richard Weinberger  wrote:

> > Signed-off-by: Michael Opdenacker 
> > ---
> >  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..2adb3d43ce44 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
> >  http://elinux.org/Linux_Tiny-FAQ;>bloatwatch
> >  efforts, memory footprint is critically important on single-CPU systems 
> > with
> >  non-preemptible (CONFIG_PREEMPT=n) kernels, and thus
> > - > href="https://lkml.kernel.org/g/20090113221724.ga15...@linux.vnet.ibm.com;>tiny
> >  RCU
> > +http://lkml.org/lkml/2009/1/14/449;>tiny RCU
> >  was born.
> >  Josh Triplett has since taken over the small-memory banner with his
> >  https://tiny.wiki.kernel.org/;>Linux kernel tinification
> > @@ -1975,7 +1975,7 @@ guard against mishaps and misuse:
> > and cleaned up with destroy_rcu_head().
> > Mathieu Desnoyers made me aware of this requirement, and also
> > supplied the needed
> > -> href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal;>patch.
> > +   https://lkml.org/lkml/2010/3/18/417;>patch.  
> 
> 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.
> 

Correct, we avoid any links to lkml.org at all costs. Simple do a

s,/g/,/r/, and all your links should work. For example, using the above
mentioned link:

 https://lkml.kernel.org/r/20100319013024.GA28456@Krystal

Works as expected.

-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

2016-09-09 Thread Paul E. McKenney 
On Fri, Sep 09, 2016 at 04:17:14PM +0200, Richard Weinberger wrote:
> Michael,
> 
> On Fri, Sep 9, 2016 at 3:43 PM, Michael Opdenacker
>  wrote:
> > Fix 4 LKML archive links that became broken (data loss
> > on mail-archive.com?)
> >
> > Working links were found on Paul McKenney's RCU articles
> > on LWN.net, from which the documentation originates:
> > http://lwn.net/Articles/652156/
> > http://lwn.net/Articles/652677/
> > http://lwn.net/Articles/653326/
> >
> > Signed-off-by: Michael Opdenacker 
> > ---
> >  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..2adb3d43ce44 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
> >  http://elinux.org/Linux_Tiny-FAQ;>bloatwatch
> >  efforts, memory footprint is critically important on single-CPU systems 
> > with
> >  non-preemptible (CONFIG_PREEMPT=n) kernels, and thus
> > - > href="https://lkml.kernel.org/g/20090113221724.ga15...@linux.vnet.ibm.com;>tiny
> >  RCU
> > +http://lkml.org/lkml/2009/1/14/449;>tiny RCU
> >  was born.
> >  Josh Triplett has since taken over the small-memory banner with his
> >  https://tiny.wiki.kernel.org/;>Linux kernel tinification
> > @@ -1975,7 +1975,7 @@ guard against mishaps and misuse:
> > and cleaned up with destroy_rcu_head().
> > Mathieu Desnoyers made me aware of this requirement, and also
> > supplied the needed
> > -> href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal;>patch.
> > +   https://lkml.org/lkml/2010/3/18/417;>patch.
> 
> 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

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

2016-09-09 Thread Richard Weinberger 
Michael,

On Fri, Sep 9, 2016 at 3:43 PM, Michael Opdenacker
 wrote:
> Fix 4 LKML archive links that became broken (data loss
> on mail-archive.com?)
>
> Working links were found on Paul McKenney's RCU articles
> on LWN.net, from which the documentation originates:
> http://lwn.net/Articles/652156/
> http://lwn.net/Articles/652677/
> http://lwn.net/Articles/653326/
>
> Signed-off-by: Michael Opdenacker 
> ---
>  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..2adb3d43ce44 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
>  http://elinux.org/Linux_Tiny-FAQ;>bloatwatch
>  efforts, memory footprint is critically important on single-CPU systems with
>  non-preemptible (CONFIG_PREEMPT=n) kernels, and thus
> - href="https://lkml.kernel.org/g/20090113221724.ga15...@linux.vnet.ibm.com;>tiny
>  RCU
> +http://lkml.org/lkml/2009/1/14/449;>tiny RCU
>  was born.
>  Josh Triplett has since taken over the small-memory banner with his
>  https://tiny.wiki.kernel.org/;>Linux kernel tinification
> @@ -1975,7 +1975,7 @@ guard against mishaps and misuse:
> and cleaned up with destroy_rcu_head().
> Mathieu Desnoyers made me aware of this requirement, and also
> supplied the needed
> -href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal;>patch.
> +   https://lkml.org/lkml/2010/3/18/417;>patch.

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.

-- 
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] documentation: fix broken lkml archive links in RCU requirements

2016-09-09 Thread Michael Opdenacker 
Fix 4 LKML archive links that became broken (data loss
on mail-archive.com?)

Working links were found on Paul McKenney's RCU articles
on LWN.net, from which the documentation originates:
http://lwn.net/Articles/652156/
http://lwn.net/Articles/652677/
http://lwn.net/Articles/653326/

Signed-off-by: Michael Opdenacker 
---
 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..2adb3d43ce44 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
 http://elinux.org/Linux_Tiny-FAQ;>bloatwatch
 efforts, memory footprint is critically important on single-CPU systems with
 non-preemptible (CONFIG_PREEMPT=n) kernels, and thus
-https://lkml.kernel.org/g/20090113221724.ga15...@linux.vnet.ibm.com;>tiny 
RCU
+http://lkml.org/lkml/2009/1/14/449;>tiny RCU
 was born.
 Josh Triplett has since taken over the small-memory banner with his
 https://tiny.wiki.kernel.org/;>Linux kernel tinification
@@ -1975,7 +1975,7 @@ guard against mishaps and misuse:
and cleaned up with destroy_rcu_head().
Mathieu Desnoyers made me aware of this requirement, and also
supplied the needed
-   https://lkml.kernel.org/g/20100319013024.GA28456@Krystal;>patch.
+   https://lkml.org/lkml/2010/3/18/417;>patch.
An infinite loop in an RCU read-side critical section will
eventually trigger an RCU CPU stall warning splat, with
the duration of eventually being controlled by the
@@ -2088,7 +2088,7 @@ be hidden behind a CONFIG_RCU_EXPERT 
Kconfig option.
 
 This all should be quite obvious, but the fact remains that
 Linus Torvalds recently had to
-https://lkml.kernel.org/g/ca+55afy4wccwal4okts8wxhgz5h-ibecy_meg9c4mnqrunw...@mail.gmail.com;>remind
+https://lkml.org/lkml/2015/4/14/616;>remind
 me of this requirement.
 
 Firmware Interface
@@ -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
-https://lkml.kernel.org/g/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anb...@mail.gmail.com;>surprised
 me
+https://lkml.org/lkml/2014/11/21/642;>surprised me
 with this requirement;
 he also kindly surprised me with
 https://lkml.kernel.org/g/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g...@mail.gmail.com;>an
 algorithm
-- 
2.7.4

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html