From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android13-5.10 8/8] mm/page_alloc.c:6789:16: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Tue, 17 Oct 2023 03:44:33 +0800 [thread overview]
Message-ID: <202310170348.mAd1UCKv-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android13-5.10
head: a2070840fa45c2e9da5e2a9aae79840f8158174a
commit: 42596c7b41c85be2647f23da66cda4b0a0c242e1 [8/8] ANDROID: fix ABI breakage caused by per_cpu_pages
config: i386-randconfig-063-20231016 (https://download.01.org/0day-ci/archive/20231017/202310170348.mAd1UCKv-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231017/202310170348.mAd1UCKv-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/202310170348.mAd1UCKv-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/page_alloc.c:6789:16: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct per_cpu_pageset_ext *ps_ext @@ got struct per_cpu_pageset_ext [noderef] __percpu * @@
mm/page_alloc.c:6789:16: sparse: expected struct per_cpu_pageset_ext *ps_ext
mm/page_alloc.c:6789:16: sparse: got struct per_cpu_pageset_ext [noderef] __percpu *
>> mm/page_alloc.c:6790:23: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct per_cpu_pageset [noderef] __percpu *pageset @@ got struct per_cpu_pageset * @@
mm/page_alloc.c:6790:23: sparse: expected struct per_cpu_pageset [noderef] __percpu *pageset
mm/page_alloc.c:6790:23: sparse: got struct per_cpu_pageset *
mm/page_alloc.c:3365:28: sparse: sparse: context imbalance in 'free_unref_page_commit' - unexpected unlock
mm/page_alloc.c:3687:20: sparse: sparse: context imbalance in '__rmqueue_pcplist' - wrong count at exit
mm/page_alloc.c: note: in included file (through include/linux/mm.h):
include/linux/gfp.h:369:27: sparse: sparse: restricted gfp_t degrades to integer
include/linux/gfp.h:369:27: sparse: sparse: restricted gfp_t degrades to integer
include/linux/gfp.h:369:27: sparse: sparse: restricted gfp_t degrades to integer
include/linux/gfp.h:369:27: sparse: sparse: restricted gfp_t degrades to integer
vim +6789 mm/page_alloc.c
6783
6784 void __meminit setup_zone_pageset(struct zone *zone)
6785 {
6786 int cpu;
6787 struct per_cpu_pageset_ext *ps_ext;
6788
> 6789 ps_ext = alloc_percpu(struct per_cpu_pageset_ext);
> 6790 zone->pageset = &ps_ext->pageset;
6791 for_each_possible_cpu(cpu)
6792 zone_pageset_init(zone, cpu);
6793 }
6794
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-10-16 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 19:44 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-25 16:02 [android-common:android13-5.10 8/8] mm/page_alloc.c:6789:16: sparse: sparse: incorrect type in assignment (different address spaces) kernel test robot
2024-11-17 11:50 kernel test robot
2024-10-03 16:10 kernel test robot
2023-04-20 3:05 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=202310170348.mAd1UCKv-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.