linux-kernel - Re: linux-next: build warning after merge of the mm-hotfixes 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <3084e97c-3a7d-ace8-2e9c-31642fd663df@google.com>
Date:   Mon, 24 Jul 2023 21:10:59 -0700 (PDT)
From:   Hugh Dickins <hughd@...gle.com>
To:     Randy Dunlap <rdunlap@...radead.org>
cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Hugh Dickins <hughd@...gle.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the mm-hotfixes tree

On Tue, 25 Jul 2023, Stephen Rothwell wrote:

> Hi all,
> 
> After merging the mm-hotfixes tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> Documentation/filesystems/tmpfs.rst:116: ERROR: Malformed table.
> Text in column margin in table line 4.
> 
> ===========  ==============================================================
> huge=never   Do not allocate huge pages.  This is the default.
> huge=always  Attempt to allocate huge page every time a new page is needed.
> huge=within_size Only allocate huge page if it will be fully within i_size.
>              Also respect madvise(2) hints.
> huge=advise  Only allocate huge page if requested with madvise(2).
> ===========  ==============================================================
> 
> Introduced by commit
> 
>   a0ebb5aa2de3 ("tmpfs: fix Documentation of noswap and huge mount options")

Sorry about that, Stephen: thanks for the report.

Randy, you're always my goto guy for how to get these Doc things right,
I hope you don't mind.  I just write the text as I want it to appear,
then get caught out by unfamiliar rules.

Please suggest a fixup to the fix patch if you can - thanks!

Hugh