From: Bart Van Assche <bvanassche@acm.org>
To: mingo@redhat.com
Cc: linux-kernel@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH 0/2] locking/lockdep: Support dynamic lockdep keys
Date: Fri, 9 Nov 2018 15:46:43 -0800 [thread overview]
Message-ID: <20181109234645.10530-1-bvanassche@acm.org> (raw)
Hi Ingo,
As you may know some false positive lockdep reports are the result of the
requirement to associate the same static lockdep key with all instances
of a locking object. Recently I encountered a lockdep false positive for
which I found no elegant way to suppress it other than by modifying the
lockdep implementation. Hence this series with two patches: one that
modifies lockdep and another patch that shows the false positive I and
others ran into and that also shows how to suppress that false positive.
Please keep in mind that I'm not a lockdep expert and hence that I'm not
sure whether the approach of patch 1/2 is correct.
Thanks,
Bart.
Bart Van Assche (2):
locking/lockdep: Add support for dynamic depmaps and keys
kernel/workqueue: Use dynamic lockdep keys for workqueues
include/linux/lockdep.h | 2 ++
include/linux/workqueue.h | 28 ++++-------------------
kernel/locking/lockdep.c | 16 ++++++++++---
kernel/workqueue.c | 48 ++++++++++++++++++++++++++++++++-------
4 files changed, 59 insertions(+), 35 deletions(-)
--
2.19.1.930.g4563a0d9d0-goog
next reply other threads:[~2018-11-09 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 23:46 Bart Van Assche [this message]
2018-11-09 23:46 ` [PATCH 1/2] locking/lockdep: Add support for dynamic depmaps and keys Bart Van Assche
2018-11-10 13:55 ` Peter Zijlstra
2018-11-19 21:55 ` Bart Van Assche
2018-11-09 23:46 ` [PATCH 2/2] kernel/workqueue: Use dynamic lockdep keys for workqueues Bart Van Assche
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=20181109234645.10530-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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).