linux-kernel - Re: [PATCH] docs: admin-guide/sysctl: escape % symbols

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: <871qvd6fq2.fsf@meer.lwn.net>
Date:   Fri, 24 Jun 2022 13:09:25 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Stephen Kitt <steve@....org>, linux-kernel@...r.kernel.org
Cc:     Stephen Kitt <steve@....org>, linux-doc@...r.kernel.org
Subject: Re: [PATCH] docs: admin-guide/sysctl: escape % symbols

Stephen Kitt <steve@....org> writes:

> % symbols need to be escaped to render correctly here, do so.
>
> Signed-off-by: Stephen Kitt <steve@....org>
> ---
>  Documentation/admin-guide/sysctl/kernel.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index ddccd1077462..079a51ed88a9 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -38,8 +38,8 @@ acct
>  
>  If BSD-style process accounting is enabled these values control
>  its behaviour. If free space on filesystem where the log lives
> -goes below ``lowwater``% accounting suspends. If free space gets
> -above ``highwater``% accounting resumes. ``frequency`` determines
> +goes below ``lowwater``\% accounting suspends. If free space gets
> +above ``highwater``\% accounting resumes. ``frequency`` determines
>  how often do we check the amount of free space (value is in
>  seconds). Default:

Interesting...I had to go digging into why this is, because "%" isn't
really special for RST.  The real problem is that ``literal`` markup
needs to have word separators around it, and the recommended solution is
to use "\ " instead.

So I'll apply this, but tweak the changelog and add the extra spaces.

Thanks,

jon