From: Oliver Neukum <oneukum@suse.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] cdc-wdm: fix "out-of-sync" due to missing notifications
Date: Sun, 10 Jul 2016 14:47:59 +0200 [thread overview]
Message-ID: <1468154879.751.5.camel@suse.com> (raw)
In-Reply-To: <87wpku3box.fsf@miraculix.mork.no>
On Sat, 2016-07-09 at 20:31 +0200, Bjørn Mork wrote:
> [removed the stable CC since this discussion isn't relevant to stable
> anymore]
>
> Oliver Neukum <oneukum@suse.com> writes:
[..]
> How about splitting the behaviour locally in cdc-wdm, keeping the
> current behaviour for CDC WDM devices and changing to "drain on open"
> for the netdev drivers? Something like this plus the necessary logic
> dealing with the "drain_on_open" ("next_desc" is a label in wdm_probe):
Even better solution.
[..]
> Yes. We could alternatively filter the EPIPE from read(), since it
> isn't supposed to happen anyway. But it's not going to look less ugly :(
I'd rather not. Dropping errors really is evil.
> Execpt for the extreme ugliness, I don't think it will hurt to apply
> this unconditionally for all the network drivers using cdc-wdm, as long
> as it is limited to open only.
It is very hard to see how would can avoid it in the long run in resume.
> I certainly want to avoid any blacklist. Device IDs are cheap in this
> market. The MBIM modems typically run Android and the device ID is
> configured in NVRAM for whatever OEM laptop vendor it is sold to.
> Having a catch-all class driver for MBIM is an absolute requirement.
> Making it depend on lists of devices is not an option, IMHO.
Obviously. I am just not optimistic that we can do without specific
exceptions in the long run.
Regards
Oliver
prev parent reply other threads:[~2016-07-10 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 19:59 [PATCH v2] cdc-wdm: fix "out-of-sync" due to missing notifications Bjørn Mork
2016-07-04 8:04 ` Oliver Neukum
2016-07-04 11:54 ` Bjørn Mork
2016-07-04 12:48 ` Oliver Neukum
2016-07-04 13:09 ` Bjørn Mork
2016-07-04 17:01 ` Bjørn Mork
2016-07-05 12:52 ` Oliver Neukum
2016-07-09 18:31 ` Bjørn Mork
2016-07-10 12:47 ` Oliver Neukum [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=1468154879.751.5.camel@suse.com \
--to=oneukum@suse.com \
--cc=bjorn@mork.no \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.