From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [akpm-mm:mm-new 285/313] ../../../mm/vma.c:2592:33: error: 'VM_NO_MLOCK_MASK' undeclared; did you mean 'VM_LOCKED_MASK'?
Date: Sat, 07 Mar 2026 04:44:52 +0100 [thread overview]
Message-ID: <202603070433.MUXyiGWN-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: David Hildenbrand <david@kernel.org>
TO: Anthony Yznaga <anthony.yznaga@oracle.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
Hi Anthony,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head: fee41c6c27b01fdd910a9d9cd4f3b978efb92ea2
commit: 6c41b23d5f57f306c940c65a2a5240bc20a95659 [285/313] mm: prevent droppable mappings from being locked
:::::: branch date: 89 minutes ago
:::::: commit date: 89 minutes ago
config: x86_64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260307/202603070433.MUXyiGWN-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/20260307/202603070433.MUXyiGWN-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/r/202603070433.MUXyiGWN-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from main.c:10:
../../../mm/vma.c: In function '__mmap_complete':
>> ../../../mm/vma.c:2592:33: error: 'VM_NO_MLOCK_MASK' undeclared (first use in this function); did you mean 'VM_LOCKED_MASK'?
2592 | if ((vm_flags & VM_NO_MLOCK_MASK) || vma_is_dax(vma) ||
| ^~~~~~~~~~~~~~~~
| VM_LOCKED_MASK
../../../mm/vma.c:2592:33: note: each undeclared identifier is reported only once for each function it appears in
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-03-07 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 3:44 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-07 4:02 [akpm-mm:mm-new 285/313] ../../../mm/vma.c:2592:33: error: 'VM_NO_MLOCK_MASK' undeclared; did you mean 'VM_LOCKED_MASK'? kernel test robot
2026-03-07 21:23 ` anthony.yznaga
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=202603070433.MUXyiGWN-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.