From: Charlemagne Lasse <charlemagnelasse@gmail.com>
To: x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
Luc Van Oostenryck <lucvoo@kernel.org>
Cc: Uros Bizjak <ubizjak@gmail.com>,
Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Nadav Amit <namit@vmware.com>, Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: warning: cast removes address space '__percpu' of expression
Date: Sat, 30 Mar 2024 00:56:54 +0100 [thread overview]
Message-ID: <CAFGhKbzev7W4aHwhFPWwMZQEHenVgZUj7=aunFieVqZg3mt14A@mail.gmail.com> (raw)
After switching to linux 6.9-rc1, I get a lot of these errors (when
compiling with cgcc/sparse):
./include/linux/netdevice.h:4033:17: warning: cast removes address
space '__percpu' of expression
This is around code which wasn't changed and which correctly uses the
per cpu helper. Sparse flags were -Wsparse-all for sparse 0.6.4
(latest release). Sparse was enabled via C=1 parameter and sparse was
configured using CHECK="sparse -Wsparse-all"
Problem was introduced between commit 8ae292c66dcb ("x86/lib: Address
kernel-doc warnings") and 3a1d3829e193 ("x86/percpu: Avoid sparse
warning with cast to named address space").
I would even go as far as saying that 1ca3683cc6d2 ("x86/percpu:
Enable named address spaces with known compiler version") together
with 3a1d3829e193 ("x86/percpu: Avoid sparse warning with cast to
named address space") triggered this problem
next reply other threads:[~2024-03-29 23:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 23:56 Charlemagne Lasse [this message]
2024-03-30 17:42 ` warning: cast removes address space '__percpu' of expression Charlemagne Lasse
2024-04-01 19:16 ` Uros Bizjak
2024-04-02 7:56 ` Charlemagne Lasse
2024-04-02 9:43 ` Uros Bizjak
2024-04-02 9:53 ` Charlemagne Lasse
2024-04-02 20:09 ` Charlemagne Lasse
2024-04-02 20:40 ` Uros Bizjak
2024-04-03 7:14 ` Charlemagne Lasse
2024-04-22 7:22 ` Charlemagne Lasse
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='CAFGhKbzev7W4aHwhFPWwMZQEHenVgZUj7=aunFieVqZg3mt14A@mail.gmail.com' \
--to=charlemagnelasse@gmail.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucvoo@kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).