From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [gourryinverse:scratch/gourry/cxl/compression/file_cleancache 87/98] mm/internal.h:2086:15: error: unknown type name 'rmap_t'
Date: Fri, 10 Jul 2026 21:06:13 +0800 [thread overview]
Message-ID: <202607102042.LZPwOQ3J-lkp@intel.com> (raw)
tree: https://github.com/gourryinverse/linux scratch/gourry/cxl/compression/file_cleancache
head: bcd0bfca5b64d6cbb5aadb07554b9bd218e0df85
commit: 6e2dd58311ea13f03bd4c1f38bd1d4d5818803ce [87/98] mm/migrate: re-install migrated write-fenced folios read-only
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20260710/202607102042.LZPwOQ3J-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260710/202607102042.LZPwOQ3J-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/202607102042.LZPwOQ3J-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from mm/filemap.c:54:
>> mm/internal.h:2086:15: error: unknown type name 'rmap_t'
2086 | static inline rmap_t migration_remap_rmap_flags(struct folio *folio,
| ^
>> mm/internal.h:2091:10: error: use of undeclared identifier 'RMAP_EXCLUSIVE'
2091 | return RMAP_EXCLUSIVE;
| ^
>> mm/internal.h:2092:9: error: use of undeclared identifier 'RMAP_NONE'; did you mean 'DMA_NONE'?
2092 | return RMAP_NONE;
| ^~~~~~~~~
| DMA_NONE
include/linux/dma-direction.h:9:2: note: 'DMA_NONE' declared here
9 | DMA_NONE = 3,
| ^
In file included from mm/filemap.c:54:
mm/internal.h:2096:10: error: unknown type name 'rmap_t'
2096 | rmap_t rmap_flags)
| ^
mm/internal.h:2105:50: error: use of undeclared identifier 'RMAP_EXCLUSIVE'
2105 | return !folio_test_anon(folio) || (rmap_flags & RMAP_EXCLUSIVE);
| ^
5 errors generated.
vim +/rmap_t +2086 mm/internal.h
2073
2074 /*
2075 * Resolve rmap flags and writability for a folio being re-installed present
2076 * after migration. Shared by remove_migration_pte() and remove_migration_pmd().
2077 *
2078 * Exclusivity is the single lever. Anon writability requires exclusive
2079 * ownership. A writable migration entry is only ever made for an exclusive anon
2080 * page; see make_writable_migration_entry() and the VM_WARN in
2081 * try_to_migrate_one(). A folio that must stay read-only, one on a write-fenced
2082 * node, is kept non-exclusive here, and writability falls out as false. The
2083 * next write then COW-promotes it off-node. This also makes the "writable anon
2084 * implies exclusive" invariant structural rather than a tripwire.
2085 */
> 2086 static inline rmap_t migration_remap_rmap_flags(struct folio *folio,
2087 bool was_read)
2088 {
2089 if (folio_test_anon(folio) && !was_read &&
2090 !node_write_fenced(folio_nid(folio)))
> 2091 return RMAP_EXCLUSIVE;
> 2092 return RMAP_NONE;
2093 }
2094
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-10 13:06 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=202607102042.LZPwOQ3J-lkp@intel.com \
--to=lkp@intel.com \
--cc=gourry@gourry.net \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox