From: cw00.choi@samsung.com (Chanwoo Choi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] extcon: Fix missing locking when [un]registering notifiers
Date: Mon, 23 Mar 2015 12:00:24 +0900 [thread overview]
Message-ID: <550F81C8.2080307@samsung.com> (raw)
In-Reply-To: <1426955184-3727-1-git-send-email-hdegoede@redhat.com>
Hi Hans,
Looks good to me of this patch.
But,
I have some comment. You have to send extcon patch to linux-kernel at vger.kerne.org mailing list
but you missed it. Also if you fixes extcon driver, you should develop them on extcon git repository
because extcon-class.c was renamed to extcon.c. I added the extcon git repository and branch name.
- git repo : http://git.kernel.org/cgit/linux/kernel/git/chanwoo/extcon.git/
- branch : extcon-next
After I modified this patch without apply conflict personally,
I applied it on extcon-next branch.
Thanks,
Chanwoo Choi
On 03/22/2015 01:26 AM, Hans de Goede wrote:
> Since extcon-class.c is using raw_notifiers it must protect the notifier
> list itself when [un]registering notifiers to avoid the list changing while
> extcon_update_state is walking the list (through raw_notifier_call_chain).
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> drivers/extcon/extcon-class.c | 35 +++++++++++++++++++++++++++++++----
> 1 file changed, 31 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/extcon/extcon-class.c b/drivers/extcon/extcon-class.c
> index 8319f25..b079c41 100644
> --- a/drivers/extcon/extcon-class.c
> +++ b/drivers/extcon/extcon-class.c
> @@ -444,6 +444,9 @@ int extcon_register_interest(struct extcon_specific_cable_nb *obj,
> const char *extcon_name, const char *cable_name,
> struct notifier_block *nb)
> {
> + unsigned long flags;
> + int ret;
> +
> if (!obj || !cable_name || !nb)
> return -EINVAL;
>
> @@ -461,8 +464,11 @@ int extcon_register_interest(struct extcon_specific_cable_nb *obj,
>
> obj->internal_nb.notifier_call = _call_per_cable;
>
> - return raw_notifier_chain_register(&obj->edev->nh,
> + spin_lock_irqsave(&obj->edev->lock, flags);
> + ret = raw_notifier_chain_register(&obj->edev->nh,
> &obj->internal_nb);
> + spin_unlock_irqrestore(&obj->edev->lock, flags);
> + return ret;
> } else {
> struct class_dev_iter iter;
> struct extcon_dev *extd;
> @@ -495,10 +501,17 @@ EXPORT_SYMBOL_GPL(extcon_register_interest);
> */
> int extcon_unregister_interest(struct extcon_specific_cable_nb *obj)
> {
> + unsigned long flags;
> + int ret;
> +
> if (!obj)
> return -EINVAL;
>
> - return raw_notifier_chain_unregister(&obj->edev->nh, &obj->internal_nb);
> + spin_lock_irqsave(&obj->edev->lock, flags);
> + ret = raw_notifier_chain_unregister(&obj->edev->nh, &obj->internal_nb);
> + spin_unlock_irqrestore(&obj->edev->lock, flags);
> +
> + return ret;
> }
> EXPORT_SYMBOL_GPL(extcon_unregister_interest);
>
> @@ -515,7 +528,14 @@ EXPORT_SYMBOL_GPL(extcon_unregister_interest);
> int extcon_register_notifier(struct extcon_dev *edev,
> struct notifier_block *nb)
> {
> - return raw_notifier_chain_register(&edev->nh, nb);
> + unsigned long flags;
> + int ret;
> +
> + spin_lock_irqsave(&edev->lock, flags);
> + ret = raw_notifier_chain_register(&edev->nh, nb);
> + spin_unlock_irqrestore(&edev->lock, flags);
> +
> + return ret;
> }
> EXPORT_SYMBOL_GPL(extcon_register_notifier);
>
> @@ -527,7 +547,14 @@ EXPORT_SYMBOL_GPL(extcon_register_notifier);
> int extcon_unregister_notifier(struct extcon_dev *edev,
> struct notifier_block *nb)
> {
> - return raw_notifier_chain_unregister(&edev->nh, nb);
> + unsigned long flags;
> + int ret;
> +
> + spin_lock_irqsave(&edev->lock, flags);
> + ret = raw_notifier_chain_unregister(&edev->nh, nb);
> + spin_unlock_irqrestore(&edev->lock, flags);
> +
> + return ret;
> }
> EXPORT_SYMBOL_GPL(extcon_unregister_notifier);
>
>
prev parent reply other threads:[~2015-03-23 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 16:26 [PATCH] extcon: Fix missing locking when [un]registering notifiers Hans de Goede
2015-03-23 3:00 ` Chanwoo Choi [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=550F81C8.2080307@samsung.com \
--to=cw00.choi@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.