From: Johan Hovold <johan@kernel.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Johan Hovold <johan@kernel.org>,
syzbot <syzbot+53f029db71c19a47325a@syzkaller.appspotmail.com>,
andreyknvl@google.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
mchehab@kernel.org, syzkaller-bugs@googlegroups.com,
wen.yang99@zte.com.cn
Subject: Re: general protection fault in smsusb_init_device
Date: Tue, 7 May 2019 17:07:25 +0200 [thread overview]
Message-ID: <20190507150725.GB29016@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1905071035450.1632-100000@iolanthe.rowland.org>
On Tue, May 07, 2019 at 10:42:58AM -0400, Alan Stern wrote:
> On Tue, 7 May 2019, Johan Hovold wrote:
> > > @@ -411,6 +412,23 @@ static int smsusb_init_device(struct usb
> > > dev->udev = interface_to_usbdev(intf);
> > > dev->state = SMSUSB_DISCONNECTED;
> > >
> > > + for (i = 0; i < intf->cur_altsetting->desc.bNumEndpoints; i++) {
> > > + struct usb_endpoint_descriptor *desc =
> > > + &intf->cur_altsetting->endpoint[i].desc;
> > > +
> > > + if (desc->bEndpointAddress & USB_DIR_IN) {
> > > + dev->in_ep = desc->bEndpointAddress;
> > > + in_maxp = usb_endpoint_maxp(desc);
> > > + } else {
> > > + dev->out_ep = desc->bEndpointAddress;
> > > + }
> > > + }
> > > +
> > > + pr_debug("in_ep = %02x, out_ep = %02x\n",
> > > + dev->in_ep, dev->out_ep);
> > > + if (!dev->in_ep || !dev->out_ep) /* Missing endpoints? */
> > > + return -EINVAL;
> >
> > Looks like you're now leaking dev here, and so is the current code in
> > the later error paths.
> >
> > Since this return value will be returned from probe, you may want to use
> > -ENXIO or -ENODEV instead of -EINVAL.
> >
> > Looks good otherwise.
>
> Thanks for the review. You're right about the memory leak (although
> you're wrong about the later error paths: smsusb_term_device()
> deallocates dev).
Indeed, I missed the free in smsusb_term_device(). Sorry about that.
Johan
prev parent reply other threads:[~2019-05-07 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 12:06 general protection fault in smsusb_init_device syzbot
2019-04-19 20:29 ` Alan Stern
2019-05-06 20:41 ` Alan Stern
2019-05-06 21:21 ` syzbot
2019-05-07 16:39 ` [PATCH] media: usb: siano: Fix general protection fault in smsusb Alan Stern
2019-05-08 6:01 ` Johan Hovold
2019-05-24 13:35 ` Mauro Carvalho Chehab
2019-05-24 13:54 ` Alan Stern
2019-05-07 8:34 ` general protection fault in smsusb_init_device Johan Hovold
2019-05-07 14:42 ` Alan Stern
2019-05-07 15:07 ` Johan Hovold [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=20190507150725.GB29016@localhost \
--to=johan@kernel.org \
--cc=andreyknvl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+53f029db71c19a47325a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wen.yang99@zte.com.cn \
/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).