<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net, branch v4.6</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v4.6</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v4.6'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2016-05-14T01:12:07Z</updated>
<entry>
<title>drivers: net: xgene: fix register offset</title>
<updated>2016-05-14T01:12:07Z</updated>
<author>
<name>Iyappan Subramanian</name>
<email>isubramanian@apm.com</email>
</author>
<published>2016-05-13T23:53:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=e2f2d9a72605666ec772c865dbe89edbab896d27'/>
<id>urn:sha1:e2f2d9a72605666ec772c865dbe89edbab896d27</id>
<content type='text'>
This patch fixes SG_RX_DV_GATE_REG_0_ADDR register offset
and ring state field lengths.

Signed-off-by: Iyappan Subramanian &lt;isubramanian@apm.com&gt;
Tested-by: Toan Le &lt;toanle@apm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>drivers: net: xgene: fix statistics counters race condition</title>
<updated>2016-05-14T01:12:06Z</updated>
<author>
<name>Iyappan Subramanian</name>
<email>isubramanian@apm.com</email>
</author>
<published>2016-05-13T23:53:00Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3bb502f83080ad28abdd7404f29aa2fc743b28b5'/>
<id>urn:sha1:3bb502f83080ad28abdd7404f29aa2fc743b28b5</id>
<content type='text'>
This patch fixes the race condition on updating the statistics
counters by moving the counters to the ring structure.

Signed-off-by: Iyappan Subramanian &lt;isubramanian@apm.com&gt;
Tested-by: Toan Le &lt;toanle@apm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>drivers: net: xgene: fix ununiform latency across queues</title>
<updated>2016-05-14T01:12:06Z</updated>
<author>
<name>Iyappan Subramanian</name>
<email>isubramanian@apm.com</email>
</author>
<published>2016-05-13T23:52:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1b090a4839f6c74af2dc42872c9e9dc9d7c60a99'/>
<id>urn:sha1:1b090a4839f6c74af2dc42872c9e9dc9d7c60a99</id>
<content type='text'>
This patch addresses ununiform latency across queues by adding
more queues to match with, upto number of CPU cores.

Also, number of interrupts are increased and the channel numbers
are reordered.

Signed-off-by: Iyappan Subramanian &lt;isubramanian@apm.com&gt;
Tested-by: Toan Le &lt;toanle@apm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>drivers: net: xgene: fix sharing of irqs</title>
<updated>2016-05-14T01:12:06Z</updated>
<author>
<name>Iyappan Subramanian</name>
<email>isubramanian@apm.com</email>
</author>
<published>2016-05-13T23:52:58Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=46a22d29a51e40704c2260168c124e260b7d660e'/>
<id>urn:sha1:46a22d29a51e40704c2260168c124e260b7d660e</id>
<content type='text'>
Since hardware doesn't allow sharing of interrupts,
this patch fixes the same by removing IRQF_SHARED flag.

Signed-off-by: Iyappan Subramanian &lt;isubramanian@apm.com&gt;
Tested-by: Toan Le &lt;toanle@apm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>drivers: net: xgene: fix IPv4 forward crash</title>
<updated>2016-05-14T01:12:06Z</updated>
<author>
<name>Iyappan Subramanian</name>
<email>isubramanian@apm.com</email>
</author>
<published>2016-05-13T23:52:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=b30cfd241fbc6818c7de0cbf89ae83c70a1dac9a'/>
<id>urn:sha1:b30cfd241fbc6818c7de0cbf89ae83c70a1dac9a</id>
<content type='text'>
This patch fixes the crash observed during IPv4 forward test by
setting the drop field in the dbptr.

Signed-off-by: Iyappan Subramanian &lt;isubramanian@apm.com&gt;
Tested-by: Toan Le &lt;toanle@apm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>xen-netback: fix extra_info handling in xenvif_tx_err()</title>
<updated>2016-05-13T05:58:57Z</updated>
<author>
<name>Paul Durrant</name>
<email>Paul.Durrant@citrix.com</email>
</author>
<published>2016-05-12T13:43:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=72eec92accabe3ec34f27a9d3cd459bf5a877c33'/>
<id>urn:sha1:72eec92accabe3ec34f27a9d3cd459bf5a877c33</id>
<content type='text'>
Patch 562abd39 "xen-netback: support multiple extra info fragments
passed from frontend" contained a mistake which can result in an in-
correct number of responses being generated when handling errors
encountered when processing packets containing extra info fragments.
This patch fixes the problem.

Signed-off-by: Paul Durrant &lt;paul.durrant@citrix.com&gt;
Reported-by: Jan Beulich &lt;JBeulich@suse.com&gt;
Cc: Wei Liu &lt;wei.liu2@citrix.com&gt;
Acked-by: Wei Liu &lt;wei.liu2@citrix.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: mvneta: bm: fix dependencies again</title>
<updated>2016-05-12T20:56:30Z</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2016-05-11T20:13:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=2073dbad172f5d55545c1aadc5f7ce8792dfc060'/>
<id>urn:sha1:2073dbad172f5d55545c1aadc5f7ce8792dfc060</id>
<content type='text'>
I tried to fix this before, but my previous fix was incomplete
and we can still get the same link error in randconfig builds
because of the way that Kconfig treats the

	default y if MVNETA=y &amp;&amp; MVNETA_BM_ENABLE

line that does not actually trigger when MVNETA_BM_ENABLE=m,
unlike I intended.
Changing the line to use MVNETA_BM_ENABLE!=n however has
the desired effect and hopefully makes all configurations
work as expected.

Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Fixes: 019ded3aa7c9 ("net: mvneta: bm: clarify dependencies")
Acked-by: Gregory CLEMENT &lt;gregory.clement@free-electrons.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>bnxt_en: Add workaround to detect bad opaque in rx completion (part 2)</title>
<updated>2016-05-12T03:46:09Z</updated>
<author>
<name>Michael Chan</name>
<email>michael.chan@broadcom.com</email>
</author>
<published>2016-05-10T23:18:00Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=fa7e28127a5ad9fd55ac9c7707d8c8b835113a7c'/>
<id>urn:sha1:fa7e28127a5ad9fd55ac9c7707d8c8b835113a7c</id>
<content type='text'>
Add detection and recovery code when the hardware returned opaque value
does not match the expected consumer index.  Once the issue is detected,
we skip the processing of all RX and LRO/GRO packets.  These completion
entries are discarded without sending the SKB to the stack and without
producing new buffers.  The function will be reset from a workqueue.

Signed-off-by: Michael Chan &lt;michael.chan@broadcom.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>bnxt_en: Add workaround to detect bad opaque in rx completion (part 1)</title>
<updated>2016-05-12T03:46:09Z</updated>
<author>
<name>Michael Chan</name>
<email>michael.chan@broadcom.com</email>
</author>
<published>2016-05-10T23:17:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=376a5b8647d6c56cb8f104d7ad0390b4f4057e70'/>
<id>urn:sha1:376a5b8647d6c56cb8f104d7ad0390b4f4057e70</id>
<content type='text'>
There is a rare hardware bug that can cause a bad opaque value in the RX
or TPA completion.  When this happens, the hardware may have used the
same buffer twice for 2 rx packets.  In addition, the driver will also
crash later using the bad opaque as the index into the ring.

The rx opaque value is predictable and is always monotonically increasing.
The workaround is to keep track of the expected next opaque value and
compare it with the one returned by hardware during RX and TPA start
completions.  If they miscompare, we will not process any more RX and
TPA completions and exit NAPI.  We will then schedule a workqueue to
reset the function.

This patch adds the logic to keep track of the next rx consumer index.

Signed-off-by: Michael Chan &lt;michael.chan@broadcom.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>qlcnic: potential NULL dereference in qlcnic_83xx_get_minidump_template()</title>
<updated>2016-05-12T03:44:56Z</updated>
<author>
<name>Dan Carpenter</name>
<email>dan.carpenter@oracle.com</email>
</author>
<published>2016-05-10T19:20:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5f46feab87bb105d6a217d966b327fdc56696802'/>
<id>urn:sha1:5f46feab87bb105d6a217d966b327fdc56696802</id>
<content type='text'>
If qlcnic_fw_cmd_get_minidump_temp() fails then "fw_dump-&gt;tmpl_hdr" is
NULL or possibly freed.  It can lead to an oops later.

Fixes: d01a6d3c8ae1 ('qlcnic: Add support to enable capability to extend minidump for iSCSI')
Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
