linux-kernel - Re: linux-next: build warnings after merge of the rcu tree

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] [day] [month] [year] [list]

Message-ID: <20221123142722.GV4001@paulmck-ThinkPad-P17-Gen-1>
Date:   Wed, 23 Nov 2022 06:27:22 -0800
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     "Leizhen (ThunderTown)" <thunder.leizhen@...wei.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the rcu tree

On Wed, Nov 23, 2022 at 04:19:15PM +0800, Leizhen (ThunderTown) wrote:
> 
> 
> On 2022/11/23 13:32, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the rcu tree, today's linux-next build (htmldocs) produced
> > these warnings:
> > 
> > Documentation/RCU/stallwarn.rst:401: WARNING: Literal block expected; none found.
> > Documentation/RCU/stallwarn.rst:428: WARNING: Literal block expected; none found.
> > Documentation/RCU/stallwarn.rst:445: WARNING: Literal block expected; none found.
> > Documentation/RCU/stallwarn.rst:459: WARNING: Literal block expected; none found.
> > Documentation/RCU/stallwarn.rst:468: WARNING: Literal block expected; none found.
> > 
> > Introduced by commit
> > 
> >   3d2788ba4573 ("doc: Document CONFIG_RCU_CPU_STALL_CPUTIME=y stall information")
> > 
> 
> Strange thing, I specially executed make htmldocs before, unexpectedly did not
> find these warnings.
> 
> I already know why. The literal block is not indented. I will post a new version to
> Paul E. McKenney. Excuse me for causing trouble to everyone.
> 
> For example:
> @@ -398,9 +398,9 @@ In kernels built with CONFIG_RCU_CPU_STALL_CPUTIME=y or booted with
>  rcupdate.rcu_cpu_stall_cputime=1, the following additional information
>  is supplied with each RCU CPU stall warning::
> 
> -rcu:          hardirqs   softirqs   csw/system
> -rcu:  number:      624         45            0
> -rcu: cputime:       69          1         2425   ==> 2500(ms)
> +  rcu:          hardirqs   softirqs   csw/system
> +  rcu:  number:      624         45            0
> +  rcu: cputime:       69          1         2425   ==> 2500(ms)

It is probably my fault during my wordsmithing, but I will happily
accept a new patch to replace the current one.

							Thanx, Paul