All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chen Lin <chen45464546@163.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org, 0day robot <lkp@intel.com>
Subject: mm/page_alloc.c:5662:16: error: use of undeclared identifier 'fragz'; did you mean 'fragsz'?
Date: Wed, 1 Jun 2022 03:53:29 +0800	[thread overview]
Message-ID: <202206010311.t1nGkYl6-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/UPDATE-20220531-224555/Chen-Lin/mm-page_frag-Warn_on-when-frag_alloc-size-is-bigger-than-PAGE_SIZE/20220528-234129
head:   21e940b5a66de64088e93248c21bce241c28a556
commit: 21e940b5a66de64088e93248c21bce241c28a556 mm: page_frag: Warn_on when frag_alloc size is bigger than PAGE_SIZE
date:   5 hours ago
config: x86_64-randconfig-a014 (https://download.01.org/0day-ci/archive/20220601/202206010311.t1nGkYl6-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project c825abd6b0198fb088d9752f556a70705bc99dfd)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/intel-lab-lkp/linux/commit/21e940b5a66de64088e93248c21bce241c28a556
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review UPDATE-20220531-224555/Chen-Lin/mm-page_frag-Warn_on-when-frag_alloc-size-is-bigger-than-PAGE_SIZE/20220528-234129
        git checkout 21e940b5a66de64088e93248c21bce241c28a556
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> mm/page_alloc.c:5662:16: error: use of undeclared identifier 'fragz'; did you mean 'fragsz'?
           if (WARN_ONCE(fragz > PAGE_SIZE,
                         ^~~~~
                         fragsz
   include/asm-generic/bug.h:151:18: note: expanded from macro 'WARN_ONCE'
           DO_ONCE_LITE_IF(condition, WARN, 1, format)
                           ^
   include/linux/once_lite.h:15:27: note: expanded from macro 'DO_ONCE_LITE_IF'
                   bool __ret_do_once = !!(condition);                     \
                                           ^
   mm/page_alloc.c:5651:22: note: 'fragsz' declared here
                         unsigned int fragsz, gfp_t gfp_mask,
                                      ^
   1 error generated.


vim +5662 mm/page_alloc.c

  5649	
  5650	void *page_frag_alloc_align(struct page_frag_cache *nc,
  5651			      unsigned int fragsz, gfp_t gfp_mask,
  5652			      unsigned int align_mask)
  5653	{
  5654		unsigned int size = PAGE_SIZE;
  5655		struct page *page;
  5656		int offset;
  5657	
  5658		/*
  5659		 * frag_alloc is not suitable for memory alloc which fragsz
  5660		 * is bigger than PAGE_SIZE, use kmalloc or alloc_pages instead.
  5661		 */
> 5662		if (WARN_ONCE(fragz > PAGE_SIZE,
  5663			      "alloc fragsz(%d) > PAGE_SIZE(%ld) not supported, alloc fail\n",
  5664			      fragsz, PAGE_SIZE))
  5665			return NULL;
  5666	
  5667		if (unlikely(!nc->va)) {
  5668	refill:
  5669			page = __page_frag_cache_refill(nc, gfp_mask);
  5670			if (!page)
  5671				return NULL;
  5672	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-05-31 19:54 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=202206010311.t1nGkYl6-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chen45464546@163.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@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.