linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org, lkft-triage@lists.linaro.org,
	rcu@vger.kernel.org, kasan-dev <kasan-dev@googlegroups.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Marco Elver <elver@google.com>, Ingo Molnar <mingo@redhat.com>,
	Will Deacon <will@kernel.org>, Lee Jones <lee.jones@linaro.org>,
	Thierry Reding <treding@nvidia.com>,
	mathias.nyman@linux.intel.com, Qian Cai <cai@lca.pw>
Subject: Re: BUG: KCSAN: data-race in mutex_spin_on_owner+0xef/0x1b0
Date: Mon, 7 Dec 2020 12:51:15 +0100	[thread overview]
Message-ID: <20201207115115.GL3040@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+G9fYuJF-L+qHJ3ufqD+M2w20LgeqMC0rhqv7oZagOA7iJMDg@mail.gmail.com>

On Fri, Dec 04, 2020 at 11:51:39PM +0530, Naresh Kamboju wrote:
> LKFT started testing KCSAN enabled kernel from the linux next tree.
> Here we have found BUG: KCSAN: data-race in mutex_spin_on_owner
> and several more KCSAN BUGs.
> 
> 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.
> 
> [    4.745161] usbcore: registered new interface driver cdc_ether
> [    4.751281] ==================================================================
> [    4.756653] usbcore: registered new interface driver net1080
> [    4.752139] BUG: KCSAN: data-race in mutex_spin_on_owner+0xef/0x1b0

At the very least run your splat through ./scripts/decode_stacktrace.sh

It's impossible to know what the thing is complaining about. I suspect
this is one of those known KCSAN 'bugs' where it can't tell a load+cmp0
is perfectly fine.

      reply	other threads:[~2020-12-07 11:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 18:21 BUG: KCSAN: data-race in mutex_spin_on_owner+0xef/0x1b0 Naresh Kamboju
2020-12-07 11:51 ` Peter Zijlstra [this message]

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=20201207115115.GL3040@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=cai@lca.pw \
    --cc=elver@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kasan-dev@googlegroups.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=mingo@redhat.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=treding@nvidia.com \
    --cc=will@kernel.org \
    /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).