From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android-mainline 1/1] mm/vmscan.c:6585:66: sparse: sparse: Using plain integer as NULL pointer
Date: Fri, 14 Aug 2026 11:04:09 +0800 [thread overview]
Message-ID: <202608141032.AZ76QJbg-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android-mainline
head: b4d3ec15824254c23211958f2e676e9394bc0600
commit: 874a0a566ede40f3d6062cae8fe1022e616edd1a [1/1] mm: vmscan: add cgroup IDs to vmscan tracepoints
config: arm-randconfig-r112-20260814 (https://download.01.org/0day-ci/archive/20260814/202608141032.AZ76QJbg-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260814/202608141032.AZ76QJbg-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
| Fixes: 874a0a566ede ("mm: vmscan: add cgroup IDs to vmscan tracepoints")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608141032.AZ76QJbg-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/vmscan.c:6585:66: sparse: sparse: Using plain integer as NULL pointer
mm/vmscan.c:6589:58: sparse: sparse: Using plain integer as NULL pointer
vim +6585 mm/vmscan.c
6551
6552 unsigned long try_to_free_pages(struct zonelist *zonelist, int order,
6553 gfp_t gfp_mask, nodemask_t *nodemask)
6554 {
6555 unsigned long nr_reclaimed;
6556 struct scan_control sc = {
6557 .nr_to_reclaim = SWAP_CLUSTER_MAX,
6558 .gfp_mask = current_gfp_context(gfp_mask),
6559 .reclaim_idx = gfp_zone(gfp_mask),
6560 .order = order,
6561 .nodemask = nodemask,
6562 .priority = DEF_PRIORITY,
6563 .may_writepage = 1,
6564 .may_unmap = 1,
6565 .may_swap = 1,
6566 };
6567
6568 /*
6569 * scan_control uses s8 fields for order, priority, and reclaim_idx.
6570 * Confirm they are large enough for max values.
6571 */
6572 BUILD_BUG_ON(MAX_PAGE_ORDER >= S8_MAX);
6573 BUILD_BUG_ON(DEF_PRIORITY > S8_MAX);
6574 BUILD_BUG_ON(MAX_NR_ZONES > S8_MAX);
6575
6576 /*
6577 * Do not enter reclaim if fatal signal was delivered while throttled.
6578 * 1 is returned so that the page allocator does not OOM kill at this
6579 * point.
6580 */
6581 if (throttle_direct_reclaim(sc.gfp_mask, zonelist, nodemask))
6582 return 1;
6583
6584 set_task_reclaim_state(current, &sc.reclaim_state);
> 6585 trace_mm_vmscan_direct_reclaim_begin(sc.gfp_mask, order, 0);
6586
6587 nr_reclaimed = do_try_to_free_pages(zonelist, &sc);
6588
6589 trace_mm_vmscan_direct_reclaim_end(nr_reclaimed, 0);
6590 set_task_reclaim_state(current, NULL);
6591
6592 return nr_reclaimed;
6593 }
6594
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-14 3:05 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=202608141032.AZ76QJbg-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.