From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
rcu@vger.kernel.org, lkft-triage@lists.linaro.org
Cc: Marco Elver <elver@google.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
fweisbec@gmail.com, Arnd Bergmann <arnd@arndb.de>
Subject: BUG: KCSAN: data-race in tick_nohz_next_event / tick_nohz_stop_tick
Date: Sat, 5 Dec 2020 00:33:51 +0530 [thread overview]
Message-ID: <CA+G9fYsHo-9tmxCKGticDowF8e3d1RkcLamapOgMQqeP6OdEEg@mail.gmail.com> (raw)
LKFT started testing KCSAN enabled kernel from the linux next tree.
Here we have found BUG: KCSAN: data-race in tick_nohz_next_event /
tick_nohz_stop_tick
This report is from an x86_64 machine clang-11 linux next 20201201.
Since we are running for the first time we do not call this regression.
[ 47.811425] BUG: KCSAN: data-race in tick_nohz_next_event /
tick_nohz_stop_tick
[ 47.818738]
[ 47.820239] write to 0xffffffffa4cbe920 of 4 bytes by task 0 on cpu 2:
[ 47.826766] tick_nohz_stop_tick+0x8b/0x310
[ 47.830951] tick_nohz_idle_stop_tick+0xcb/0x170
[ 47.835571] do_idle+0x193/0x250
[ 47.838804] cpu_startup_entry+0x25/0x30
[ 47.842728] start_secondary+0xa0/0xb0
[ 47.846482] secondary_startup_64_no_verify+0xc2/0xcb
[ 47.851531]
[ 47.853034] read to 0xffffffffa4cbe920 of 4 bytes by task 0 on cpu 3:
[ 47.859473] tick_nohz_next_event+0x165/0x1e0
[ 47.863831] tick_nohz_get_sleep_length+0x94/0xd0
[ 47.868539] menu_select+0x250/0xac0
[ 47.872116] cpuidle_select+0x47/0x50
[ 47.875781] do_idle+0x17c/0x250
[ 47.879015] cpu_startup_entry+0x25/0x30
[ 47.882942] start_secondary+0xa0/0xb0
[ 47.886694] secondary_startup_64_no_verify+0xc2/0xcb
[ 47.891743]
[ 47.893234] Reported by Kernel Concurrency Sanitizer on:
[ 47.898541] CPU: 3 PID: 0 Comm: swapper/3 Not tainted
5.10.0-rc6-next-20201201 #2
[ 47.906017] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
2.2 05/23/2018
metadata:
git_repo: https://gitlab.com/aroxell/lkft-linux-next
target_arch: x86
toolchain: clang-11
git_describe: next-20201201
download_url: https://builds.tuxbuild.com/1l8eiWgGMi6W4aDobjAAlOleFVl/
Full test log link,
https://lkft.validation.linaro.org/scheduler/job/2002643#L2019
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2020-12-04 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 19:03 Naresh Kamboju [this message]
2020-12-04 19:53 ` BUG: KCSAN: data-race in tick_nohz_next_event / tick_nohz_stop_tick Marco Elver
2020-12-05 18:18 ` Thomas Gleixner
2020-12-05 23:47 ` Thomas Gleixner
2020-12-07 12:23 ` Marco Elver
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=CA+G9fYsHo-9tmxCKGticDowF8e3d1RkcLamapOgMQqeP6OdEEg@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=arnd@arndb.de \
--cc=elver@google.com \
--cc=fweisbec@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).