From: Tejun Heo <tj@kernel.org>
To: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: linux-kernel@vger.kernel.org, Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: [BUG] KCSAN: data-race in process_one_work / process_one_work
Date: Tue, 22 Aug 2023 09:52:24 -1000 [thread overview]
Message-ID: <ZOUR-Apz2Tws4d2c@slm.duckdns.org> (raw)
In-Reply-To: <4ef130ef-b37b-2564-3cb3-6a930b2f729b@alu.unizg.hr>
On Fri, Aug 18, 2023 at 01:58:27PM +0200, Mirsad Todorovac wrote:
> Just as an exercise, this seems to work, but it is probably not very clean and not very scalable:
pwq is already per-cpu. It's not strictly accessed per-cpu because workers
can go unbound but given that it's a stat counter, that doesn't really
matter all that much. Sounds like it should be marked so that kcsan ignores
it.
Thanks.
--
tejun
next prev parent reply other threads:[~2023-08-22 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 19:24 [BUG] KCSAN: data-race in process_one_work / process_one_work Mirsad Todorovac
2023-08-17 21:59 ` Tejun Heo
2023-08-18 6:27 ` Mirsad Todorovac
2023-08-18 8:10 ` Mirsad Todorovac
2023-08-18 11:58 ` Mirsad Todorovac
2023-08-22 19:52 ` Tejun Heo [this message]
2023-08-23 9:04 ` Mirsad Todorovac
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=ZOUR-Apz2Tws4d2c@slm.duckdns.org \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
/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