From: Barry Song <21cnbao@gmail.com>
To: Wale Zhang <wale.zhang.ftd@gmail.com>
Cc: akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
chrisl@kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/1] mm,swapops: Fix compile error on set_pmd_migration_entry.
Date: Thu, 25 Dec 2025 23:22:05 +1300 [thread overview]
Message-ID: <CAGsJ_4yEAOxUmrPvca3Nzc-OB0+xXk5Y5gzszsY5TPqHCGvgcQ@mail.gmail.com> (raw)
In-Reply-To: <20251225094057.286954-1-wale.zhang.ftd@gmail.com>
On Thu, Dec 25, 2025 at 10:41 PM Wale Zhang <wale.zhang.ftd@gmail.com> wrote:
>
> ../include/linux/swapops.h: In function ‘set_pmd_migration_entry’:
> ../include/linux/swapops.h:346:1: error: no return statement in function returning non-void [-Werror=return-type]
> 346 | }
> | ^
> cc1: some warnings being treated as errors
>
> Signed-off-by: Wale Zhang <wale.zhang.ftd@gmail.com>
Sorry. NAK.
This looks odd. We already have a BUILD_BUG(), so no fix is needed.
we should already have:
././include/linux/compiler_types.h:631:45: error: call to
‘__compiletime_assert_907’ declared with attribute error: BUILD_BUG
failed
631 | _compiletime_assert(condition, msg,
__compiletime_assert_, __COUNTER__)
| ^
././include/linux/compiler_types.h:612:25: note: in definition of
macro ‘__compiletime_assert’
612 | prefix ## suffix();
\
| ^~~~~~
Do you actually see this being built? If so, please help identify why it
gets built.
> ---
> include/linux/swapops.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/swapops.h b/include/linux/swapops.h
> index 8cfc966eae48..84eb36d97212 100644
> --- a/include/linux/swapops.h
> +++ b/include/linux/swapops.h
> @@ -343,6 +343,7 @@ static inline int set_pmd_migration_entry(struct page_vma_mapped_walk *pvmw,
> struct page *page)
> {
> BUILD_BUG();
> + return 0;
> }
>
> static inline void remove_migration_pmd(struct page_vma_mapped_walk *pvmw,
> --
> 2.43.0
>
Thanks
Barry
next prev parent reply other threads:[~2025-12-25 10:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 9:40 Wale Zhang
2025-12-25 10:22 ` Barry Song [this message]
2025-12-26 11:45 ` wale zhang
2025-12-26 18:43 ` Barry Song
2025-12-27 7:51 ` wale zhang
2025-12-27 8:16 ` Barry Song
2025-12-27 9:58 ` wale zhang
2025-12-27 11:25 ` Barry Song
2025-12-28 21:37 ` Andrew Morton
2025-12-28 22:07 ` Barry Song
2025-12-29 11:37 ` wale zhang
2025-12-30 5:00 ` Matthew Wilcox
2025-12-30 8:05 ` wale zhang
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=CAGsJ_4yEAOxUmrPvca3Nzc-OB0+xXk5Y5gzszsY5TPqHCGvgcQ@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chrisl@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=wale.zhang.ftd@gmail.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