Re: linux-next: build failure after merge of the block tree

Jens Axboe
2025-01-21T14:40:39Z

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@canb.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