From: kernel test robot <lkp@intel.com>
To: Brendan Jackman <jackmanb@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [bjackman:asi/next 27/49] include/linux/set_memory.h:77:20: error: redefinition of 'direct_map_sensitive'
Date: Wed, 12 Nov 2025 07:46:33 +0800 [thread overview]
Message-ID: <202511120744.Ej8ITYYu-lkp@intel.com> (raw)
tree: https://github.com/bjackman/linux asi/next
head: 3c0474df6f211ae4eebffa6f5538335687dd9e0b
commit: c1f37f806e373cf7de31395a0cb72c0e11a1593a [27/49] mm/asi: bad_page() when ASI mappings are wrong
config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20251112/202511120744.Ej8ITYYu-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251112/202511120744.Ej8ITYYu-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/202511120744.Ej8ITYYu-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/filter.h:19,
from kernel/extable.c:14:
include/linux/set_memory.h:73:5: error: redefinition of 'set_direct_map_sensitive'
73 | int set_direct_map_sensitive(struct page *page, unsigned long nr, bool sensitive)
| ^~~~~~~~~~~~~~~~~~~~~~~~
include/linux/set_memory.h:48:19: note: previous definition of 'set_direct_map_sensitive' with type 'int(struct page *, long unsigned int, bool)' {aka 'int(struct page *, long unsigned int, _Bool)'}
48 | static inline int set_direct_map_sensitive(struct page *page,
| ^~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/set_memory.h:77:20: error: redefinition of 'direct_map_sensitive'
77 | static inline bool direct_map_sensitive(struct page *page) { return false; }
| ^~~~~~~~~~~~~~~~~~~~
include/linux/set_memory.h:54:20: note: previous definition of 'direct_map_sensitive' with type 'bool(struct page *)' {aka '_Bool(struct page *)'}
54 | static inline bool direct_map_sensitive(struct page *page) { return false; }
| ^~~~~~~~~~~~~~~~~~~~
vim +/direct_map_sensitive +77 include/linux/set_memory.h
d253ca0c3865a8 Rick Edgecombe 2019-04-25 69
6dd7718570d9a8 Brendan Jackman 2025-09-11 70 /* Without ASI, sensitivity ops are a nop regardless of ARCH_HAS_SET_DIRECT_MAP. */
6dd7718570d9a8 Brendan Jackman 2025-09-11 71 #ifndef CONFIG_MITIGATION_ADDRESS_SPACE_ISOLATION
6dd7718570d9a8 Brendan Jackman 2025-09-11 72 static inline
6dd7718570d9a8 Brendan Jackman 2025-09-11 73 int set_direct_map_sensitive(struct page *page, unsigned long nr, bool sensitive)
6dd7718570d9a8 Brendan Jackman 2025-09-11 74 {
6dd7718570d9a8 Brendan Jackman 2025-09-11 75 return 0;
6dd7718570d9a8 Brendan Jackman 2025-09-11 76 }
6dd7718570d9a8 Brendan Jackman 2025-09-11 @77 static inline bool direct_map_sensitive(struct page *page) { return false; }
6dd7718570d9a8 Brendan Jackman 2025-09-11 78 #endif /* !CONFIG_MITIGATION_ADDRESS_SPACE_ISOLATION */
6dd7718570d9a8 Brendan Jackman 2025-09-11 79
:::::: The code at line 77 was first introduced by commit
:::::: 6dd7718570d9a84ab2563fd3e9d696935dfd904b mm/asi: support changing pageblock sensitivity
:::::: TO: Brendan Jackman <jackmanb@google.com>
:::::: CC: Brendan Jackman <jackmanb@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-11 23:46 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=202511120744.Ej8ITYYu-lkp@intel.com \
--to=lkp@intel.com \
--cc=jackmanb@google.com \
--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 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.