From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752011AbcIOOtn (ORCPT ); Thu, 15 Sep 2016 10:49:43 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:52034 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751025AbcIOOtd (ORCPT ); Thu, 15 Sep 2016 10:49:33 -0400 X-IBM-Helo: d03dlp02.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com Date: Thu, 15 Sep 2016 07:49:26 -0700 From: "Paul E. McKenney" To: Steven Rostedt Cc: Michael Opdenacker , corbet@lwn.net, josh@joshtriplett.org, mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements Reply-To: paulmck@linux.vnet.ibm.com References: <1473941826-11518-1-git-send-email-michael.opdenacker@free-electrons.com> <20160915091828.4ae347e9@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160915091828.4ae347e9@gandalf.local.home> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16091514-0008-0000-0000-0000059107C1 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00005765; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000185; SDB=6.00757981; UDB=6.00359640; IPR=6.00531596; BA=6.00004731; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00012682; XFM=3.00000011; UTC=2016-09-15 14:49:30 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16091514-0009-0000-0000-00003B351277 Message-Id: <20160915144926.GD10850@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-09-15_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609020000 definitions=main-1609150199 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > bloatwatch > > efforts, memory footprint is critically important on single-CPU systems with > > non-preemptible (CONFIG_PREEMPT=n) kernels, and thus > > -tiny RCU > > +tiny RCU > > was born. > > Josh Triplett has since taken over the small-memory banner with his > > 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 > > - patch. > > + 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 > > -remind > > +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 > > -surprised me > > +surprised me > > with this requirement; > > he also kindly surprised me with > > 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