netdev - Re: [PATCH net] net: qmi_wwan: fix Gobi device probing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 22 Jun 2012 17:17:35 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	bjorn@...k.no
Cc:	netdev@...r.kernel.org, linux-usb@...r.kernel.org,
	H.Siebmanns@...nline.de
Subject: Re: [PATCH net] net: qmi_wwan: fix Gobi device probing

From: Bjørn Mork <bjorn@...k.no>
Date: Thu, 21 Jun 2012 14:45:58 +0200

> Ignoring interfaces with additional descriptors is not a reliable
> method for locating the correct interface on Gobi devices.  There
> is at least one device where this method fails:
> https://bbs.archlinux.org/viewtopic.php?id=143506
> 
> The result is that the AT command port (interface #2) is hidden
> from qcserial, preventing traditional serial modem usage:
 ...
> Use static interface numbers taken from the interface map in
> qcserial for all Gobi devices instead:
 ...
> This should be more reliable over all, and will also prevent the
> noisy "probe failed" messages.  The whitelisting logic is expected
> to be replaced by direct interface number matching in 3.6.
> 
> Reported-by: Heinrich Siebmanns (Harvey) <H.Siebmanns@...nline.de>
> Cc: <stable@...r.kernel.org> # v3.4: 0000188 USB: qmi_wwan: Make forced int 4 whitelist generic
> Cc: <stable@...r.kernel.org> # v3.4: f7142e6 USB: qmi_wwan: Add ZTE (Vodafone) K3520-Z
> Cc: <stable@...r.kernel.org> # v3.4
> Signed-off-by: Bjørn Mork <bjorn@...k.no>

Applied.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html