From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: kasan-dev <kasan-dev@googlegroups.com>,
open list <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
linux-nfs@vger.kernel.org, lkft-triage@lists.linaro.org,
rcu@vger.kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
chuck.lever@oracle.com, bfields@fieldses.org,
anna.schumaker@netapp.com, trond.myklebust@hammerspace.com,
"Paul E. McKenney" <paulmck@kernel.org>,
Marco Elver <elver@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Subject: BUG: KCSAN: data-race in __rpc_do_wake_up_task_on_wq / xprt_request_transmit
Date: Sat, 5 Dec 2020 00:05:02 +0530 [thread overview]
Message-ID: <CA+G9fYvhvZtDYVBo4kj9OkKY_vVFSa6EbWz99iCmRPojExRieA@mail.gmail.com> (raw)
LKFT started testing KCSAN enabled kernel from the linux next tree.
Here we have found BUG: KCSAN: data-race in
__rpc_do_wake_up_task_on_wq / xprt_request_transmit
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.
[ 17.316725] BUG: KCSAN: data-race in __rpc_do_wake_up_task_on_wq /
xprt_request_transmit
[ 17.324821]
[ 17.326322] write to 0xffff90a801de6a9c of 2 bytes by task 142 on cpu 1:
[ 17.333022] __rpc_do_wake_up_task_on_wq+0x295/0x350
[ 17.337987] rpc_wake_up_queued_task+0x99/0xc0
[ 17.342432] xprt_complete_rqst+0xef/0x100
[ 17.346533] xs_read_stream+0x9c6/0xc40
[ 17.350370] xs_stream_data_receive+0x60/0x130
[ 17.354819] xs_stream_data_receive_workfn+0x5c/0x90
[ 17.359784] process_one_work+0x4a6/0x830
[ 17.363795] worker_thread+0x5f7/0xaa0
[ 17.367548] kthread+0x20b/0x220
[ 17.370780] ret_from_fork+0x22/0x30
[ 17.374359]
[ 17.375858] read to 0xffff90a801de6a9c of 2 bytes by task 249 on cpu 3:
[ 17.382473] xprt_request_transmit+0x389/0x7a0
[ 17.386919] xprt_transmit+0xfe/0x250
[ 17.390583] call_transmit+0x10d/0x120
[ 17.394337] __rpc_execute+0x12d/0x700
[ 17.398089] rpc_async_schedule+0x59/0x90
[ 17.402100] process_one_work+0x4a6/0x830
[ 17.406114] worker_thread+0x5f7/0xaa0
[ 17.409868] kthread+0x20b/0x220
[ 17.413099] ret_from_fork+0x22/0x30
[ 17.416675]
[ 17.418167] Reported by Kernel Concurrency Sanitizer on:
[ 17.423475] CPU: 3 PID: 249 Comm: kworker/u8:1 Not tainted
5.10.0-rc6-next-20201201 #2
[ 17.431385] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
2.2 05/23/2018
[ 17.438778] Workqueue: rpciod rpc_async_schedule
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#L1005
--
Linaro LKFT
https://lkft.linaro.org
reply other threads:[~2020-12-04 18:36 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=CA+G9fYvhvZtDYVBo4kj9OkKY_vVFSa6EbWz99iCmRPojExRieA@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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).