linux-kernel - Re: linux-next: build warnings after merge of the mm 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <787bc86c-b49e-4120-9eb3-0c5e0156a5eb@redhat.com>
Date: Wed, 5 Mar 2025 11:05:54 +0100
From: David Hildenbrand <david@...hat.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
 Andrew Morton <akpm@...ux-foundation.org>
Cc: 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 mm tree

On 05.03.25 10:53, David Hildenbrand wrote:
> On 05.03.25 10:42, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the mm tree, today's linux-next build (htmldocs) produced
>> these warnings:
>>
>> include/linux/mm_types.h:482: warning: Function parameter or struct member '_usable_1' not described in 'folio'
>> include/linux/mm_types.h:482: warning: Function parameter or struct member '_mapcount_1' not described in 'folio'
>> include/linux/mm_types.h:482: warning: Function parameter or struct member '_refcount_1' not described in 'folio'
>>
>> Introduced by commit
>>
>>     bbde3b621cf7 ("mm: let _folio_nr_pages overlay memcg_data in first tail page")
>>
>> from the mm-unstable branch of the mm tree.
> 
> Hm, we also don't document other dummy placeholders like:
> 
> * _flags_1
> * _head_1
> * __page_1
> 
> So I assume there must be one way to silence these warnings, let me dig ...

Ah, likely because they are part of the "private:" section.

-- 
Cheers,

David / dhildenb