From: Marcel Holtmann <marcel@holtmann.org>
To: David Herrmann <dh.herrmann@googlemail.com>
Cc: linux-bluetooth@vger.kernel.org, padovan@profusion.mobi
Subject: Re: [PATCH 1/2] Bluetooth: bcm203x: Fix race condition on disconnect
Date: Wed, 26 Oct 2011 10:57:07 +0200 [thread overview]
Message-ID: <1319619427.15441.254.camel@aeonflux> (raw)
In-Reply-To: <1319570016-7439-1-git-send-email-dh.herrmann@googlemail.com>
Hi David,
> When disconnecting a bcm203x device we kill and destroy the usb-urb, however,
> there might still be a pending work-structure which resubmits the now invalid
> urb. To avoid this race condition, we simply set a shutdown-flag and
> synchronously kill the worker first.
>
> This also adds a comment to all schedule_work()s, as it is really not clear
> that they are used as replacement for short timers (which can be seen in the git
> history).
>
> Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
> ---
> drivers/bluetooth/bcm203x.c | 12 ++++++++++++
> 1 files changed, 12 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/bluetooth/bcm203x.c b/drivers/bluetooth/bcm203x.c
> index 8b1b643..6b42732 100644
> --- a/drivers/bluetooth/bcm203x.c
> +++ b/drivers/bluetooth/bcm203x.c
> @@ -24,6 +24,7 @@
>
> #include <linux/module.h>
>
> +#include <linux/atomic.h>
> #include <linux/kernel.h>
> #include <linux/init.h>
> #include <linux/slab.h>
> @@ -65,6 +66,7 @@ struct bcm203x_data {
> unsigned long state;
>
> struct work_struct work;
> + atomic_t shutdown;
>
> struct urb *urb;
> unsigned char *buffer;
> @@ -97,6 +99,7 @@ static void bcm203x_complete(struct urb *urb)
>
> data->state = BCM203X_SELECT_MEMORY;
>
> + /* use workqueue to have a small delay */
> schedule_work(&data->work);
> break;
>
> @@ -155,6 +158,10 @@ static void bcm203x_work(struct work_struct *work)
> struct bcm203x_data *data =
> container_of(work, struct bcm203x_data, work);
>
> + smp_rmb();
> + if (atomic_read(&data->shutdown))
> + return;
> +
> if (usb_submit_urb(data->urb, GFP_ATOMIC) < 0)
> BT_ERR("Can't submit URB");
> }
> @@ -243,6 +250,7 @@ static int bcm203x_probe(struct usb_interface *intf, const struct usb_device_id
>
> usb_set_intfdata(intf, data);
>
> + /* use workqueue to have a small delay */
> schedule_work(&data->work);
>
> return 0;
> @@ -254,6 +262,10 @@ static void bcm203x_disconnect(struct usb_interface *intf)
>
> BT_DBG("intf %p", intf);
>
> + atomic_inc(&data->shutdown);
> + smp_wmb();
> + cancel_work_sync(&data->work);
> +
can you quickly explain to me why we need the memory barrier here.
Regards
Marcel
next prev parent reply other threads:[~2011-10-26 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 19:13 [PATCH 1/2] Bluetooth: bcm203x: Fix race condition on disconnect David Herrmann
2011-10-25 19:13 ` [PATCH 2/2] Bluetooth: bcm203x: Use GFP_KERNEL in workqueue David Herrmann
2011-10-26 8:54 ` Marcel Holtmann
2011-10-31 19:55 ` Gustavo Padovan
2011-10-26 8:57 ` Marcel Holtmann [this message]
2011-10-26 9:03 ` [PATCH 1/2] Bluetooth: bcm203x: Fix race condition on disconnect David Herrmann
2011-10-26 9:04 ` Marcel Holtmann
2011-10-26 9:13 ` [PATCH v2] " David Herrmann
2011-10-26 9:16 ` Marcel Holtmann
2011-10-31 19:54 ` Gustavo Padovan
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=1319619427.15441.254.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=dh.herrmann@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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).