From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: kernel/futex/core.c:505:38: sparse: sparse: cast removes address space '__user' of expression
Date: Tue, 13 Jan 2026 12:59:46 +0100 [thread overview]
Message-ID: <20260113115946.L49jwJMx@linutronix.de> (raw)
In-Reply-To: <202601131901.j7WJ9OeZ-lkp@intel.com>
On 2026-01-13 19:22:40 [+0800], kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: b71e635feefc852405b14620a7fc58c4c80c0f73
> commit: cec199c5e39bde7191a08087cc3d002ccfab31ff futex: Implement FUTEX2_NUMA
> date: 9 months ago
> config: arm64-randconfig-r123-20260113 (https://download.01.org/0day-ci/archive/20260113/202601131901.j7WJ9OeZ-lkp@intel.com/config)
> compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260113/202601131901.j7WJ9OeZ-lkp@intel.com/reproduce)
…
>sparse warnings: (new ones prefixed by >>)
>>> kernel/futex/core.c:505:38: sparse: sparse: cast removes address space '__user' of expression
>>> kernel/futex/core.c:505:51: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected unsigned int [noderef] [usertype] __user *naddr @@ got void * @@
> kernel/futex/core.c:505:51: sparse: expected unsigned int [noderef] [usertype] __user *naddr
> kernel/futex/core.c:505:51: sparse: got void *
> kernel/futex/core.c:894:9: sparse: sparse: context imbalance in 'futex_q_lockptr_lock' - wrong count at exit
…
> > 505 u32 __user *naddr = (void *)uaddr + size / 2;
[ ] I (PeterZ) have it fixed, will post soon
[ ] Fix it for me, I'm saving the world atm
[ ] Ignore it because of $reasonable_reason
Sebastian
next prev parent reply other threads:[~2026-01-13 11:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 11:22 kernel test robot
2026-01-13 11:59 ` Sebastian Andrzej Siewior [this message]
2026-01-13 12:10 ` Peter Zijlstra
2026-01-13 17:37 ` Sebastian Andrzej Siewior
2026-01-13 19:39 ` Peter Zijlstra
2026-01-14 9:35 ` Sebastian Andrzej Siewior
2026-01-14 11:08 ` Peter Zijlstra
2026-01-14 12:09 ` Sebastian Andrzej Siewior
2026-01-14 12:16 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2026-02-15 22:01 kernel test robot
2025-12-11 8:07 kernel test robot
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=20260113115946.L49jwJMx@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@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
all inboxes | Powered by JetHome®