<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/net/can/usb, branch linux-4.1.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.1.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.1.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2018-03-01T03:09:39Z</updated>
<entry>
<title>can: peak: fix potential bug in packet fragmentation</title>
<updated>2018-03-01T03:09:39Z</updated>
<author>
<name>Stephane Grosjean</name>
<email>s.grosjean@peak-system.com</email>
</author>
<published>2018-01-15T15:31:19Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=166df6fcf6d2f7ab2d6a508b87593e10136f4378'/>
<id>urn:sha1:166df6fcf6d2f7ab2d6a508b87593e10136f4378</id>
<content type='text'>
[ Upstream commit d8a243af1a68395e07ac85384a2740d4134c67f4 ]

In some rare conditions when running one PEAK USB-FD interface over
a non high-speed USB controller, one useless USB fragment might be sent.
This patch fixes the way a USB command is fragmented when its length is
greater than 64 bytes and when the underlying USB controller is not a
high-speed one.

Signed-off-by: Stephane Grosjean &lt;s.grosjean@peak-system.com&gt;
Cc: linux-stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
</content>
</entry>
<entry>
<title>can: gs_usb: fix return value of the "set_bittiming" callback</title>
<updated>2018-03-01T00:32:21Z</updated>
<author>
<name>Wolfgang Grandegger</name>
<email>wg@grandegger.com</email>
</author>
<published>2017-12-13T18:52:23Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=6aa975f1b5a15881670160d96d65537a20b012f4'/>
<id>urn:sha1:6aa975f1b5a15881670160d96d65537a20b012f4</id>
<content type='text'>
[ Upstream commit d5b42e6607661b198d8b26a0c30969605b1bf5c7 ]

The "set_bittiming" callback treats a positive return value as error!
For that reason "can_changelink()" will quit silently after setting
the bittiming values without processing ctrlmode, restart-ms, etc.

Signed-off-by: Wolfgang Grandegger &lt;wg@grandegger.com&gt;
Cc: linux-stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
</content>
</entry>
<entry>
<title>can: usb_8dev: cancel urb on -EPIPE and -EPROTO</title>
<updated>2018-01-17T17:55:21Z</updated>
<author>
<name>Martin Kelly</name>
<email>mkelly@xevo.com</email>
</author>
<published>2017-12-05T19:15:50Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=8a7022f7625040e4295d89f72200cabd8195bdaf'/>
<id>urn:sha1:8a7022f7625040e4295d89f72200cabd8195bdaf</id>
<content type='text'>
[ Upstream commit 12147edc434c9e4c7c2f5fee2e5519b2e5ac34ce ]

In mcba_usb, we have observed that when you unplug the device, the driver will
endlessly resubmit failing URBs, which can cause CPU stalls. This issue
is fixed in mcba_usb by catching the codes seen on device disconnect
(-EPIPE and -EPROTO).

This driver also resubmits in the case of -EPIPE and -EPROTO, so fix it
in the same way.

Signed-off-by: Martin Kelly &lt;mkelly@xevo.com&gt;
Cc: linux-stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
</content>
</entry>
<entry>
<title>can: esd_usb2: cancel urb on -EPIPE and -EPROTO</title>
<updated>2018-01-17T17:55:21Z</updated>
<author>
<name>Martin Kelly</name>
<email>mkelly@xevo.com</email>
</author>
<published>2017-12-05T19:15:48Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=8b65515d121586ebbfb1440768e35b207dde98b2'/>
<id>urn:sha1:8b65515d121586ebbfb1440768e35b207dde98b2</id>
<content type='text'>
[ Upstream commit 7a31ced3de06e9878e4f9c3abe8f87d9344d8144 ]

In mcba_usb, we have observed that when you unplug the device, the driver will
endlessly resubmit failing URBs, which can cause CPU stalls. This issue
is fixed in mcba_usb by catching the codes seen on device disconnect
(-EPIPE and -EPROTO).

This driver also resubmits in the case of -EPIPE and -EPROTO, so fix it
in the same way.

Signed-off-by: Martin Kelly &lt;mkelly@xevo.com&gt;
Cc: linux-stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
</content>
</entry>
<entry>
<title>can: ems_usb: cancel urb on -EPIPE and -EPROTO</title>
<updated>2018-01-17T17:55:21Z</updated>
<author>
<name>Martin Kelly</name>
<email>mkelly@xevo.com</email>
</author>
<published>2017-12-05T19:15:47Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=1faeca460ed7144544652dac82412e01a5ca9f29'/>
<id>urn:sha1:1faeca460ed7144544652dac82412e01a5ca9f29</id>
<content type='text'>
[ Upstream commit bd352e1adfe0d02d3ea7c8e3fb19183dc317e679 ]

In mcba_usb, we have observed that when you unplug the device, the driver will
endlessly resubmit failing URBs, which can cause CPU stalls. This issue
is fixed in mcba_usb by catching the codes seen on device disconnect
(-EPIPE and -EPROTO).

This driver also resubmits in the case of -EPIPE and -EPROTO, so fix it
in the same way.

Signed-off-by: Martin Kelly &lt;mkelly@xevo.com&gt;
Cc: linux-stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
</content>
</entry>
<entry>
<title>can: kvaser_usb: cancel urb on -EPIPE and -EPROTO</title>
<updated>2018-01-17T17:55:21Z</updated>
<author>
<name>Martin Kelly</name>
<email>mkelly@xevo.com</email>
</author>
<published>2017-12-05T19:15:49Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=bf4857475f657204552d790fd979577076d6e4ce'/>
<id>urn:sha1:bf4857475f657204552d790fd979577076d6e4ce</id>
<content type='text'>
[ Upstream commit 6aa8d5945502baf4687d80de59b7ac865e9e666b ]

In mcba_usb, we have observed that when you unplug the device, the driver will
endlessly resubmit failing URBs, which can cause CPU stalls. This issue
is fixed in mcba_usb by catching the codes seen on device disconnect
(-EPIPE and -EPROTO).

This driver also resubmits in the case of -EPIPE and -EPROTO, so fix it
in the same way.

Signed-off-by: Martin Kelly &lt;mkelly@xevo.com&gt;
Cc: linux-stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
</content>
</entry>
<entry>
<title>can: kvaser_usb: ratelimit errors if incomplete messages are received</title>
<updated>2018-01-17T17:55:21Z</updated>
<author>
<name>Jimmy Assarsson</name>
<email>jimmyassarsson@gmail.com</email>
</author>
<published>2017-11-21T07:22:28Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=16ec63f0f106391c728010e00263f7ee1f0d75c8'/>
<id>urn:sha1:16ec63f0f106391c728010e00263f7ee1f0d75c8</id>
<content type='text'>
[ Upstream commit 8bd13bd522ff7dfa0eb371921aeb417155f7a3be ]

Avoid flooding the kernel log with "Formate error", if incomplete message
are received.

Signed-off-by: Jimmy Assarsson &lt;jimmyassarsson@gmail.com&gt;
Cc: linux-stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
</content>
</entry>
<entry>
<title>can: kvaser_usb: Fix comparison bug in kvaser_usb_read_bulk_callback()</title>
<updated>2018-01-17T17:55:21Z</updated>
<author>
<name>Jimmy Assarsson</name>
<email>jimmyassarsson@gmail.com</email>
</author>
<published>2017-11-21T07:22:27Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=5875c419e115db4f1cdd0fbc7dfac08b88cade9b'/>
<id>urn:sha1:5875c419e115db4f1cdd0fbc7dfac08b88cade9b</id>
<content type='text'>
[ Upstream commit e84f44eb5523401faeb9cc1c97895b68e3cfb78d ]

The conditon in the while-loop becomes true when actual_length is less than
2 (MSG_HEADER_LEN). In best case we end up with a former, already
dispatched msg, that got msg-&gt;len greater than actual_length. This will
result in a "Format error" error printout.

Problem seen when unplugging a Kvaser USB device connected to a vbox guest.

warning: comparison between signed and unsigned integer expressions
[-Wsign-compare]

Signed-off-by: Jimmy Assarsson &lt;jimmyassarsson@gmail.com&gt;
Cc: linux-stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
</content>
</entry>
<entry>
<title>can: kvaser_usb: free buf in error paths</title>
<updated>2018-01-17T17:55:21Z</updated>
<author>
<name>Jimmy Assarsson</name>
<email>jimmyassarsson@gmail.com</email>
</author>
<published>2017-11-21T07:22:26Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=db0081b8eab496df2b7c94ccce32e3ebb8aaefd8'/>
<id>urn:sha1:db0081b8eab496df2b7c94ccce32e3ebb8aaefd8</id>
<content type='text'>
[ Upstream commit 435019b48033138581a6171093b181fc6b4d3d30 ]

The allocated buffer was not freed if usb_submit_urb() failed.

Signed-off-by: Jimmy Assarsson &lt;jimmyassarsson@gmail.com&gt;
Cc: linux-stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
</content>
</entry>
<entry>
<title>can: kvaser_usb: Ignore CMD_FLUSH_QUEUE_REPLY messages</title>
<updated>2017-11-06T04:54:38Z</updated>
<author>
<name>Jimmy Assarsson</name>
<email>jimmyassarsson@gmail.com</email>
</author>
<published>2017-10-24T10:23:29Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=3da77feabb846d4bc357c3a2944aa20f07e0a880'/>
<id>urn:sha1:3da77feabb846d4bc357c3a2944aa20f07e0a880</id>
<content type='text'>
[ Upstream commit e1d2d1329a5722dbecc9c278303fcc4aa01f8790 ]

To avoid kernel warning "Unhandled message (68)", ignore the
CMD_FLUSH_QUEUE_REPLY message for now.

As of Leaf v2 firmware version v4.1.844 (2017-02-15), flush tx queue is
synchronous. There is a capability bit indicating whether flushing tx
queue is synchronous or asynchronous.

A proper solution would be to query the device for capabilities. If the
synchronous tx flush capability bit is set, we should wait for
CMD_FLUSH_QUEUE_REPLY message, while flushing the tx queue.

Signed-off-by: Jimmy Assarsson &lt;jimmyassarsson@gmail.com&gt;
Cc: linux-stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@verizon.com&gt;
</content>
</entry>
</feed>
