linux-kernel - Re: linux-next: build failure after merge of the block 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: <48d04a52-8f84-44c3-bf14-95fe9a3e9e06@kernel.dk>
Date: Tue, 21 Jan 2025 07:40:36 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Luiz Capitulino <luizcap@...hat.com>,
 Stephen Rothwell <sfr@...b.auug.org.au>,
 Andrew Morton <akpm@...ux-foundation.org>
Cc: Pavel Begunkov <asml.silence@...il.com>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the block tree

On 1/21/25 6:57 AM, Luiz Capitulino wrote:
> On 2025-01-21 02:39, Stephen Rothwell wrote:
>> Hi all,
>>
>> On Fri, 10 Jan 2025 12:44:06 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>>
>>> After merging the block tree, today's linux-next build (powerpc
>>> ppc64_defconfig) failed like this:
>>>
>>> io_uring/memmap.c: In function 'io_region_allocate_pages':
>>> io_uring/memmap.c:173:24: error: implicit declaration of function 'alloc_pages_bulk_array_node'; did you mean 'alloc_pages_bulk_node'? [-Wimplicit-function-declaration]
>>>    173 |         nr_allocated = alloc_pages_bulk_array_node(gfp, NUMA_NO_NODE,
>>>        |                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>        |                        alloc_pages_bulk_node
>>>
>>> Caused by commit
>>>
>>>    1e21df691ffa ("io_uring/memmap: implement kernel allocated regions")
>>
>> That commit is now in Linus' tree.
>>
>>> interacting with commit
>>>
>>>    4f6a90a13f78 ("mm: alloc_pages_bulk: rename API")
>>
>> That is now commit
>>
>>    8c3cbdcf4d82 ("mm: alloc_pages_bulk: rename API")
>>
>> in the mm-stable tree.
> 
> Should I resend against latest Linus tree? I thought we were going with
> your fixup...

As long as it gets mentioned when the pull request goes out, Linus is
usually quite happy to just fix it up while merging.

-- 
Jens Axboe