From: kernel test robot <lkp@intel.com>
To: Yu Zhao <yuzhao@google.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 4227/4328] mm/vmscan.c:3184:40: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 16 Apr 2022 08:35:32 +0800 [thread overview]
Message-ID: <202204160827.ekEARWQo-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 40354149f4d738dc3492d9998e45b3f02950369a
commit: 32be05f0e1b84564fa4e5d1810191a198c47f87b [4227/4328] mm: multi-gen LRU: support page table walks
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20220416/202204160827.ekEARWQo-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=32be05f0e1b84564fa4e5d1810191a198c47f87b
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 32be05f0e1b84564fa4e5d1810191a198c47f87b
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=m68k SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> mm/vmscan.c:3184:40: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct task_struct *p @@ got struct task_struct [noderef] __rcu *owner @@
mm/vmscan.c:3184:40: sparse: expected struct task_struct *p
mm/vmscan.c:3184:40: sparse: got struct task_struct [noderef] __rcu *owner
mm/vmscan.c:1329:28: sparse: sparse: context imbalance in '__remove_mapping' - unexpected unlock
mm/vmscan.c:2203:33: sparse: sparse: context imbalance in 'folio_isolate_lru' - unexpected unlock
mm/vmscan.c:2296:48: sparse: sparse: context imbalance in 'move_pages_to_lru' - unexpected unlock
mm/vmscan.c: note: in included file (through include/linux/rculist.h, include/linux/pid.h, include/linux/sched.h, ...):
include/linux/rcupdate.h:725:9: sparse: sparse: context imbalance in 'lru_gen_look_around' - different lock contexts for basic block
mm/vmscan.c: note: in included file (through include/linux/swap.h):
include/linux/memcontrol.h:1610:39: sparse: sparse: context imbalance in 'check_move_unevictable_pages' - unexpected unlock
vim +3184 mm/vmscan.c
3171
3172 #ifdef CONFIG_MEMCG
3173 void lru_gen_migrate_mm(struct mm_struct *mm)
3174 {
3175 struct mem_cgroup *memcg;
3176
3177 lockdep_assert_held(&mm->owner->alloc_lock);
3178
3179 /* for mm_update_next_owner() */
3180 if (mem_cgroup_disabled())
3181 return;
3182
3183 rcu_read_lock();
> 3184 memcg = mem_cgroup_from_task(mm->owner);
3185 rcu_read_unlock();
3186 if (memcg == mm->lru_gen.memcg)
3187 return;
3188
3189 VM_BUG_ON_MM(!mm->lru_gen.memcg, mm);
3190 VM_BUG_ON_MM(list_empty(&mm->lru_gen.list), mm);
3191
3192 lru_gen_del_mm(mm);
3193 lru_gen_add_mm(mm);
3194 }
3195 #endif
3196
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-04-16 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 0:35 kernel test robot [this message]
2022-04-16 2:41 ` Yu Zhao
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=202204160827.ekEARWQo-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=yuzhao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox