From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Marco Elver <elver@google.com>,
Justin Stitt <justinstitt@google.com>
Subject: [linux-next:master 4528/5901] kernel/rcu/update.c:319:1: warning: 'no_sanitize' attribute directive ignored
Date: Fri, 9 Feb 2024 18:51:16 +0800 [thread overview]
Message-ID: <202402091848.rFySykYW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 445a555e0623387fa9b94e68e61681717e70200a
commit: 2c312f328894df239807173b5b34f1db4cfc397f [4528/5901] ubsan: Reintroduce signed overflow sanitizer
config: um-randconfig-001-20240209 (https://download.01.org/0day-ci/archive/20240209/202402091848.rFySykYW-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240209/202402091848.rFySykYW-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/202402091848.rFySykYW-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/rcu/update.c:319:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
--
>> kernel/locking/lockdep.c:883:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
kernel/locking/lockdep.c:4365:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
kernel/locking/lockdep.c:4432:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
kernel/locking/lockdep.c:5199:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
kernel/locking/lockdep.c:5585:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
kernel/locking/lockdep.c:5810:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
--
>> kernel/locking/irqflag-debug.c:8:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
--
>> kernel/time/timekeeping.c:1045:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
--
In file included from kernel/sched/build_policy.c:43:0:
>> kernel/sched/idle.c:53:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
kernel/sched/idle.c:90:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes]
{
^
vim +/no_sanitize +319 kernel/rcu/update.c
24ef659a857c3c kernel/rcu/update.c Paul E. McKenney 2013-10-28 317
ff5c4f5cad3306 kernel/rcu/update.c Thomas Gleixner 2020-03-13 318 noinstr int notrace debug_lockdep_rcu_enabled(void)
bc293d62b26ec5 kernel/rcupdate.c Paul E. McKenney 2010-04-15 @319 {
3066820034b5dd kernel/rcu/update.c Paul E. McKenney 2021-04-05 320 return rcu_scheduler_active != RCU_SCHEDULER_INACTIVE && READ_ONCE(debug_locks) &&
bc293d62b26ec5 kernel/rcupdate.c Paul E. McKenney 2010-04-15 321 current->lockdep_recursion == 0;
bc293d62b26ec5 kernel/rcupdate.c Paul E. McKenney 2010-04-15 322 }
bc293d62b26ec5 kernel/rcupdate.c Paul E. McKenney 2010-04-15 323 EXPORT_SYMBOL_GPL(debug_lockdep_rcu_enabled);
bc293d62b26ec5 kernel/rcupdate.c Paul E. McKenney 2010-04-15 324
:::::: The code at line 319 was first introduced by commit
:::::: bc293d62b26ec590afc90a9e0a31c45d355b7bd8 rcu: Make RCU lockdep check the lockdep_recursion variable
:::::: TO: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
:::::: CC: Ingo Molnar <mingo@elte.hu>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-09 10:51 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=202402091848.rFySykYW-lkp@intel.com \
--to=lkp@intel.com \
--cc=elver@google.com \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--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