<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/s390/net, branch linux-4.8.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.8.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.8.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2016-09-16T08:29:14Z</updated>
<entry>
<title>s390/qeth: fix setting VIPA address</title>
<updated>2016-09-16T08:29:14Z</updated>
<author>
<name>Thomas Richter</name>
</author>
<published>2016-09-15T12:39:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=732a59cb6e7faed7a40da6665a517945c95fc895'/>
<id>urn:sha1:732a59cb6e7faed7a40da6665a517945c95fc895</id>
<content type='text'>
commit 5f78e29ceebf ("qeth: optimize IP handling in rx_mode callback")
restructured the internal address handling.
This work broke setting a virtual IP address.
The command
echo 10.1.1.1 &gt; /sys/bus/ccwgroup/devices/&lt;device&gt;/vipa/add4
fails with file exist error even if the IP address has not
been set before.

It turned out that the search result for the IP address
search is handled incorrectly in the VIPA case.

This patch fixes the setting of an virtual IP address.

Signed-off-by: Thomas Richter &lt;tmricht@linux.vnet.ibm.com&gt;
Signed-off-by: Ursula Braun &lt;ubraun@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>qeth: do not turn on SG per default</title>
<updated>2016-09-16T08:29:14Z</updated>
<author>
<name>Ursula Braun</name>
</author>
<published>2016-09-15T12:39:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5722963a8e83309dad831cf6968c4c805aa342c0'/>
<id>urn:sha1:5722963a8e83309dad831cf6968c4c805aa342c0</id>
<content type='text'>
According to recent performance measurements, turning on net_device
feature NETIF_F_SG only behaves well, but turning on feature
NETIF_F_GSO shows bad results. Since the kernel activates NETIF_F_GSO
automatically as soon as the driver configures feature NETIF_F_SG, qeth
should not activate feature NETIF_F_SG per default, until the qeth
problems with NETIF_F_GSO are solved.

Signed-off-by: Ursula Braun &lt;ubraun@linux.vnet.ibm.com&gt;
Reviewed-by: Thomas Richter &lt;tmricht@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>qeth: do not limit number of gso segments</title>
<updated>2016-09-16T08:29:14Z</updated>
<author>
<name>Ursula Braun</name>
</author>
<published>2016-09-15T12:39:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=243f750fc6f5d8e4dec984a9a785941c67452b8f'/>
<id>urn:sha1:243f750fc6f5d8e4dec984a9a785941c67452b8f</id>
<content type='text'>
To reduce the need of skb_linearize() calls, gso_max_segs of qeth
net_devices had been limited according to the maximum number of qdio SBAL
elements. But a gso segment cannot be larger than the mtu-size, while an
SBAL element can contain up to 4096 bytes. The gso_max_segs limitation
limits the maximum packet size given to the qeth driver. Performance
measurements with tso-enabled qeth network interfaces and mtu-size 1500
showed, that the disadvantage of smaller packets is much more severe than
the advantage of fewer skb_linearize() calls.
This patch gets rid of the gso_max_segs limitations in the qeth driver.

Signed-off-by: Ursula Braun &lt;ubraun@linux.vnet.ibm.com&gt;
Reviewed-by: Thomas Richter &lt;tmricht@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>qeth: check not more than 16 SBALEs on the completion queue</title>
<updated>2016-09-16T08:29:13Z</updated>
<author>
<name>Ursula Braun</name>
</author>
<published>2016-09-15T12:39:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=903e48531e8b5d414c8f1960eacac24c31f60344'/>
<id>urn:sha1:903e48531e8b5d414c8f1960eacac24c31f60344</id>
<content type='text'>
af_iucv socket programs with HiperSockets as transport make use of the qdio
completion queue. Running such an af_iucv socket program may result in a
crash:

[90341.677709] Oops: 0038 ilc:2 [#1] SMP
[90341.677743] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.6.0-20160720.0.0e86ec7.5e62689.fc23.s390xperformance #1
[90341.677744] Hardware name: IBM              2964 N96              703              (LPAR)
[90341.677746] task: 00000000edb79f00 ti: 00000000edb84000 task.ti: 00000000edb84000
[90341.677748] Krnl PSW : 0704d00180000000 000000000075bc50 (qeth_qdio_input_handler+0x258/0x4e0)
[90341.677756]            R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3
Krnl GPRS: 000003d10391e900 0000000000000001 00000000e61e6000 0000000000000005
[90341.677759]            0000000000a9e6ec 5420040001a77400 0000000000000001 000000000000006f
[90341.677761]            00000000e0d83f00 0000000000000003 0000000000000010 5420040001a77400
[90341.677784]            000000007ba8b000 0000000000943fd0 000000000075bc4e 00000000ed3b3c10
[90341.677793] Krnl Code: 000000000075bc42: e320cc180004        lg      %r2,3096(%r12)
           000000000075bc48: c0e5ffffc5cc       brasl   %r14,7547e0
          #000000000075bc4e: 1816               lr      %r1,%r6
          &gt;000000000075bc50: ba19b008           cs      %r1,%r9,8(%r11)
           000000000075bc54: ec180041017e       cij     %r1,1,8,75bcd6
           000000000075bc5a: 5810b008           l       %r1,8(%r11)
           000000000075bc5e: ec16005c027e       cij     %r1,2,6,75bd16
           000000000075bc64: 5090b008           st      %r9,8(%r11)
[90341.677807] Call Trace:
[90341.677810] ([&lt;000000000075bbc0&gt;] qeth_qdio_input_handler+0x1c8/0x4e0)
[90341.677812] ([&lt;000000000070efbc&gt;] qdio_kick_handler+0x124/0x2a8)
[90341.677814] ([&lt;0000000000713570&gt;] __tiqdio_inbound_processing+0xf0/0xcd0)
[90341.677818] ([&lt;0000000000143312&gt;] tasklet_action+0x92/0x120)
[90341.677823] ([&lt;00000000008b6e72&gt;] __do_softirq+0x112/0x308)
[90341.677824] ([&lt;0000000000142bce&gt;] irq_exit+0xd6/0xf8)
[90341.677829] ([&lt;000000000010b1d2&gt;] do_IRQ+0x6a/0x88)
[90341.677830] ([&lt;00000000008b6322&gt;] io_int_handler+0x112/0x220)
[90341.677832] ([&lt;0000000000102b2e&gt;] enabled_wait+0x56/0xa8)
[90341.677833] ([&lt;0000000000000000&gt;]           (null))
[90341.677835] ([&lt;0000000000102e32&gt;] arch_cpu_idle+0x32/0x48)
[90341.677838] ([&lt;000000000018a126&gt;] cpu_startup_entry+0x266/0x2b0)
[90341.677841] ([&lt;0000000000113b38&gt;] smp_start_secondary+0x100/0x110)
[90341.677843] ([&lt;00000000008b68a6&gt;] restart_int_handler+0x62/0x78)
[90341.677845] ([&lt;00000000008b6588&gt;] psw_idle+0x3c/0x40)
[90341.677846] Last Breaking-Event-Address:
[90341.677848]  [&lt;00000000007547ec&gt;] qeth_dbf_longtext+0xc/0xc0
[90341.677849]
[90341.677850] Kernel panic - not syncing: Fatal exception in interrupt

qeth_qdio_cq_handler() analyzes SBALs on this completion queue, but does
not observe the limit of 16 SBAL elements per SBAL. This patch adds the
additional check to process not more than 16 SBAL elements.

Signed-off-by: Ursula Braun &lt;ubraun@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>s390/qeth: allow hsuid configuration in DOWN state</title>
<updated>2016-09-16T08:29:13Z</updated>
<author>
<name>Ursula Braun</name>
</author>
<published>2016-09-15T12:39:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a7531c1cc09855df5e33ceefe4fdfc2d74ccab19'/>
<id>urn:sha1:a7531c1cc09855df5e33ceefe4fdfc2d74ccab19</id>
<content type='text'>
The qeth IP address mapping logic has been reworked recently. It
causes now problems to specify qeth sysfs attribute "hsuid" in DOWN
state, which is allowed. Postpone registering or deregistering of
IP-addresses in this case.

Signed-off-by: Ursula Braun &lt;ubraun@linux.vnet.ibm.com&gt;
Reviewed-by: Thomas Richter &lt;tmricht@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>s390/qeth: use ip_lock for hsuid configuration</title>
<updated>2016-09-16T08:29:13Z</updated>
<author>
<name>Ursula Braun</name>
</author>
<published>2016-09-15T12:39:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=016930b88a1d6eb6e6b3287d593e13ca06986acc'/>
<id>urn:sha1:016930b88a1d6eb6e6b3287d593e13ca06986acc</id>
<content type='text'>
qeth_l3_dev_hsuid_store() changes the ip hash table, which
requires the ip_lock.

Signed-off-by: Ursula Braun &lt;ubraun@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>qeth: restore device features after recovery</title>
<updated>2016-09-16T08:29:13Z</updated>
<author>
<name>Hans Wippel</name>
</author>
<published>2016-09-15T12:39:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e830baa9c3f0023769ba9aab19eb44c892769d87'/>
<id>urn:sha1:e830baa9c3f0023769ba9aab19eb44c892769d87</id>
<content type='text'>
After device recovery, only a basic set of network device features is
enabled on the device. If features like checksum offloading or TSO were
enabled by the user before the recovery, this results in a mismatch
between the network device features, that the kernel assumes to be
enabled on the device, and the features actually enabled on the device.

This patch tries to restore previously set features, that require
changes on the device, after the recovery of a device. In case of an
error, the network device's features are changed to contain only the
features that are actually turned on.

Signed-off-by: Hans Wippel &lt;hwippel@linux.vnet.ibm.com&gt;
Signed-off-by: Ursula Braun &lt;ubraun@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net</title>
<updated>2016-07-06T17:35:22Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2016-07-06T17:35:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=30d0844bdcea9fb8b0b3c8abfa5547bc3bcf8baa'/>
<id>urn:sha1:30d0844bdcea9fb8b0b3c8abfa5547bc3bcf8baa</id>
<content type='text'>
Conflicts:
	drivers/net/ethernet/mellanox/mlx5/core/en.h
	drivers/net/ethernet/mellanox/mlx5/core/en_main.c
	drivers/net/usb/r8152.c

All three conflicts were overlapping changes.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>qeth: delete napi struct when removing a qeth device</title>
<updated>2016-07-05T06:32:08Z</updated>
<author>
<name>Ursula Braun</name>
</author>
<published>2016-07-04T12:07:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7831b4ff0d926e0deeaabef9db8800ed069a2757'/>
<id>urn:sha1:7831b4ff0d926e0deeaabef9db8800ed069a2757</id>
<content type='text'>
A qeth_card contains a napi_struct linked to the net_device during
device probing. This struct must be deleted when removing the qeth
device, otherwise Panic on oops can occur when qeth devices are
repeatedly removed and added.

Fixes: a1c3ed4c9ca ("qeth: NAPI support for l2 and l3 discipline")
Cc: stable@vger.kernel.org # v2.6.37+
Signed-off-by: Ursula Braun &lt;ubraun@linux.vnet.ibm.com&gt;
Tested-by: Alexander Klein &lt;ALKL@de.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>s390/qeth: fix indentation in qeth_l3_arp_query</title>
<updated>2016-06-17T05:16:13Z</updated>
<author>
<name>Sebastian Ott</name>
</author>
<published>2016-06-16T14:19:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=77a83ed10bcccf67e803d0eab7c8506c7546586a'/>
<id>urn:sha1:77a83ed10bcccf67e803d0eab7c8506c7546586a</id>
<content type='text'>
gcc-6 warns about obviously wrong indentation:
drivers/s390/net/qeth_l3_main.c: In function 'qeth_l3_arp_query':
drivers/s390/net/qeth_l3_main.c:2315:3: warning: this 'if' clause does not
guard... [-Wmisleading-indentation]
   if (copy_to_user(udata, qinfo.udata, 4))
   ^~
drivers/s390/net/qeth_l3_main.c:2317:4: note: ...this statement, but the
latter is misleadingly indented as if it is guarded by the 'if'
    goto free_and_out;
    ^~~~

Although this particular case is harmless, fix the indentation to get rid
of that warning and improve readability.

Signed-off-by: Sebastian Ott &lt;sebott@linux.vnet.ibm.com&gt;
Signed-off-by: Ursula Braun &lt;ubraun@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
