From: kernel test robot <oliver.sang@intel.com>
To: Anna-Maria Behnsen <anna-maria@linutronix.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [timers] fe90c5ba88: BUG:KCSAN:data-race_in_timer_expire_remote/timer_recalc_next_expiry
Date: Wed, 30 Oct 2024 13:38:34 +0800 [thread overview]
Message-ID: <202410301205.ef8e9743-lkp@intel.com> (raw)
Hello,
we understand this is a renaming commit, which causes below KCSAN report
difference.
d7b01b81bd2dad57 fe90c5ba88ad43d42acefb21b57
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
20:300 -7% :300 dmesg.BUG:KCSAN:data-race_in_next_expiry_recalc/run_timer_softirq
11:300 -4% :300 dmesg.BUG:KCSAN:data-race_in_next_expiry_recalc/timer_expire_remote
:300 6% 18:300 dmesg.BUG:KCSAN:data-race_in_run_timer_softirq/timer_recalc_next_expiry
:300 5% 14:300 dmesg.BUG:KCSAN:data-race_in_timer_expire_remote/timer_recalc_next_expiry
we made out this report to let you be aware that the possible issues in
related code. then it's up to you to see if these issues need to care.
if you need us do more tests or test some patch, please let us know. thanks!
below is full report FYI.
kernel test robot noticed "BUG:KCSAN:data-race_in_timer_expire_remote/timer_recalc_next_expiry" on:
commit: fe90c5ba88ad43d42acefb21b57df837be86a61a ("timers: Rename next_expiry_recalc() to be unique")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 81983758430957d9a5cb3333fe324fd70cf63e7e]
[test failed on linux-next/master dec9255a128e19c5fcc3bdb18175d78094cc624d]
in testcase: trinity
version:
with following parameters:
runtime: 300s
group: group-03
nr_groups: 5
config: x86_64-randconfig-073-20241025
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202410301205.ef8e9743-lkp@intel.com
[ 131.612941][ C0] ==================================================================
[ 131.614221][ C0] BUG: KCSAN: data-race in timer_expire_remote / timer_recalc_next_expiry
[ 131.615526][ C0]
[ 131.615932][ C0] write (marked) to 0xffff88842fd1d4d0 of 8 bytes by interrupt on cpu 1:
[ 131.617229][ C0] timer_recalc_next_expiry (kernel/time/timer.c:1969 (discriminator 2))
[ 131.618104][ C0] __run_timers (kernel/time/timer.c:2399)
[ 131.618818][ C0] run_timer_softirq (kernel/time/timer.c:2431 kernel/time/timer.c:2423 kernel/time/timer.c:2439 kernel/time/timer.c:2449)
[ 131.619581][ C0] handle_softirqs (arch/x86/include/asm/jump_label.h:27 include/linux/jump_label.h:207 include/trace/events/irq.h:142 kernel/softirq.c:555)
[ 131.620321][ C0] __irq_exit_rcu (kernel/softirq.c:589 kernel/softirq.c:428 kernel/softirq.c:637)
[ 131.621036][ C0] irq_exit_rcu (kernel/softirq.c:651)
[ 131.621719][ C0] sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1043 arch/x86/kernel/apic/apic.c:1043)
[ 131.622596][ C0] asm_sysvec_apic_timer_interrupt (arch/x86/include/asm/idtentry.h:702)
[ 131.623523][ C0] default_idle (arch/x86/include/asm/irqflags.h:37 arch/x86/include/asm/irqflags.h:92 arch/x86/kernel/process.c:743)
[ 131.628342][ C0] default_idle_call (include/linux/cpuidle.h:143 kernel/sched/idle.c:118)
[ 131.629091][ C0] cpuidle_idle_call (kernel/sched/idle.c:186)
[ 131.629892][ C0] do_idle (kernel/sched/idle.c:328)
[ 131.630536][ C0] cpu_startup_entry (kernel/sched/idle.c:423 (discriminator 1))
[ 131.631318][ C0] start_secondary (arch/x86/kernel/smpboot.c:224 arch/x86/kernel/smpboot.c:291)
[ 131.632082][ C0] common_startup_64 (arch/x86/kernel/head_64.S:421)
[ 131.632864][ C0]
[ 131.633255][ C0] read to 0xffff88842fd1d4d0 of 8 bytes by interrupt on cpu 0:
[ 131.634436][ C0] timer_expire_remote (kernel/time/timer.c:2425 kernel/time/timer.c:2182)
[ 131.635247][ C0] tmigr_handle_remote_up (arch/x86/include/asm/irqflags.h:26 arch/x86/include/asm/irqflags.h:87 arch/x86/include/asm/irqflags.h:147 kernel/time/timer_migration.c:947 kernel/time/timer_migration.c:1021)
[ 131.636092][ C0] tmigr_handle_remote (kernel/time/timer_migration.c:533 kernel/time/timer_migration.c:1080)
[ 131.636875][ C0] run_timer_softirq (kernel/time/timer.c:2455)
[ 131.637671][ C0] handle_softirqs (arch/x86/include/asm/jump_label.h:27 include/linux/jump_label.h:207 include/trace/events/irq.h:142 kernel/softirq.c:555)
[ 131.638358][ C0] __irq_exit_rcu (kernel/softirq.c:589 kernel/softirq.c:428 kernel/softirq.c:637)
[ 131.639083][ C0] irq_exit_rcu (kernel/softirq.c:651)
[ 131.639737][ C0] sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1043 arch/x86/kernel/apic/apic.c:1043)
[ 131.640600][ C0] asm_sysvec_apic_timer_interrupt (arch/x86/include/asm/idtentry.h:702)
[ 131.641494][ C0] mtree_range_walk (lib/maple_tree.c:788 lib/maple_tree.c:2792)
[ 131.642226][ C0] mas_walk (lib/maple_tree.c:265 lib/maple_tree.c:4907)
[ 131.642874][ C0] lock_vma_under_rcu (mm/memory.c:5996)
[ 131.643627][ C0] do_user_addr_fault (arch/x86/mm/fault.c:1330)
[ 131.644422][ C0] exc_page_fault (arch/x86/include/asm/irqflags.h:26 arch/x86/include/asm/irqflags.h:87 arch/x86/include/asm/irqflags.h:147 arch/x86/mm/fault.c:1489 arch/x86/mm/fault.c:1539)
[ 131.645154][ C0] asm_exc_page_fault (arch/x86/include/asm/idtentry.h:623)
[ 131.645911][ C0]
[ 131.646292][ C0] value changed: 0x00000000ffff5991 -> 0x00000000ffff5bc0
[ 131.647367][ C0]
[ 131.647755][ C0] Reported by Kernel Concurrency Sanitizer on:
[ 131.648646][ C0] CPU: 0 UID: 0 PID: 518 Comm: run Not tainted 6.11.0-rc1-00042-gfe90c5ba88ad #1 cf6842c5d2875ed08b01af3196bb8a34c3713203
[ 131.650536][ C0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 131.652009][ C0] ==================================================================
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241030/202410301205.ef8e9743-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-10-30 5:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 5:38 kernel test robot [this message]
2024-10-30 7:53 ` timers: Add missing READ_ONCE() in __run_timer_base() Thomas Gleixner
2024-10-31 9:44 ` Frederic Weisbecker
2024-10-31 10:54 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
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=202410301205.ef8e9743-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=tglx@linutronix.de \
/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