From: kernel test robot <lkp@intel.com>
To: Patricia Alfonso <trishalfonso@google.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Richard Weinberger <richard@nod.at>,
Vincent Whitchurch <vincent.whitchurch@axis.com>,
David Gow <davidgow@google.com>,
Johannes Berg <johannes@sipsolutions.net>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>
Subject: mm/kasan/kasan.h:485:2: error: #error kasan_arch_is_ready only works in KASAN generic outline mode!
Date: Mon, 11 Sep 2023 05:36:33 +0800 [thread overview]
Message-ID: <202309110520.SZfumSJ2-lkp@intel.com> (raw)
Hi Patricia,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 1548b060d6f32a00a2f7e2c11328205fb66fc4fa
commit: 5b301409e8bc5d7fad2ee138be44c5c529dd0874 UML: add support for KASAN under x86_64
date: 1 year, 2 months ago
config: um-randconfig-r026-20230911 (https://download.01.org/0day-ci/archive/20230911/202309110520.SZfumSJ2-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230911/202309110520.SZfumSJ2-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/202309110520.SZfumSJ2-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from mm/kasan/quarantine.c:25:
>> mm/kasan/kasan.h:485:2: error: #error kasan_arch_is_ready only works in KASAN generic outline mode!
485 | #error kasan_arch_is_ready only works in KASAN generic outline mode!
| ^~~~~
vim +485 mm/kasan/kasan.h
e2db1a9aa38149 Andrey Konovalov 2021-02-25 481
af3751f3c2b628 Daniel Axtens 2021-06-28 482 #ifndef kasan_arch_is_ready
af3751f3c2b628 Daniel Axtens 2021-06-28 483 static inline bool kasan_arch_is_ready(void) { return true; }
af3751f3c2b628 Daniel Axtens 2021-06-28 484 #elif !defined(CONFIG_KASAN_GENERIC) || !defined(CONFIG_KASAN_OUTLINE)
af3751f3c2b628 Daniel Axtens 2021-06-28 @485 #error kasan_arch_is_ready only works in KASAN generic outline mode!
af3751f3c2b628 Daniel Axtens 2021-06-28 486 #endif
af3751f3c2b628 Daniel Axtens 2021-06-28 487
:::::: The code at line 485 was first introduced by commit
:::::: af3751f3c2b6282bebcb56c35bbe4c8b671f80aa kasan: allow architectures to provide an outline readiness check
:::::: TO: Daniel Axtens <dja@axtens.net>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-09-10 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 21:36 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-28 12:14 mm/kasan/kasan.h:485:2: error: #error kasan_arch_is_ready only works in KASAN generic outline mode! kernel test robot
2024-03-03 23:39 kernel test robot
2024-01-28 5:34 kernel test robot
2023-07-30 22:49 kernel test robot
2023-06-26 7:16 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=202309110520.SZfumSJ2-lkp@intel.com \
--to=lkp@intel.com \
--cc=andreyknvl@gmail.com \
--cc=davidgow@google.com \
--cc=dvyukov@google.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard@nod.at \
--cc=trishalfonso@google.com \
--cc=vincent.whitchurch@axis.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