public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: peterz@infradead.org
Cc: mingo@redhat.com, tj@kernel.org, longman@redhat.com,
	johannes.berg@intel.com, linux-kernel@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH v4 13/15] locking/lockdep: Add support for dynamic keys
Date: Fri, 14 Dec 2018 09:20:02 -0800	[thread overview]
Message-ID: <1544808002.185366.414.camel@acm.org> (raw)
In-Reply-To: <20181211221321.196536-14-bvanassche@acm.org>

On Tue, 2018-12-11 at 14:13 -0800, Bart Van Assche wrote:
> +/*
> + * Unregister a dynamically allocated key. Must not be called from interrupt
> + * context. The caller must ensure that freeing @key only happens after an RCU
> + * grace period.
> + */
> +void lockdep_unregister_key(struct lock_class_key *key)
> +{
> +	struct hlist_head *hash_head = keyhashentry(key);
> +	struct lock_class_key *k;
> +	struct pending_free *pf;
> +	unsigned long flags;
> +	bool found = false;
> +
> +	might_sleep();
> +
> +	if (WARN_ON_ONCE(static_obj(key)))
> +		return;
> +
> +	pf = get_pending_free_lock(&flags);
> +	if (WARN_ON_ONCE(!pf))
> +		return;
> +	hlist_for_each_entry_rcu(k, hash_head, hash_entry) {
> +		if (k == key) {
> +			hlist_del_rcu(&k->hash_entry);
> +			found = true;
> +			break;
> +		}
> +	}
> +	WARN_ON_ONCE(!found);
> +	__lockdep_free_key_range(pf, key, 1);
> +	schedule_free_zapped_classes(pf);
> +	graph_unlock();
> +	raw_local_irq_restore(flags);
> +}
> +EXPORT_SYMBOL_GPL(lockdep_unregister_key);

Since is_dynamic_key() has been modified from using locking into using RCU, a
synchronize_rcu() call needs to be added at the end of lockdep_unregister_key().
I will repost this patch series if the 0-day test infrastructure is happy with
the new version.

Bart.

  reply	other threads:[~2018-12-14 17:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 22:13 [PATCH v4 00/15] locking/lockdep: Add support for dynamic keys Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 01/15] locking/lockdep: Fix required memory size reported if CONFIG_PROVE_LOCKING=n Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 02/15] locking/lockdep: Make zap_class() remove all matching lock order entries Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 03/15] locking/lockdep: Reorder struct lock_class members Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 04/15] locking/lockdep: Initialize the locks_before and locks_after lists earlier Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 05/15] locking/lockdep: Split lockdep_free_key_range() and lockdep_reset_lock() Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 06/15] locking/lockdep: Make it easy to detect whether or not inside a selftest Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 07/15] locking/lockdep: Free lock classes that are no longer in use Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 08/15] locking/lockdep: Reuse list entries " Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 09/15] locking/lockdep: Introduce lockdep_next_lockchain() and lock_chain_count() Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 10/15] locking/lockdep: Reuse lock chains that have been freed Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 11/15] locking/lockdep: Check data structure consistency Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 12/15] locking/lockdep: Verify whether lock objects are small enough to be used as class keys Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 13/15] locking/lockdep: Add support for dynamic keys Bart Van Assche
2018-12-14 17:20   ` Bart Van Assche [this message]
2018-12-11 22:13 ` [PATCH v4 14/15] kernel/workqueue: Use dynamic lockdep keys for workqueues Bart Van Assche
2018-12-11 22:13 ` [PATCH v4 15/15] lockdep tests: Test dynamic key registration 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=1544808002.185366.414.camel@acm.org \
    --to=bvanassche@acm.org \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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