All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 117/327] kernel/cgroup/cgroup.c:3528:13: sparse: error: incompatible types in comparison expression (different address spaces)
Date: Thu, 7 Feb 2019 22:55:15 +0800	[thread overview]
Message-ID: <201902072213.zItcUwRS%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]

tree:   git://git.cmpxchg.org/linux-mmotm.git master
head:   79d7b443931d1eff3b746a2956a6abf9cb5d85cc
commit: 52c6636ad0584ccff2e166dee62d55a6dacbb76f [117/327] psi: introduce psi monitor
reproduce:
        # apt-get install sparse
        git checkout 52c6636ad0584ccff2e166dee62d55a6dacbb76f
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

Note: the mmotm/master HEAD 79d7b443931d1eff3b746a2956a6abf9cb5d85cc builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

>> kernel/cgroup/cgroup.c:3528:13: sparse: error: incompatible types in comparison expression (different address spaces)
   kernel/cgroup/cgroup.c:2684:20: sparse: warning: context imbalance in 'cgroup_procs_write_start' - wrong count at exit
   kernel/cgroup/cgroup.c:2740:9: sparse: warning: context imbalance in 'cgroup_procs_write_finish' - wrong count at exit
   kernel/cgroup/cgroup.c:2851:9: sparse: warning: context imbalance in 'cgroup_lock_and_drain_offline' - wrong count at exit
   kernel/cgroup/cgroup.c:4552:16: sparse: warning: context imbalance in 'cgroup_procs_write' - wrong count at exit
   kernel/cgroup/cgroup.c:4593:16: sparse: warning: context imbalance in 'cgroup_threads_write' - wrong count at exit

vim +3528 kernel/cgroup/cgroup.c

  3520	
  3521	static __poll_t cgroup_pressure_poll(struct kernfs_open_file *of,
  3522						  poll_table *pt)
  3523	{
  3524		struct psi_trigger *t;
  3525		__poll_t ret;
  3526	
  3527		rcu_read_lock();
> 3528		t = rcu_dereference(of->priv);
  3529		if (t)
  3530			ret = psi_trigger_poll(t, of->file, pt);
  3531		else
  3532			ret = DEFAULT_POLLMASK | EPOLLERR | EPOLLPRI;
  3533		rcu_read_unlock();
  3534	
  3535		return ret;
  3536	}
  3537	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 67278 bytes --]

                 reply	other threads:[~2019-02-07 14:56 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=201902072213.zItcUwRS%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=surenb@google.com \
    /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.