From: Johan Hovold <jhovold@gmail.com>
To: Mike Remski <mremski@mutualink.net>
Cc: Johan Hovold <jhovold@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: ftdi_sio BUG: NULL pointer dereference
Date: Wed, 4 Jun 2014 17:09:38 +0200 [thread overview]
Message-ID: <20140604150938.GD11160@localhost> (raw)
In-Reply-To: <538F3360.40407@mutualink.net>
On Wed, Jun 04, 2014 at 10:55:28AM -0400, Mike Remski wrote:
> On 06/04/2014 10:52 AM, Johan Hovold wrote:
> > On Wed, Jun 04, 2014 at 10:29:37AM -0400, Mike Remski wrote:
> >> On 06/04/2014 10:19 AM, Johan Hovold wrote:
> >>> >From 4ddea3a573b8c15beefb67bc35c440850063d79d Mon Sep 17 00:00:00 2001
> >>> From: Johan Hovold <johan@kernel.org>
> >>> Date: Wed, 4 Jun 2014 14:09:43 +0200
> >>> Subject: [PATCH 1/5] USB: ftdi_sio: fix null deref at port probe
> >>>
> >>> Fix NULL-pointer dereference when probing an interface with no
> >>> endpoints.
> >>>
> >>> These devices have two bulk endpoints per interface, but this avoids
> >>> crashing the kernel if a user forces a non-FTDI device to be probed.
> >>>
> >>> Note that the iterator variable was made unsigned in order to avoid
> >>> a maybe-uninitialized compiler warning for ep_desc after the loop.
> >>>
> >>> Fixes: 895f28badce9 ("USB: ftdi_sio: fix hi-speed device packet size
> >>> calculation")
> >>>
> >>> Reported-by: Mike Remski <mremski@mutualink.net>
> >>> Cc: <stable@vger.kernel.org> # 2.3.61
> >>> Signed-off-by: Johan Hovold <johan@kernel.org>
> >>> ---
> >>> drivers/usb/serial/ftdi_sio.c | 7 +++++--
> >>> 1 file changed, 5 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
> >>> index 7c6e1dedeb06..3019141397eb 100644
> >>> --- a/drivers/usb/serial/ftdi_sio.c
> >>> +++ b/drivers/usb/serial/ftdi_sio.c
> >>> @@ -1564,14 +1564,17 @@ static void ftdi_set_max_packet_size(struct usb_serial_port *port)
> >>> struct usb_device *udev = serial->dev;
> >>>
> >>> struct usb_interface *interface = serial->interface;
> >>> - struct usb_endpoint_descriptor *ep_desc = &interface->cur_altsetting->endpoint[1].desc;
> >>> + struct usb_endpoint_descriptor *ep_desc;
> >>>
> >>> unsigned num_endpoints;
> >>> - int i;
> >>> + unsigned i;
> >>>
> >>> num_endpoints = interface->cur_altsetting->desc.bNumEndpoints;
> >>> dev_info(&udev->dev, "Number of endpoints %d\n", num_endpoints);
> >>>
> >>> + if (!num_endpoints)
> >>> + return;
> >>> +
> >>> /* NOTE: some customers have programmed FT232R/FT245R devices
> >>> * with an endpoint size of 0 - not good. In this case, we
> >>> * want to override the endpoint descriptor setting and use a
> >> Thanks Johan. I tried to get the cdc_acm working; did not have much
> >> luck/time (typical overcommit on workload) I will retry with the commit
> >> mentioned.
> >> I will try the patch today and get back to you. Nice on the ep_desc:
> >> looking at the code priv->max_packet_size is attached to the port, your
> >> change would use the last thing off of cur_altsetting->endpoint[], but
> >> I'm wondering if we should actually be setting priv->max_packet_size to
> >> whatever the max is of all endpoint[].desc->wMaxPacketSize?
> >>
> >> Thoughts?
> > This is the exact same behaviour as the old code (minus the NULL-deref).
> >
> > These device have two bulk endpoints per interface and they are supposed
> > to be using the same max packet size (64 or 512 depending on device and
> > host).
> >
> > This value is also used during depacketisation of incoming data (and
> > packetisation of outgoing data for legacy devices). I'm pretty convinced
> > you're using the wrong driver, something which would lead to corruption
> > of incoming data when the (non-existing) status bytes are stripped from
> > the stream.
> >
> > You really should try cdc-acm.
> >
> > Johan
> Sorry, forgot to add:
> Tested patch and it works as desired.
Thanks, I'll add a Tested-by tag then.
Johan
next prev parent reply other threads:[~2014-06-04 15:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 14:25 ftdi_sio BUG: NULL pointer dereference Mike Remski
2014-06-02 14:33 ` Johan Hovold
2014-06-02 15:16 ` Mike Remski
2014-06-02 15:40 ` Johan Hovold
2014-06-02 16:02 ` Mike Remski
2014-06-02 16:20 ` Johan Hovold
2014-06-02 16:24 ` Mike Remski
2014-06-02 16:49 ` Johan Hovold
2014-06-02 17:11 ` Mike Remski
2014-06-02 17:46 ` Johan Hovold
2014-06-02 17:50 ` Mike Remski
2014-06-03 10:17 ` Mike Remski
2014-06-04 14:19 ` Johan Hovold
2014-06-04 14:29 ` Mike Remski
2014-06-04 14:52 ` Johan Hovold
2014-06-04 14:54 ` Mike Remski
2014-06-04 14:55 ` Mike Remski
2014-06-04 15:09 ` Johan Hovold [this message]
2014-06-04 15:12 ` Mike Remski
2014-06-04 15:41 ` Mike Remski
2014-06-04 16:00 ` Johan Hovold
2014-06-04 16:13 ` Mike Remski
2014-06-04 17:05 ` Mike Remski
2014-06-05 7:10 ` Johan Hovold
2014-06-02 16:09 ` Mike Remski
2014-06-02 16:23 ` Greg KH
2014-06-02 16:26 ` Mike Remski
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=20140604150938.GD11160@localhost \
--to=jhovold@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mremski@mutualink.net \
/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