From: Andrew Morton <akpm@linux-foundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"David Hildenbrand (Red Hat)" <david@kernel.org>,
Ankur Arora <ankur.a.arora@oracle.com>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH v2] m68k: Avoid -Wunused-but-set-parameter in clear_user_page()
Date: Mon, 25 May 2026 12:54:41 -0700 [thread overview]
Message-ID: <20260525125441.6a3a74300d73f1e0d32db4f8@linux-foundation.org> (raw)
In-Reply-To: <20260525-m68k-clear_user_page-v2-1-0c8981c6eca1@weissschuh.net>
On Mon, 25 May 2026 10:33:52 +0200 Thomas Weißschuh <linux@weissschuh.net> wrote:
> The loop in clear_user_pages() iterates over all pages and calls
> clear_user_page() for each of them. During the loop "vaddr" is modified.
> However on m68k clear_user() is a macro which does not use "vaddr".
> The compiler sees a variable which is modified but never used and emits
> a warning for that:
>
> include/linux/highmem.h: In function 'clear_user_pages':
> include/linux/highmem.h:234:63: warning: parameter 'vaddr' set but not used [-Wunused-but-set-parameter=]
> static inline void clear_user_pages(void *addr, unsigned long vaddr,
>
> Other architectures use an inline function for clear_user_page() which
> avoids the warning. This is not possible on m68k, as dlush_dcache_page()
> is another macro which is not yet defined where clear_user_page() is
> defined. Including cacheflush_mm.h will trigger recursive and lots of
> other issues.
>
> So hide the warning with a cast to (void) instead.
>
> While we are here, do the same for copy_user_page().
>
As with sparc, can this be addressed by converting these macros into
static inline C functions?
> --- a/arch/m68k/include/asm/page_mm.h
> +++ b/arch/m68k/include/asm/page_mm.h
> @@ -55,10 +55,12 @@ static inline void clear_page(void *page)
> #define clear_user_page(addr, vaddr, page) \
> do { clear_page(addr); \
> flush_dcache_page(page); \
> + (void)(vaddr); \
> } while (0)
> #define copy_user_page(to, from, vaddr, page) \
> do { copy_page(to, from); \
> flush_dcache_page(page); \
> + (void)(vaddr); \
> } while (0)
>
> extern unsigned long m68k_memoffset;
next prev parent reply other threads:[~2026-05-25 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 8:33 Thomas Weißschuh
2026-05-25 19:54 ` Andrew Morton [this message]
2026-07-01 9:48 ` Geert Uytterhoeven
2026-07-01 23:12 ` Andrew Morton
2026-07-02 8:07 ` Geert Uytterhoeven
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=20260525125441.6a3a74300d73f1e0d32db4f8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ankur.a.arora@oracle.com \
--cc=david@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux@weissschuh.net \
--cc=schwab@linux-m68k.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