From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Sunil Dhamne <amitsd@google.com>
Cc: heikki.krogerus@linux.intel.com, badhri@google.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
kyletso@google.com, rdbabiera@google.com
Subject: Re: [PATCH v1] usb: roles: add lockdep class key to struct usb_role_switch
Date: Wed, 14 Aug 2024 06:49:36 +0200 [thread overview]
Message-ID: <2024081450-triage-glorious-cba5@gregkh> (raw)
In-Reply-To: <20240813224216.132619-1-amitsd@google.com>
On Tue, Aug 13, 2024 at 03:42:11PM -0700, Amit Sunil Dhamne wrote:
> There can be multiple role switch devices running on a platform. Given
> that lockdep is not capable of differentiating between locks of
> different instances, false positive warnings for circular locking are
> reported. To prevent this, register unique lockdep key for each of the
> individual instances.
>
> Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>
> ---
> drivers/usb/roles/class.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/usb/roles/class.c b/drivers/usb/roles/class.c
> index d7aa913ceb8a..807a8f18ec20 100644
> --- a/drivers/usb/roles/class.c
> +++ b/drivers/usb/roles/class.c
> @@ -11,6 +11,7 @@
> #include <linux/usb/role.h>
> #include <linux/property.h>
> #include <linux/device.h>
> +#include <linux/lockdep.h>
> #include <linux/module.h>
> #include <linux/mutex.h>
> #include <linux/slab.h>
> @@ -33,6 +34,10 @@ struct usb_role_switch {
> usb_role_switch_set_t set;
> usb_role_switch_get_t get;
> bool allow_userspace_control;
> +
> +#ifdef CONFIG_LOCKDEP
> + struct lock_class_key key;
> +#endif
Please do not put #ifdef lines in .c files, they are not needed for this
change to work properly, right?
checkpatch should have complained about this...
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-14 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 22:42 [PATCH v1] usb: roles: add lockdep class key to struct usb_role_switch Amit Sunil Dhamne
2024-08-14 4:49 ` Greg KH [this message]
2024-08-15 4:27 ` Amit Sunil Dhamne
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=2024081450-triage-glorious-cba5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amitsd@google.com \
--cc=badhri@google.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=kyletso@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdbabiera@google.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