From: kernel test robot <lkp@intel.com>
To: Rob Clark <robdclark@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 6881/8719] drivers/gpu/drm/msm/msm_gem.c:51:43: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Fri, 28 Jun 2024 00:12:13 +0800 [thread overview]
Message-ID: <202406280050.syeEwLTE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: df9574a57d02b265322e77fb8628d4d33641dda9
commit: 204226de27c3a6328b155005f132afe12eca3a5e [6881/8719] drm/msm: Add GPU memory traces
config: powerpc64-randconfig-r132-20240627 (https://download.01.org/0day-ci/archive/20240628/202406280050.syeEwLTE-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240628/202406280050.syeEwLTE-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202406280050.syeEwLTE-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/msm/msm_gem.c:51:43: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct pid *pid @@ got struct pid [noderef] __rcu *pid @@
drivers/gpu/drm/msm/msm_gem.c:51:43: sparse: expected struct pid *pid
drivers/gpu/drm/msm/msm_gem.c:51:43: sparse: got struct pid [noderef] __rcu *pid
drivers/gpu/drm/msm/msm_gem.c: note: in included file (through include/linux/smp.h, include/linux/lockdep.h, include/linux/spinlock.h, ...):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
vim +51 drivers/gpu/drm/msm/msm_gem.c
44
45 static void update_ctx_mem(struct drm_file *file, ssize_t size)
46 {
47 struct msm_file_private *ctx = file->driver_priv;
48 uint64_t ctx_mem = atomic64_add_return(size, &ctx->ctx_mem);
49
50 rcu_read_lock(); /* Locks file->pid! */
> 51 trace_gpu_mem_total(0, pid_nr(file->pid), ctx_mem);
52 rcu_read_unlock();
53
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-27 16:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202406280050.syeEwLTE-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robdclark@chromium.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