From: kernel test robot <lkp@intel.com>
To: Alice Ryhl <aliceryhl@google.com>, acsjakub@amazon.de
Cc: oe-kbuild-all@lists.linux.dev, akpm@linux-foundation.org,
axelrasmussen@google.com, chengming.zhou@linux.dev,
david@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
peterx@redhat.com, xu.xin16@zte.com.cn,
rust-for-linux@vger.kernel.org, Alice Ryhl <aliceryhl@google.com>
Subject: Re: [PATCH] mm: use enum for vm_flags
Date: Sat, 11 Oct 2025 00:13:50 +0800 [thread overview]
Message-ID: <202510110039.N3gHQwXj-lkp@intel.com> (raw)
In-Reply-To: <20251007162136.1885546-1-aliceryhl@google.com>
Hi Alice,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/Alice-Ryhl/mm-use-enum-for-vm_flags/20251010-095004
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20251007162136.1885546-1-aliceryhl%40google.com
patch subject: [PATCH] mm: use enum for vm_flags
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20251011/202510110039.N3gHQwXj-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251011/202510110039.N3gHQwXj-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/202510110039.N3gHQwXj-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/pagewalk.h:5,
from fs/proc/task_mmu.c:2:
fs/proc/task_mmu.c: In function 'show_smap_vma_flags':
>> include/linux/mm.h:353:24: warning: "VM_HIGH_ARCH_3" is not defined, evaluates to 0 [-Wundef]
353 | # define VM_PKEY_BIT3 VM_HIGH_ARCH_3
| ^~~~~~~~~~~~~~
fs/proc/task_mmu.c:1184:5: note: in expansion of macro 'VM_PKEY_BIT3'
1184 | #if VM_PKEY_BIT3
| ^~~~~~~~~~~~
vim +/VM_HIGH_ARCH_3 +353 include/linux/mm.h
63c17fb8e5a46a Dave Hansen 2016-02-12 346
5212213aa5a235 Ram Pai 2018-03-27 347 #ifdef CONFIG_ARCH_HAS_PKEYS
8f62c883222c9e Dave Hansen 2016-02-12 348 # define VM_PKEY_SHIFT VM_HIGH_ARCH_BIT_0
9f82f15ddfdd60 Joey Gouly 2024-08-22 349 # define VM_PKEY_BIT0 VM_HIGH_ARCH_0
9f82f15ddfdd60 Joey Gouly 2024-08-22 350 # define VM_PKEY_BIT1 VM_HIGH_ARCH_1
8f62c883222c9e Dave Hansen 2016-02-12 351 # define VM_PKEY_BIT2 VM_HIGH_ARCH_2
9f82f15ddfdd60 Joey Gouly 2024-08-22 352 #if CONFIG_ARCH_PKEY_BITS > 3
8f62c883222c9e Dave Hansen 2016-02-12 @353 # define VM_PKEY_BIT3 VM_HIGH_ARCH_3
9f82f15ddfdd60 Joey Gouly 2024-08-22 354 #else
9f82f15ddfdd60 Joey Gouly 2024-08-22 355 # define VM_PKEY_BIT3 0
9f82f15ddfdd60 Joey Gouly 2024-08-22 356 #endif
9f82f15ddfdd60 Joey Gouly 2024-08-22 357 #if CONFIG_ARCH_PKEY_BITS > 4
2c9e0a6fa2bb75 Ram Pai 2018-03-27 358 # define VM_PKEY_BIT4 VM_HIGH_ARCH_4
2c9e0a6fa2bb75 Ram Pai 2018-03-27 359 #else
2c9e0a6fa2bb75 Ram Pai 2018-03-27 360 # define VM_PKEY_BIT4 0
8f62c883222c9e Dave Hansen 2016-02-12 361 #endif
5212213aa5a235 Ram Pai 2018-03-27 362 #endif /* CONFIG_ARCH_HAS_PKEYS */
5212213aa5a235 Ram Pai 2018-03-27 363
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-10 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 7:52 [PATCH v4] mm: redefine VM_* flag constants with BIT() Jakub Acs
2025-10-02 7:54 ` David Hildenbrand
2025-10-02 17:43 ` SeongJae Park
2025-10-07 16:21 ` [PATCH] mm: use enum for vm_flags Alice Ryhl
2025-10-07 17:01 ` Darrick J. Wong
2025-10-08 2:36 ` John Hubbard
2025-10-08 12:54 ` Jakub Acs
2025-10-08 13:15 ` Alice Ryhl
2025-10-10 15:10 ` Darrick J. Wong
2025-10-08 14:17 ` Steven Rostedt
2025-10-09 2:33 ` John Hubbard
2025-10-11 0:18 ` kernel test robot
2025-10-11 0:39 ` kernel test robot
2025-10-10 16:13 ` kernel test robot [this message]
2025-10-11 0:50 ` 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=202510110039.N3gHQwXj-lkp@intel.com \
--to=lkp@intel.com \
--cc=acsjakub@amazon.de \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=axelrasmussen@google.com \
--cc=chengming.zhou@linux.dev \
--cc=david@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterx@redhat.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=xu.xin16@zte.com.cn \
/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