Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1610427
| From | Oliver Neukum <oneukum@suse.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 1/4] cdc-acm: reassemble fragmented notifications |
| Date | 2017-03-28 11:00 +0200 |
| Message-ID | <tpV8T-535-25@gated-at.bofh.it> (permalink) |
| References | <tl15f-5mY-9@gated-at.bofh.it> <tmrK1-27E-3@gated-at.bofh.it> <tmrTI-2ru-13@gated-at.bofh.it> <tn76x-6tc-1@gated-at.bofh.it> <toFpw-7JB-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Am Freitag, den 24.03.2017, 22:50 +0100 schrieb Tobias Herzog:
> Hi Oliver,
>
> thank you for your patience... :) I have a question to one of your
> comments (see below).
>
> Best regards,
> Tobias
>
> >
> > Am Samstag, den 18.03.2017, 19:52 +0100 schrieb Tobias Herzog:
> > >
> > >
> > > USB devices may have very limitited endpoint packet sizes, so that
> > > notifications can not be transferred within one single usb packet.
> > > Reassembling of multiple packages may be necessary.
> > Hi,
> >
> > almost perfect.
> > A few new issue. Comments inline.
> >
> > >
> > >
> > >
> > > + struct usb_cdc_notification *dr = (struct
> > > usb_cdc_notification *)buf;
> > > + unsigned char *data = (unsigned char *)(dr + 1);
> > This is border line incorrect. It depends on the compiler not
> > adding padding. Please make it
> >
> > buf + sizeof(struct usb_cdc_notification)
> >
> > >
> > >
> > > - usb_mark_last_busy(acm->dev);
> > > -
> > > - data = (unsigned char *)(dr + 1);
> > > switch (dr->bNotificationType) {
> > > case USB_CDC_NOTIFY_NETWORK_CONNECTION:
> > > dev_dbg(&acm->control->dev,
> > > @@ -363,8 +337,77 @@ static void acm_ctrl_irq(struct urb *urb)
> > > __func__,
> > > dr->bNotificationType, dr->wIndex,
> > > dr->wLength, data[0], data[1]);
> > > + }
> > > +}
> > > +
> > > +/* control interface reports status changes with "interrupt"
> > > transfers */
> > > +static void acm_ctrl_irq(struct urb *urb)
> > > +{
> > > + struct acm *acm = urb->context;
> > > + struct usb_cdc_notification *dr = urb->transfer_buffer;
> > > + unsigned int current_size = urb->actual_length;
> > > + unsigned int expected_size, copy_size;
> > > + int retval;
> > > + int status = urb->status;
> > > +
> > > + switch (status) {
> > > + case 0:
> > > + /* success */
> > > break;
> > > + case -ECONNRESET:
> > > + case -ENOENT:
> > > + case -ESHUTDOWN:
> > > + /* this urb is terminated, clean up */
> > > + acm->nb_index = 0;
> > > + dev_dbg(&acm->control->dev,
> > > + "%s - urb shutting down with status:
> > > %d\n",
> > > + __func__, status);
> > > + return;
> > > + default:
> > > + dev_dbg(&acm->control->dev,
> > > + "%s - nonzero urb status received: %d\n",
> > > + __func__, status);
> > > + goto exit;
> > > }
> > > +
> > > + usb_mark_last_busy(acm->dev);
> > > +
> > > + if (acm->nb_index)
> > > + dr = (struct usb_cdc_notification *)acm-
> > > >
> > > > notification_buffer;
> > > +
> > > + /* size = notification-header + (optional) data */
> > > + expected_size = sizeof(struct usb_cdc_notification) +
> > > + le16_to_cpu(dr->wLength);
> > > +
> > > + if (current_size < expected_size) {
> > > + /* notification is transmitted fragmented,
> > > reassemble */
> > > + if (acm->nb_size < expected_size) {
> > > + if (acm->nb_size) {
> > > + kfree(acm->notification_buffer);
> > > + acm->nb_size = 0;
> > > + }
> > > + acm->notification_buffer =
> > > + kmalloc(expected_size,
> > > GFP_ATOMIC);
> > Given how kmalloc works you'd better round this up to a power of two.
> >
> > >
> > >
> > > + if (!acm->notification_buffer)
> > > + goto exit;
> > This is most subtle. Please add a comment that this prevents a double
> > free if we get a disconnect()
> I'm unsure if I got this right: Are you talking about the fact, that
> the use of 'kmalloc' will make 'acm->notification_buffer' valid again
> (i.e. NULL or pointing to a correctly allocated block), after it was
yes
> "invalidated" by 'kfree' (in case the previously allocated buffer was
> too small)?
> The 'goto exit'-thing for me is just not to use the buffer if
> allocation fails. Or am I missing anything here?
You need to consider the hot unplug case.
Regards
Oliver
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH v2 0/4] cdc-acm: reassemble fragmented notifications Tobias Herzog <t-herzog@gmx.de> - 2017-03-18 20:00 +0100
[PATCH v2 4/4] cdc-acm: remove unused element of struct acm Tobias Herzog <t-herzog@gmx.de> - 2017-03-18 20:00 +0100
[PATCH v2 2/4] cdc-acm: fix possible invalid access when processing notification Tobias Herzog <t-herzog@gmx.de> - 2017-03-18 20:00 +0100
Re: [PATCH v2 2/4] cdc-acm: fix possible invalid access when processing notification Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> - 2017-03-19 11:00 +0100
Re: [PATCH v2 2/4] cdc-acm: fix possible invalid access when processing notification Oliver Neukum <oneukum@suse.com> - 2017-03-20 16:10 +0100
[PATCH v2 1/4] cdc-acm: reassemble fragmented notifications Tobias Herzog <t-herzog@gmx.de> - 2017-03-18 20:10 +0100
Re: [PATCH v2 1/4] cdc-acm: reassemble fragmented notifications Oliver Neukum <oneukum@suse.com> - 2017-03-20 16:10 +0100
Re: [PATCH v2 1/4] cdc-acm: reassemble fragmented notifications Tobias Herzog <t-herzog@gmx.de> - 2017-03-24 23:00 +0100
Re: [PATCH v2 1/4] cdc-acm: reassemble fragmented notifications Oliver Neukum <oneukum@suse.com> - 2017-03-28 11:00 +0200
csiph-web