All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Nazarewicz <mina86@mina86.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] usb: gadget: f_midi: unlock on error
Date: Mon, 04 Apr 2016 19:25:24 +0000	[thread overview]
Message-ID: <xa1toa9pi3bv.fsf@mina86.com> (raw)
In-Reply-To: <20160402045108.GD11775@mwanda>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 2469 bytes --]

> On 04/04/16 13:11, Michal Nazarewicz wrote:
>> Or maybe even this which gets away with gotos all together:
>> 
>> diff --git a/drivers/usb/gadget/function/f_midi.c b/drivers/usb/gadget/function/f_midi.c
>> index 56e2dde..91cae60 100644
>> --- a/drivers/usb/gadget/function/f_midi.c
>> +++ b/drivers/usb/gadget/function/f_midi.c
>> @@ -598,27 +598,20 @@ done:
>>  static void f_midi_transmit(struct f_midi *midi)
>>  {
>>         struct usb_ep *ep = midi->in_ep;
>> -       int ret;
>>         unsigned long flags;
>> +       int ret = -1;
>>  
>>         /* We only care about USB requests if IN endpoint is enabled */
>> -       if (!ep || !ep->enabled)
>> -               goto drop_out;
>> -
>> -       spin_lock_irqsave(&midi->transmit_lock, flags);
>> -
>> -       do {
>> -               ret = f_midi_do_transmit(midi, ep);
>> -               if (ret < 0)
>> -                       goto drop_out;
>> -       } while (ret);
>> -
>> -       spin_unlock_irqrestore(&midi->transmit_lock, flags);
>> -
>> -       return;
>> +       if (ep && ep->enabled) {
>> +               spin_lock_irqsave(&midi->transmit_lock, flags);
>> +               while ((ret = f_midi_do_transmit(midi, ep)) > 0) {
>> +                       /* nop */
>> +               }
>> +               spin_unlock_irqrestore(&midi->transmit_lock, flags);
>> +       }
>>  
>> -drop_out:
>> -       f_midi_drop_out_substreams(midi);
>> +       if (ret < 0)
>> +               f_midi_drop_out_substreams(midi);
>>  }
>>  
>>  static void f_midi_in_tasklet(unsigned long data)

On Mon, Apr 04 2016, Felipe Ferreri Tonello wrote:
> I am fine with these options, probably the second, but I don't think
> they are any clearer than before, so I don't see any real benefits with
> the changes.

The spin_lock_irqsave is paired with exactly one spin_unlock_irqrestore
which is cleaner in my book.  I don’t have strong feelings about this
though.

> In fact, I think f_midi_do_transmit should be documented, since there
> are 3 possible return condition:
> <0 breaks the loop and drop out substreams
> 0 breaks the loop
> >0 continues the loop

That’s of course separate issue.

-- 
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2016-04-04 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-02  4:51 [patch] usb: gadget: f_midi: unlock on error Dan Carpenter
2016-04-04  9:43 ` Felipe Ferreri Tonello
2016-04-04 12:11 ` Michal Nazarewicz
2016-04-04 12:18 ` Felipe Balbi
2016-04-04 13:22 ` Felipe Ferreri Tonello
2016-04-04 19:25 ` Michal Nazarewicz [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=xa1toa9pi3bv.fsf@mina86.com \
    --to=mina86@mina86.com \
    --cc=kernel-janitors@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.