From: kernel test robot <lkp@intel.com>
To: Brendan Jackman <jackmanb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org,
Brendan Jackman <jackmanb@google.com>
Subject: Re: [PATCH] mm/vmalloc: clarify why vmap_range_noflush() might sleep
Date: Tue, 9 Dec 2025 09:10:40 +0800 [thread overview]
Message-ID: <202512090844.OmozcWcI-lkp@intel.com> (raw)
In-Reply-To: <20251208-b4-vmalloc-might_alloc-v1-1-94a9bb8ecb08@google.com>
Hi Brendan,
kernel test robot noticed the following build errors:
[auto build test ERROR on ecc46e02e0abe025a6e840cba2d647f23fd1d721]
url: https://github.com/intel-lab-lkp/linux/commits/Brendan-Jackman/mm-vmalloc-clarify-why-vmap_range_noflush-might-sleep/20251208-132202
base: ecc46e02e0abe025a6e840cba2d647f23fd1d721
patch link: https://lore.kernel.org/r/20251208-b4-vmalloc-might_alloc-v1-1-94a9bb8ecb08%40google.com
patch subject: [PATCH] mm/vmalloc: clarify why vmap_range_noflush() might sleep
config: nios2-allnoconfig (https://download.01.org/0day-ci/archive/20251209/202512090844.OmozcWcI-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251209/202512090844.OmozcWcI-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/202512090844.OmozcWcI-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/vmalloc.c: In function 'vmap_range_noflush':
>> mm/vmalloc.c:308:21: error: 'GFP_PGTABLE_KERNEL' undeclared (first use in this function)
308 | might_alloc(GFP_PGTABLE_KERNEL);
| ^~~~~~~~~~~~~~~~~~
mm/vmalloc.c:308:21: note: each undeclared identifier is reported only once for each function it appears in
vim +/GFP_PGTABLE_KERNEL +308 mm/vmalloc.c
297
298 static int vmap_range_noflush(unsigned long addr, unsigned long end,
299 phys_addr_t phys_addr, pgprot_t prot,
300 unsigned int max_page_shift)
301 {
302 pgd_t *pgd;
303 unsigned long start;
304 unsigned long next;
305 int err;
306 pgtbl_mod_mask mask = 0;
307
> 308 might_alloc(GFP_PGTABLE_KERNEL);
309 BUG_ON(addr >= end);
310
311 start = addr;
312 pgd = pgd_offset_k(addr);
313 do {
314 next = pgd_addr_end(addr, end);
315 err = vmap_p4d_range(pgd, addr, next, phys_addr, prot,
316 max_page_shift, &mask);
317 if (err)
318 break;
319 } while (pgd++, phys_addr += (next - addr), addr = next, addr != end);
320
321 if (mask & ARCH_PAGE_TABLE_SYNC_MASK)
322 arch_sync_kernel_mappings(start, end);
323
324 return err;
325 }
326
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-12-09 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 5:19 Brendan Jackman
2025-12-08 6:41 ` Anshuman Khandual
2025-12-08 7:39 ` Brendan Jackman
2025-12-08 17:32 ` Uladzislau Rezki
2025-12-08 8:51 ` [syzbot ci] " syzbot ci
2025-12-09 2:56 ` Brendan Jackman
2025-12-09 1:10 ` kernel test robot [this message]
2025-12-09 1:52 ` [PATCH] " 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=202512090844.OmozcWcI-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=urezki@gmail.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