From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Benjamin Berg <benjamin@sipsolutions.net>
Subject: Re: wireless locking simplifications
Date: Wed, 10 May 2023 13:25:51 +0200 [thread overview]
Message-ID: <ab3ddf836d89af4c559543c9d519f8dab394d684.camel@sipsolutions.net> (raw)
In-Reply-To: <f3471853cd7063a4bd2d783caa14706ee9115748.camel@sipsolutions.net>
On Fri, 2023-05-05 at 23:05 +0200, Johannes Berg wrote:
>
> + /* FIXME: can this be done better? */ \
> + WARN_ON_ONCE(strncmp(current->comm, "kworker/", 8)); \
Ah, also, is there a better way to do this? Not strictly needed, but
some kind of debug check that you're calling the right thing would be
nice.
(Unless we do the user mutex to workqueue thing :) )
johannes
prev parent reply other threads:[~2023-05-10 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 21:05 wireless locking simplifications Johannes Berg
2023-05-05 21:51 ` Tejun Heo
2023-05-08 16:06 ` Johannes Berg
2023-05-10 10:58 ` Johannes Berg
2023-05-10 11:11 ` Johannes Berg
2023-05-10 11:25 ` Johannes Berg [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=ab3ddf836d89af4c559543c9d519f8dab394d684.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benjamin@sipsolutions.net \
--cc=jiangshanlai@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tj@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