From: Oleg Nesterov <oleg@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org, Thomas Gleixner <tglx@kernel.org>,
Bradley Morgan <include@grrlz.net>
Subject: Re: [tip:timers/core 2/31] kernel/time/posix-cpu-timers.c:1307:9: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Wed, 8 Jul 2026 17:45:16 +0200 [thread overview]
Message-ID: <ak5wjJSOyqpXKBdj@redhat.com> (raw)
In-Reply-To: <202607081829.RPQBe6Fs-lkp@intel.com>
On 07/08, kernel test robot wrote:
>
> sparse warnings: (new ones prefixed by >>)
> >> kernel/time/posix-cpu-timers.c:1307:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
> kernel/time/posix-cpu-timers.c:1307:9: sparse: expected struct spinlock [usertype] *lock
> kernel/time/posix-cpu-timers.c:1307:9: sparse: got struct spinlock [noderef] __rcu *
> kernel/time/posix-cpu-timers.c:1367:36: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
> kernel/time/posix-cpu-timers.c:1367:36: sparse: expected struct spinlock [usertype] *lock
> kernel/time/posix-cpu-timers.c:1367:36: sparse: got struct spinlock [noderef] __rcu *
> kernel/time/posix-cpu-timers.c: note: in included file:
> include/linux/sched/signal.h:749:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
> include/linux/sched/signal.h:749:37: sparse: expected struct spinlock [usertype] *lock
> include/linux/sched/signal.h:749:37: sparse: got struct spinlock [noderef] __rcu *
> include/linux/sched/signal.h:749:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
> include/linux/sched/signal.h:749:37: sparse: expected struct spinlock [usertype] *lock
> include/linux/sched/signal.h:749:37: sparse: got struct spinlock [noderef] __rcu *
> include/linux/sched/signal.h:749:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
> include/linux/sched/signal.h:749:37: sparse: expected struct spinlock [usertype] *lock
> include/linux/sched/signal.h:749:37: sparse: got struct spinlock [noderef] __rcu *
> include/linux/sched/signal.h:749:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
> include/linux/sched/signal.h:749:37: sparse: expected struct spinlock [usertype] *lock
> include/linux/sched/signal.h:749:37: sparse: got struct spinlock [noderef] __rcu *
> include/linux/sched/signal.h:749:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
> include/linux/sched/signal.h:749:37: sparse: expected struct spinlock [usertype] *lock
> include/linux/sched/signal.h:749:37: sparse: got struct spinlock [noderef] __rcu *
IMO, we should remove this __rcu annotation, it doesn't really help.
Oleg.
prev parent reply other threads:[~2026-07-08 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 10:52 [tip:timers/core 2/31] kernel/time/posix-cpu-timers.c:1307:9: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2026-07-08 15:45 ` Oleg Nesterov [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=ak5wjJSOyqpXKBdj@redhat.com \
--to=oleg@redhat.com \
--cc=include@grrlz.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@kernel.org \
--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