From: Yu Zhao <yuzhao@google.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 1876/2065] mm/vmscan.c:3232:9: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Thu, 18 Aug 2022 12:34:01 -0600 [thread overview]
Message-ID: <CAOUHufY8+O_MwkrPzgfBKSFwLJ1v6LPDox1yGV0tjX4ozjh2Dw@mail.gmail.com> (raw)
In-Reply-To: <202208190147.RwbMifl8-lkp@intel.com>
On Thu, Aug 18, 2022 at 11:50 AM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 5b6a4bf680d61b1dd26629840f848d0df8983c62
> commit: 37f44f48d52d734fe0879909f5071a6c635d255b [1876/2065] mm: multi-gen LRU: support page table walks
> config: sparc64-randconfig-s053-20220818
> compiler: sparc64-linux-gcc (GCC) 12.1.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-39-gce1a6720-dirty
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=37f44f48d52d734fe0879909f5071a6c635d255b
> 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 37f44f48d52d734fe0879909f5071a6c635d255b
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=sparc64 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
>
> sparse warnings: (new ones prefixed by >>)
> >> mm/vmscan.c:3232:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct lockdep_map const *lock @@ got struct lockdep_map [noderef] __rcu * @@
> mm/vmscan.c:3232:9: sparse: expected struct lockdep_map const *lock
> mm/vmscan.c:3232:9: sparse: got struct lockdep_map [noderef] __rcu *
...
> vim +3232 mm/vmscan.c
>
> 3226
> 3227 #ifdef CONFIG_MEMCG
> 3228 void lru_gen_migrate_mm(struct mm_struct *mm)
> 3229 {
> 3230 struct mem_cgroup *memcg;
> 3231
> > 3232 lockdep_assert_held(&mm->owner->alloc_lock);
...
Thanks. Queued the fix:
struct task_struct *task = rcu_dereference_protected(mm->owner, true);
lockdep_assert_held(&task->alloc_lock);
prev parent reply other threads:[~2022-08-18 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 17:49 kernel test robot
2022-08-18 18:34 ` Yu Zhao [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=CAOUHufY8+O_MwkrPzgfBKSFwLJ1v6LPDox1yGV0tjX4ozjh2Dw@mail.gmail.com \
--to=yuzhao@google.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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