From: Andreas Larsson <andreas@gaisler.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"David S. Miller" <davem@davemloft.net>,
"Ankur Arora" <ankur.a.arora@oracle.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Hildenbrand (Red Hat)" <david@kernel.org>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sparc: Avoid -Wunused-but-set-parameter in clear_user_page()
Date: Fri, 12 Jun 2026 11:15:22 +0200 [thread overview]
Message-ID: <b7749d3f-ab9a-420d-a203-2a9d5289e22b@gaisler.com> (raw)
In-Reply-To: <20260525-sparc-clear_user_page-v2-1-e7a47fbcf439@weissschuh.net>
On 2026-05-25 10:36, Thomas Weißschuh 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 sparc 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 sparc, as
> sparc_flush_page_to_ram() is not yet declared where clear_user_page() is
> defined. Including cacheflush_32.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().
>
> Fixes: 62a9f5a85b98 ("mm: introduce clear_pages() and clear_user_pages()")
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Changes in v2:
> - Put parens around vaddr.
> - Link to v1: https://patch.msgid.link/20260524-sparc-clear_user_page-v1-1-baa5b90e5d0d@weissschuh.net
> ---
> arch/sparc/include/asm/page_32.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/sparc/include/asm/page_32.h b/arch/sparc/include/asm/page_32.h
> index c1bccbedf567..9f0b54f70908 100644
> --- a/arch/sparc/include/asm/page_32.h
> +++ b/arch/sparc/include/asm/page_32.h
> @@ -20,10 +20,12 @@
> #define clear_user_page(addr, vaddr, page) \
> do { clear_page(addr); \
> sparc_flush_page_to_ram(page); \
> + (void)(vaddr); \
> } while (0)
> #define copy_user_page(to, from, vaddr, page) \
> do { copy_page(to, from); \
> sparc_flush_page_to_ram(page); \
> + (void)(vaddr); \
> } while (0)
>
> /* The following structure is used to hold the physical
>
> ---
> base-commit: d87895ce6e45997825cfe1b3565a1843e8ac8011
> change-id: 20260523-sparc-clear_user_page-7448669a2476
Reviewed-by: Andreas Larsson <andreas@gaisler.com>
Picking this up to my for-next.
Thanks,
Andreas
prev parent reply other threads:[~2026-06-12 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 8:36 Thomas Weißschuh
2026-05-25 17:44 ` Andrew Morton
2026-05-25 19:48 ` Thomas Weißschuh
2026-05-25 20:39 ` Andrew Morton
2026-06-12 9:15 ` Andreas Larsson [this message]
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=b7749d3f-ab9a-420d-a203-2a9d5289e22b@gaisler.com \
--to=andreas@gaisler.com \
--cc=akpm@linux-foundation.org \
--cc=ankur.a.arora@oracle.com \
--cc=davem@davemloft.net \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=sparclinux@vger.kernel.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
all inboxes | Powered by JetHome®