From: Johannes Berg <johannes@sipsolutions.net>
To: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
Byungchul Park <byungchul.park@lge.com>
Subject: [PATCH v2 0/2] workqueue lockdep limitations/bugs
Date: Wed, 22 Aug 2018 11:49:02 +0200 [thread overview]
Message-ID: <20180822094904.15718-1-johannes@sipsolutions.net> (raw)
This addresses the first two issues.
The third problem is actually caught when the flush ever does
anything, but that might be rare depending on the circumstances,
so I still think it'd be nice to catch it somehow, but right now
I don't have the time to look into it.
johannes
v2:
* move the acquire/release into flush_work() where it used to be
* also re-add the acquire/release into flush_workqueue()
next reply other threads:[~2018-08-22 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 9:49 Johannes Berg [this message]
2018-08-22 9:49 ` [PATCH v2 1/2] workqueue: skip lockdep wq dependency in cancel_work_sync() Johannes Berg
2018-08-22 9:49 ` [PATCH v2 2/2] workqueue: re-add lockdep dependencies for flushing Johannes Berg
2018-08-22 15:32 ` [PATCH v2 0/2] workqueue lockdep limitations/bugs Tejun Heo
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=20180822094904.15718-1-johannes@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=byungchul.park@lge.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).