From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
syzbot <syzbot+85e3ddbf0ddbfbc85f1e@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] media/usb/siano: Fix endpoint type checking in smsusb
Date: Tue, 20 Aug 2024 01:10:33 +0200 [thread overview]
Message-ID: <20240820011033.79312cb5@foz.lan> (raw)
In-Reply-To: <044260d2-4aa3-4937-9f5b-91e039a1df41@rowland.harvard.edu>
Em Mon, 19 Aug 2024 13:14:19 -0400
Alan Stern <stern@rowland.harvard.edu> escreveu:
> On Mon, Aug 19, 2024 at 06:24:56PM +0200, Mauro Carvalho Chehab wrote:
> > Basically, the actual SMS device type is given by this enum:
> >
> > enum sms_device_type_st {
> > SMS_UNKNOWN_TYPE = -1,
> >
> > SMS_STELLAR = 0,
> > SMS_NOVA_A0,
> > SMS_NOVA_B0,
> > SMS_VEGA,
> > SMS_VENICE,
> > SMS_MING,
> > SMS_PELE,
> > SMS_RIO,
> > SMS_DENVER_1530,
> > SMS_DENVER_2160,
> >
> > SMS_NUM_OF_DEVICE_TYPES /* This is just a count */
> > };
> >
> > But I dunno if there are a 1:1 mapping between type and chipset
> > number. The above type names probably match some vendor internal
> > names, but we never had any tables associating them to a device number,
> > as the vendor never provided us such information.
> >
> > Btw I vaguely remember I heard about a newer Siano chipsets (sm3xxx),
> > but never saw such devices.
> >
> > -
> >
> > Now, I'm not sure about what endpoints this specific driver exports, as
> > I'm lacking vendor's documentation. What I said is that almost all DVB
> > devices have isoc endpoints, but I dunno if this is the case of Siano.
>
> Currently the driver exports only bulk endpoints, even though it doesn't
> check the endpoint type. You can tell because the only routine in it
> that calls usb_submit_urb() is smsusb_submit_urb(), and that routine
> calls usb_fill_bulk_urb() before doing the submission.
>
> Given this, I suggest merging the earlier patch submission from Nikita
> Zhandarovich as-is. If the driver ever evolves to include support for
> isochronous endpoints, the probe function can be modified then.
I'll see if I can try his patch and see if device keeps working. The
logic indeed use endpoints in bulk mode, but I'm not sure if, for all the
BIOS files at drivers/media/common/siano/smscoreapi.[ch], the endpoints
are properly reported as bulk.
What happens if an endpoint is reported as ISOC, but the URB submit
is called without URB_ISO_ASAP? On a quick check, the code at usb_submit_urb()
seems to not complain about that.
I would be a lot more comfortable if the patch were using just
if (usb_endpoint_dir_in(desc))
...
if (usb_endpoint_dir_out(desc))
...
or something like this (to accept both isoc and bulk):
if (!usb_endpoint_xfer_int(epd)) {
if (usb_endpoint_dir_in(desc))
...
if (usb_endpoint_dir_out(desc))
...
}
instead of calling usb_endpoint_xfer_bulk(desc) to check if type
is bulk.
I'll try to do some tests, but not sure when, as I'm traveling abroad
this week.
Thanks,
Mauro
next prev parent reply other threads:[~2024-08-19 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 21:37 [syzbot] [media?] [usb?] WARNING in smsusb_init_device/usb_submit_urb syzbot
2024-07-29 19:31 ` Alan Stern
2024-07-29 20:00 ` syzbot
2024-07-31 17:29 ` [PATCH] media/usb/siano: Fix endpoint type checking in smsusb Alan Stern
2024-08-18 18:20 ` Alan Stern
2024-08-19 3:11 ` Greg KH
2024-08-19 8:15 ` Mauro Carvalho Chehab
2024-08-19 14:32 ` Alan Stern
2024-08-19 16:24 ` Mauro Carvalho Chehab
2024-08-19 17:14 ` Alan Stern
2024-08-19 23:10 ` Mauro Carvalho Chehab [this message]
2024-08-20 2:31 ` Alan Stern
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=20240820011033.79312cb5@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=gregkh@linuxfoundation.org \
--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+85e3ddbf0ddbfbc85f1e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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).