All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Herrmann <dh.herrmann@gmail.com>
To: Karl Relton <karllinuxtest.relton@ntlworld.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Resend [PATCH] hidp: Make hidp_get_raw_report abort if the session is terminating
Date: Wed, 20 Feb 2013 16:29:07 +0100	[thread overview]
Message-ID: <CANq1E4QD1O64iZuN3pToOddQMp8kF57BGUcD5hDPmm7MYPwJ7w@mail.gmail.com> (raw)
In-Reply-To: <1361197622.4983.2.camel@dellpc>

Hi Karl

One minor nitpick below:

On Mon, Feb 18, 2013 at 3:27 PM, Karl Relton
<karllinuxtest.relton@ntlworld.com> wrote:
> From: Karl Relton <karllinuxtest.relton@ntlworld.com>
>
> After linux 3.2 the hid_destroy_device call in hidp_session cleaning up
> invokes a hook to the power_supply code which in turn tries to read the
> battery capacity. This read will trigger a call to hidp_get_raw_report
> which is bound to fail because the device is being taken away - so rather
> than wait for the 5 second timeout failure this change enables it to fail
> straight away.
>
> Signed-off-by: Karl Relton <karllinuxtest.relton@ntlworld.com>
> ---
>  net/bluetooth/hidp/core.c |    7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/hidp/core.c b/net/bluetooth/hidp/core.c
> index b2bcbe2..a4c1bb0 100644
> --- a/net/bluetooth/hidp/core.c
> +++ b/net/bluetooth/hidp/core.c
> @@ -311,6 +311,9 @@ static int hidp_get_raw_report(struct hid_device *hid,
>         int numbered_reports = hid->report_enum[report_type].numbered;
>         int ret;
>
> +       if (atomic_read(&session->terminate))
> +               return -EIO;
> +
>         switch (report_type) {
>         case HID_FEATURE_REPORT:
>                 report_type = HIDP_TRANS_GET_REPORT | HIDP_DATA_RTYPE_FEATURE;
> @@ -695,8 +698,10 @@ static int hidp_session(void *arg)
>         set_current_state(TASK_INTERRUPTIBLE);
>         while (!atomic_read(&session->terminate)) {
>                 if (ctrl_sk->sk_state != BT_CONNECTED ||
> -                               intr_sk->sk_state != BT_CONNECTED)
> +                               intr_sk->sk_state != BT_CONNECTED) {
> +                       atomic_inc(&session->terminate);

Lets move this atomic_inc() directly below the while() loop. This
guarantees that we won't trap into this again if we add other "break;"
conditions.

Other than that the patch looks fine. Feel free to add a:
  Reviewed-by: David Herrmann <dh.herrmann@gmail.com>

Thanks
David

>                         break;
> +               }
>
>                 while ((skb = skb_dequeue(&intr_sk->sk_receive_queue))) {
>                         skb_orphan(skb);
> --
> 1.7.9.5
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-02-20 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 14:27 Resend [PATCH] hidp: Make hidp_get_raw_report abort if the session is terminating Karl Relton
2013-02-20 15:29 ` David Herrmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-18 14:25 Karl and Karen Relton

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=CANq1E4QD1O64iZuN3pToOddQMp8kF57BGUcD5hDPmm7MYPwJ7w@mail.gmail.com \
    --to=dh.herrmann@gmail.com \
    --cc=karllinuxtest.relton@ntlworld.com \
    --cc=linux-bluetooth@vger.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 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.