mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Suren Baghdasaryan <surenb@google.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the mm tree
Date: Mon, 25 Mar 2024 22:44:06 -0700	[thread overview]
Message-ID: <5e1321ca-0d46-4e9d-a6e5-0560d99f65ff@infradead.org> (raw)
In-Reply-To: <CAJuCfpH4Ee00hM9+B7=mi5Dwjrhov8vUK-KwPuoO3wsD7iJSAQ@mail.gmail.com>



On 3/25/24 19:19, Suren Baghdasaryan wrote:
> On Sun, Mar 24, 2024 at 6:36 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Hi all,
>>
>> After merging the mm tree, today's linux-next build (htmldocs) produced
>> these warnings:
>>
>> include/linux/slab.h:545: warning: expecting prototype for kmem_cache_alloc(). Prototype was for kmem_cache_alloc_noprof() instead
>> include/linux/slab.h:652: warning: expecting prototype for kmalloc(). Prototype was for kmalloc_noprof() instead
>> include/linux/slab.h:692: warning: expecting prototype for kmalloc_array(). Prototype was for kmalloc_array_noprof() instead
>> include/linux/slab.h:714: warning: expecting prototype for krealloc_array(). Prototype was for krealloc_array_noprof() instead
>> include/linux/slab.h:730: warning: Function parameter or struct member '_n' not described in 'kcalloc'
>> include/linux/slab.h:730: warning: Function parameter or struct member '_size' not described in 'kcalloc'
>> include/linux/slab.h:730: warning: Function parameter or struct member '_flags' not described in 'kcalloc'
>> include/linux/slab.h:730: warning: Excess function parameter 'n' description in 'kcalloc'
>> include/linux/slab.h:730: warning: Excess function parameter 'size' description in 'kcalloc'
>> include/linux/slab.h:730: warning: Excess function parameter 'flags' description in 'kcalloc'
>> include/linux/slab.h:774: warning: expecting prototype for kzalloc(). Prototype was for kzalloc_noprof() instead
>> mm/slab_common.c:1217: warning: expecting prototype for krealloc(). Prototype was for krealloc_noprof() instead
>> mm/util.c:751: warning: expecting prototype for __vcalloc(). Prototype was for __vcalloc_noprof() instead
>> mm/vmalloc.c:3897: warning: expecting prototype for vmalloc(). Prototype was for vmalloc_noprof() instead
>> mm/vmalloc.c:3916: warning: expecting prototype for vmalloc_huge(). Prototype was for vmalloc_huge_noprof() instead
>> mm/vmalloc.c:3953: warning: expecting prototype for vmalloc_user(). Prototype was for vmalloc_user_noprof() instead
>> mm/mempool.c:245: warning: expecting prototype for mempool_init(). Prototype was for mempool_init_noprof() instead
>> mm/mempool.c:271: warning: Function parameter or struct member 'gfp_mask' not described in 'mempool_create_node_noprof'
>> mm/mempool.c:271: warning: Function parameter or struct member 'node_id' not described in 'mempool_create_node_noprof'
>> mm/mempool.c:271: warning: expecting prototype for mempool_create_node(). Prototype was for mempool_create_node_noprof() instead
>>
>> Introduced by commits
>>
>>   c64e38ed88d1 ("mm/slab: enable slab allocation tagging for kmalloc and friends")
>>   ea7b8933f21b ("mempool: hook up to memory allocation profiling")
>>   576477564ede ("mm: vmalloc: enable memory allocation profiling")
>>
>> from the mm-unstable branch of the mm tree.
> 
> Thanks for the report, Stephen!
> Let us check with Randy Dunlap how we should handle these. I assume we
> still want documentation to document kmalloc(), not kmalloc_noprof().
> Maybe there is a way to mute these warnings.

A proposed patch is here:
  https://lore.kernel.org/lkml/20240326054149.2121-1-rdunlap@infradead.org/T/#u


-- 
#Randy

  reply	other threads:[~2024-03-26  5:44 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25  1:36 Stephen Rothwell
2024-03-26  2:19 ` Suren Baghdasaryan
2024-03-26  5:44   ` Randy Dunlap [this message]
2024-03-26  6:16     ` Suren Baghdasaryan
2024-03-28  4:39       ` Stephen Rothwell
2024-03-28  4:44         ` Stephen Rothwell
2024-03-28  5:35           ` Suren Baghdasaryan
2024-03-29 22:49             ` Stephen Rothwell
2024-03-29 23:01               ` Suren Baghdasaryan
2024-03-29 23:01                 ` Suren Baghdasaryan
  -- strict thread matches above, loose matches on Subject: below --
2025-03-05  9:42 Stephen Rothwell
2025-03-05  9:53 ` David Hildenbrand
2025-03-05 10:05   ` David Hildenbrand
2025-02-17  6:10 Stephen Rothwell
2025-02-17 16:28 ` Suren Baghdasaryan
2025-02-10  3:49 Stephen Rothwell
2025-02-09 23:06 Stephen Rothwell
2025-01-06  6:42 Stephen Rothwell
2024-09-11 10:21 Stephen Rothwell
2024-07-01  8:49 Stephen Rothwell
2024-07-02  3:14 ` Andrew Morton
2024-07-02  4:15   ` Jiaqi Yan
2024-07-02  4:33     ` Jiaqi Yan
2024-07-02  6:18       ` Andrew Morton
2024-07-02  6:37         ` Jiaqi Yan
2024-07-02 23:09           ` SeongJae Park
2024-07-02 23:55             ` Jiaqi Yan
2024-07-01  1:01 Stephen Rothwell
2024-07-01  1:13 ` Andrii Nakryiko
2024-07-01  8:28 ` Stephen Rothwell
2024-02-21  5:27 Stephen Rothwell
2024-02-21 17:12 ` SeongJae Park
2023-07-27  4:28 Stephen Rothwell
2023-07-27  4:46 ` Aneesh Kumar K.V
2023-07-27  5:00   ` Stephen Rothwell
2023-05-08  4:54 Stephen Rothwell
2023-05-08 16:10 ` Liam R. Howlett
2022-11-22  6:50 Stephen Rothwell
2022-08-23  3:54 Stephen Rothwell
2022-08-23 14:55 ` Liam Howlett
2022-05-11 10:20 Stephen Rothwell
2022-05-11 16:06 ` Johannes Weiner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5e1321ca-0d46-4e9d-a6e5-0560d99f65ff@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=surenb@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®