From: Nam Cao <namcao@linutronix.de>
To: kernel test robot <lkp@intel.com>, Gabriele Monaco <gmonaco@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: kernel/trace/rv/monitors/deadline/deadline.h:115:46: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Tue, 19 May 2026 07:27:33 +0200 [thread overview]
Message-ID: <87zf1wufy2.fsf@yellow.woof> (raw)
In-Reply-To: <202605191116.acPXYOW4-lkp@intel.com>
kernel test robot <lkp@intel.com> writes:
> sparse warnings: (new ones prefixed by >>)
> kernel/trace/rv/monitors/nomiss/nomiss.c: note: in included file:
>>> kernel/trace/rv/monitors/deadline/deadline.h:115:46: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *dst @@ got struct sched_attr [noderef] __user * @@
> kernel/trace/rv/monitors/deadline/deadline.h:115:46: sparse: expected void *dst
> kernel/trace/rv/monitors/deadline/deadline.h:115:46: sparse: got struct sched_attr [noderef] __user *
>>> kernel/trace/rv/monitors/deadline/deadline.h:118:21: sparse: sparse: dereference of noderef expression
> kernel/trace/rv/monitors/deadline/deadline.h:120:30: sparse: sparse: dereference of noderef expression
Already fixed by:
https://lore.kernel.org/lkml/20260512140250.262190-2-gmonaco@redhat.com/
Nam
prev parent reply other threads:[~2026-05-19 5:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 3:15 kernel/trace/rv/monitors/deadline/deadline.h:115:46: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2026-05-19 5:27 ` Nam Cao [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=87zf1wufy2.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=gmonaco@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.