From: Philip Li <philip.li@intel.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: kernel test robot <lkp@intel.com>,
Christian Schrrefl <chrisi.schrefl@gmail.com>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Subject: Re: error: kernel-address sanitizer is not supported for this target
Date: Tue, 7 Apr 2026 20:31:41 +0800 [thread overview]
Message-ID: <adT5La8XYtP6zTH0@rli9-mobl> (raw)
In-Reply-To: <adTAvyb_tRD6jDzX@google.com>
On Tue, Apr 07, 2026 at 08:30:55AM +0000, Alice Ryhl wrote:
> On Tue, Apr 07, 2026 at 11:58:00AM +0800, kernel test robot wrote:
> > Hi Christian,
> >
> > FYI, the error/warning still remains.
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 3aae9383f42f687221c011d7ee87529398e826b3
> > commit: ccb8ce526807fcbd4578d6619100d8ec48769ea8 ARM: 9441/1: rust: Enable Rust support for ARMv7
> > date: 1 year ago
> > config: arm-randconfig-r061-20260405 (https://download.01.org/0day-ci/archive/20260405/202604051027.NPt0H2Dy-lkp@intel.com/config)
> > compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project c80443cd37b2e2788cba67ffa180a6331e5f0791)
> > rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260405/202604051027.NPt0H2Dy-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
> > | Fixes: ccb8ce526807 ("ARM: 9441/1: rust: Enable Rust support for ARMv7")
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202604051027.NPt0H2Dy-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > scripts/dtc/dtc-lexer.lex.c:630:12: warning: variable 'dts_version' set but not used [-Wunused-but-set-global]
> > 630 | static int dts_version = 1;
> > | ^
> > 1 warning generated.
> > scripts/sorttable.c:399:12: warning: variable 'long_size' set but not used [-Wunused-but-set-global]
> > 399 | static int long_size;
> > | ^
> > 1 warning generated.
> > In file included from <built-in>:3:
> > In file included from include/linux/compiler_types.h:171:
> > include/linux/compiler-clang.h:28:9: warning: '__SANITIZE_ADDRESS__' macro redefined [-Wmacro-redefined]
> > 28 | #define __SANITIZE_ADDRESS__
> > | ^
> > <built-in>:367:9: note: previous definition is here
> > 367 | #define __SANITIZE_ADDRESS__ 1
> > | ^
> > >> error: kernel-address sanitizer is not supported for this target
>
> Like [1], this would probably be fixed by moving away from the linux
> target, as kernel-address is a bare-metal only sanitizer.
Thanks for the info, I will configure the bot to avoid reporting this commit again.
>
> [1]: https://lore.kernel.org/all/acUGAsjYvNvTEO92@google.com/
>
next prev parent reply other threads:[~2026-04-07 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 3:58 kernel test robot
2026-04-07 8:30 ` Alice Ryhl
2026-04-07 12:31 ` Philip Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-03 20:06 kernel test robot
2025-06-23 12:51 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=adT5La8XYtP6zTH0@rli9-mobl \
--to=philip.li@intel.com \
--cc=aliceryhl@google.com \
--cc=chrisi.schrefl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®