<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/net/can, 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-05-23T01:33:53Z</updated>
<entry>
<title>can: cc770: Fix use after free in cc770_tx_interrupt()</title>
<updated>2018-05-23T01:33:53Z</updated>
<author>
<name>Andri Yngvason</name>
<email>andri.yngvason@marel.com</email>
</author>
<published>2018-03-15T18:23:17Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=7cd55433682315d37976b3430b2bd76978d4e995'/>
<id>urn:sha1:7cd55433682315d37976b3430b2bd76978d4e995</id>
<content type='text'>
[ Upstream commit 9ffd7503944ec7c0ef41c3245d1306c221aef2be ]

This fixes use after free introduced by the last cc770 patch.

Signed-off-by: Andri Yngvason &lt;andri.yngvason@marel.com&gt;
Fixes: 746201235b3f ("can: cc770: Fix queue stall &amp; dropped RTR reply")
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: cc770: Fix queue stall &amp; dropped RTR reply</title>
<updated>2018-05-23T01:33:53Z</updated>
<author>
<name>Andri Yngvason</name>
<email>andri.yngvason@marel.com</email>
</author>
<published>2018-03-14T11:52:57Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a6133cf1545ae23b13619756e7312fb4fc39494e'/>
<id>urn:sha1:a6133cf1545ae23b13619756e7312fb4fc39494e</id>
<content type='text'>
[ Upstream commit 746201235b3f876792099079f4c6fea941d76183 ]

While waiting for the TX object to send an RTR, an external message with a
matching id can overwrite the TX data. In this case we must call the rx
routine and then try transmitting the message that was overwritten again.

The queue was being stalled because the RX event did not generate an
interrupt to wake up the queue again and the TX event did not happen
because the TXRQST flag is reset by the chip when new data is received.

According to the CC770 datasheet the id of a message object should not be
changed while the MSGVAL bit is set. This has been fixed by resetting the
MSGVAL bit before modifying the object in the transmit function and setting
it after. It is not enough to set &amp; reset CPUUPD.

It is important to keep the MSGVAL bit reset while the message object is
being modified. Otherwise, during RTR transmission, a frame with matching
id could trigger an rx-interrupt, which would cause a race condition
between the interrupt routine and the transmit function.

Signed-off-by: Andri Yngvason &lt;andri.yngvason@marel.com&gt;
Tested-by: Richard Weinberger &lt;richard@nod.at&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: cc770: Fix stalls on rt-linux, remove redundant IRQ ack</title>
<updated>2018-05-23T01:33:53Z</updated>
<author>
<name>Andri Yngvason</name>
<email>andri.yngvason@marel.com</email>
</author>
<published>2018-03-14T11:52:56Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=5d87c7df104640e19ea8b617da39951ec0728b10'/>
<id>urn:sha1:5d87c7df104640e19ea8b617da39951ec0728b10</id>
<content type='text'>
[ Upstream commit f4353daf4905c0099fd25fa742e2ffd4a4bab26a ]

This has been reported to cause stalls on rt-linux.

Suggested-by: Richard Weinberger &lt;richard@nod.at&gt;
Tested-by: Richard Weinberger &lt;richard@nod.at&gt;
Signed-off-by: Andri Yngvason &lt;andri.yngvason@marel.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: 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>
</feed>
