From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Zhang Zekun <zhangzekun11@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 2600/2600] mm/hugetlb.c:6315:13: sparse: sparse: symbol 'hugetlb_alloc_hugepage_nodemask' was not declared. Should it be static?
Date: Fri, 27 Dec 2024 14:34:01 +0800 [thread overview]
Message-ID: <202412271456.Cm4dJ23V-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-5.10
head: 951151c7a27bc2a9436c2c49ae12510c82137ec1
commit: 8deff3a60ce1a9dffb552210f065fc9ed6a55f84 [2600/2600] mm/sharepool: Add mg_sp_alloc_nodemask
config: arm64-randconfig-r133-20241227 (https://download.01.org/0day-ci/archive/20241227/202412271456.Cm4dJ23V-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20241227/202412271456.Cm4dJ23V-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/202412271456.Cm4dJ23V-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/hugetlb.c:6315:13: sparse: sparse: symbol 'hugetlb_alloc_hugepage_nodemask' was not declared. Should it be static?
mm/hugetlb.c:446:12: sparse: sparse: context imbalance in 'allocate_file_region_entries' - wrong count at exit
mm/hugetlb.c:519:13: sparse: sparse: context imbalance in 'region_add' - wrong count at exit
mm/hugetlb.c:587:13: sparse: sparse: context imbalance in 'region_chg' - wrong count at exit
mm/hugetlb.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/mm.h):
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
mm/hugetlb.c: note: in included file:
include/linux/mm.h:1232:21: sparse: sparse: context imbalance in 'hugetlb_cow' - unexpected unlock
mm/hugetlb.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/mm.h):
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
mm/hugetlb.c:5402:25: sparse: sparse: context imbalance in 'follow_hugetlb_page' - different lock contexts for basic block
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:263:46: sparse: sparse: self-comparison always evaluates to false
vim +/hugetlb_alloc_hugepage_nodemask +6315 mm/hugetlb.c
6311
6312 /*
6313 * Allocate hugepage without reserve
6314 */
> 6315 struct page *hugetlb_alloc_hugepage_nodemask(int nid, int flag, nodemask_t *nodemask)
6316 {
6317 struct hstate *h = &default_hstate;
6318 gfp_t gfp_mask = htlb_alloc_mask(h);
6319 struct page *page = NULL;
6320
6321 if (nid == NUMA_NO_NODE)
6322 nid = numa_mem_id();
6323
6324 if (nid < 0 || nid >= MAX_NUMNODES)
6325 return NULL;
6326
6327 if (flag & ~HUGETLB_ALLOC_MASK)
6328 return NULL;
6329
6330 if (enable_charge_mighp)
6331 gfp_mask |= __GFP_ACCOUNT;
6332
6333 if (flag & HUGETLB_ALLOC_NORECLAIM)
6334 gfp_mask &= ~__GFP_RECLAIM;
6335
6336 if (flag & HUGETLB_ALLOC_NORMAL)
6337 page = hugetlb_alloc_hugepage_normal(h, gfp_mask, nid);
6338 else if (flag & HUGETLB_ALLOC_BUDDY)
6339 page = alloc_migrate_huge_page(h, gfp_mask, nid, nodemask);
6340 else
6341 page = alloc_huge_page_nodemask(h, nid, nodemask, gfp_mask);
6342
6343 return page;
6344 }
6345
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-12-27 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 6:34 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-27 23:56 [openeuler:OLK-5.10 2600/2600] mm/hugetlb.c:6315:13: sparse: sparse: symbol 'hugetlb_alloc_hugepage_nodemask' was not declared. Should it be static? 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=202412271456.Cm4dJ23V-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zhangzekun11@huawei.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.