From: Chuck Lever <chuck.lever@oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: shrink_folio_list() does not compile on late-model kernels
Date: Tue, 8 Apr 2025 16:25:45 -0400 [thread overview]
Message-ID: <40a307cf-74ef-4461-93d6-89b1732f4963@oracle.com> (raw)
In-Reply-To: <Z_WFMPkLhHCJFxgB@casper.infradead.org>
On 4/8/25 4:21 PM, Matthew Wilcox wrote:
> On Tue, Apr 08, 2025 at 03:21:21PM -0400, Chuck Lever wrote:
>> Hi-
>>
>> Some of my CI runs have started failing to build v6.13+ kernels with:
>>
>> mm/vmscan.c: In function ‘shrink_folio_list’:
>> mm/vmscan.c:1082:21: error: implicit declaration of function
>> ‘folio_contain_hwpoisoned_page’ [-Wimplicit-function-declaration]
>> 1082 | if (folio_contain_hwpoisoned_page(folio)) {
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> make[3]: *** [scripts/Makefile.build:196: mm/vmscan.o] Error 1
>> make[2]: *** [scripts/Makefile.build:442: mm] Error 2
>> make[2]: *** Waiting for unfinished jobs....
>> make[1]: *** [/data/linux-stable-rc/Makefile:1989: .] Error 2
>> make: *** [Makefile:251: __sub-make] Error 2
>>
>> Is there a .config change I need to prevent this failure?
>
> I don't see why folio_contain_hwpoisoned_page() wouldn't be declared.
> Could you include your .config?
I assumed linux-mm would bounce an attachment. But it turns out I have a
sample .config in a public git repo:
https://github.com/chucklever/kdevops/blob/queue-6-13/playbooks/roles/bootlinux/templates/config-kdevops
The failure seems to be intermittent.
--
Chuck Lever
next prev parent reply other threads:[~2025-04-08 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 19:21 Chuck Lever
2025-04-08 20:21 ` Matthew Wilcox
2025-04-08 20:25 ` Chuck Lever [this message]
2025-04-14 17:40 ` Chuck Lever
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=40a307cf-74ef-4461-93d6-89b1732f4963@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
/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