From: kbuild test robot <lkp@intel.com>
To: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>
Subject: kernel/livepatch/../sched/sched.h:1619:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
Date: Sun, 24 May 2020 08:54:54 +0800 [thread overview]
Message-ID: <202005240847.QeA05Zl1%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0cfc8a8d70dcd51db783e8e87917e02149c71458
commit: 4104a562e0ca62e971089db9d3c47794a0d7d4eb sched/core: Annotate curr pointer in rq with __rcu
date: 3 months ago
config: x86_64-randconfig-s002-20200524 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-193-gb8fad4bc-dirty
git checkout 4104a562e0ca62e971089db9d3c47794a0d7d4eb
# save the attached .config to linux build tree
make W=1 C=1 ARCH=x86_64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> kernel/livepatch/../sched/sched.h:1619:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
>> kernel/livepatch/../sched/sched.h:1619:25: sparse: struct task_struct [noderef] <asn:4> *
>> kernel/livepatch/../sched/sched.h:1619:25: sparse: struct task_struct *
vim +1619 kernel/livepatch/../sched/sched.h
029632fbb7b7c9 kernel/sched.h Peter Zijlstra 2011-10-25 1616
029632fbb7b7c9 kernel/sched.h Peter Zijlstra 2011-10-25 1617 static inline int task_current(struct rq *rq, struct task_struct *p)
029632fbb7b7c9 kernel/sched.h Peter Zijlstra 2011-10-25 1618 {
029632fbb7b7c9 kernel/sched.h Peter Zijlstra 2011-10-25 @1619 return rq->curr == p;
029632fbb7b7c9 kernel/sched.h Peter Zijlstra 2011-10-25 1620 }
029632fbb7b7c9 kernel/sched.h Peter Zijlstra 2011-10-25 1621
:::::: The code at line 1619 was first introduced by commit
:::::: 029632fbb7b7c9d85063cc9eb470de6c54873df3 sched: Make separate sched*.c translation units
:::::: TO: Peter Zijlstra <a.p.zijlstra@chello.nl>
:::::: CC: Ingo Molnar <mingo@elte.hu>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35445 bytes --]
next reply other threads:[~2020-05-24 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 0:54 kbuild test robot [this message]
2020-08-04 20:03 kernel test robot
2020-11-28 18:14 kernel test robot
2021-01-15 7:45 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=202005240847.QeA05Zl1%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--cc=mingo@kernel.org \
--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®