From: Vladis Dronov <vdronov@redhat.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: aiptek: fix crash on detecting device without endpoints
Date: Fri, 27 Nov 2015 05:50:10 -0500 (EST) [thread overview]
Message-ID: <1953763158.25062502.1448621410440.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1511261233120.14257-100000@netrider.rowland.org>
Hello,
> > Hmm, I see quite a few drivers assuming that endpoint 0 will be present.
> > I wonder if that should not be solved at USB level.
>
> Every USB device always has endpoint 0. If one didn't, the kernel
> wouldn't be able to initialize and enumerate it.
Yes for the normal USB device. This case is a weird USB device (with no
endpoints) specially designed to be weird. My point here is that even a
weird device probing should not crash a kernel by a NULL-deref.
> > Alan, does it make sense to have drivers probe interface if it does not
> > have any endpoints?
>
> Yes; in theory an interface can do everything it needs using only
> endpoint 0. Driver shouldn't assume anything about the endpoints in
> the interfaces they problem.
The current kernel code in drivers/usb/core/config.c accepts an interface
with no endpoints in one of its configurations, and I could not find a
direct ban for that in USB standard. So, I currently believe, it is a driver
job to check if the endpoint 0 exist, otherwise we must change the kernel
USB detection code.
btw, indeed, this is not the only driver with this problem, I've met 2 more.
Best regards,
Vladis Dronov | Red Hat, Inc. | Product Security Engineer
next prev parent reply other threads:[~2015-11-27 10:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 15:58 [PATCH] Input: aiptek: fix crash on detecting device without endpoints Vladis Dronov
2015-11-26 16:36 ` Dmitry Torokhov
2015-11-26 17:35 ` Alan Stern
2015-11-27 10:50 ` Vladis Dronov [this message]
2015-11-27 21:54 ` Alan Stern
2015-11-30 12:36 ` Vladis Dronov
2015-11-30 16:06 ` Alan Stern
2015-11-30 19:40 ` Dmitry Torokhov
2015-11-30 20:38 ` Alan Stern
2015-11-30 21:11 ` Dmitry Torokhov
2015-12-01 8:09 ` Vladis Dronov
2015-12-01 15:07 ` Alan Stern
2015-12-01 21:16 ` Dmitry Torokhov
2015-12-02 11:03 ` Vladis Dronov
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=1953763158.25062502.1448621410440.JavaMail.zimbra@redhat.com \
--to=vdronov@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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).