4.14.83-stable review
Subsystems (2)
Greg Kroah-Hartman
maintainercover 4.14.83-stable review
This is the start of the stable review cycle for the 4.14.83 release. There are 21 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Fri Nov 23 18:34:13 UTC 2018. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.83-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.14.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 4.14.83-rc1
Chris Paterson <[email protected]>
ARM: dts: r8a7793: Correct critical CPU temperature
Chris Paterson <[email protected]>
ARM: dts: r8a7791: Correct critical CPU temperature
Greg Kroah-Hartman <[email protected]>
Revert "x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation"
Eric Dumazet <[email protected]>
inet: frags: better deal with smp races
Frieder Schrempf <[email protected]>
usbnet: smsc95xx: disable carrier check while suspending
Stefan Wahren <[email protected]>
net: smsc95xx: Fix MTU range
Shalom Toledo <[email protected]>
mlxsw: spectrum: Fix IP2ME CPU policer configuration
Xin Long <[email protected]>
sctp: not increase stream's incnt before sending addstrm_in request
Martin Schiller <[email protected]>
net: phy: mdio-gpio: Fix working over slow can_sleep GPIOs
Xin Long <[email protected]>
sctp: fix strchange_flags name for Stream Change Event
Tristram Ha <[email protected]>
net: dsa: microchip: initialize mutex before use
Subash Abhinov Kasiviswanathan <[email protected]>
net: qualcomm: rmnet: Fix incorrect assignment of real_dev
Florian Fainelli <[email protected]>
net: systemport: Protect stop from timeout
Matthew Cover <[email protected]>
tuntap: fix multiqueue rx
Siva Reddy Kallam <[email protected]>
tg3: Add PHY reset for 5717/5719/5720 in change ring and flow control paths
Xin Long <[email protected]>
sctp: not allow to set asoc prsctp_enable by sockopt
Eric Dumazet <[email protected]>
net-gro: reset skb->pkt_type in napi_reuse_skb()
David Ahern <[email protected]>
ipv6: Fix PMTU updates for UDP/raw sockets in presence of VRF
Sabrina Dubroca <[email protected]>
ip_tunnel: don't force DF when MTU is locked
Michał Mirosław <[email protected]>
ibmvnic: fix accelerated VLAN handling
배석진 <[email protected]>
flow_dissector: do not dissect l4 ports for fragments
-------------
Diffstat:
Makefile | 4 +- arch/arm/boot/dts/r8a7791.dtsi | 2 +- arch/arm/boot/dts/r8a7793.dtsi | 2 +- arch/x86/kernel/cpu/bugs.c | 57 +++---------------------- drivers/net/dsa/microchip/ksz_common.c | 10 ++--- drivers/net/ethernet/broadcom/bcmsysport.c | 15 +++---- drivers/net/ethernet/broadcom/tg3.c | 18 +++++++- drivers/net/ethernet/ibm/ibmvnic.c | 2 +- drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 1 - drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c | 6 +-- drivers/net/phy/mdio-gpio.c | 10 ++--- drivers/net/tun.c | 6 ++- drivers/net/usb/smsc95xx.c | 9 ++++ include/uapi/linux/sctp.h | 2 + kernel/cpu.c | 11 +---- net/core/dev.c | 4 ++ net/core/flow_dissector.c | 4 +- net/ipv4/inet_fragment.c | 28 ++++++------ net/ipv4/ip_tunnel_core.c | 2 +- net/ipv6/route.c | 7 ++- net/sctp/socket.c | 26 +++-------- net/sctp/stream.c | 1 - 22 files changed, 96 insertions(+), 131 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/21 flow_dissector: do not dissect l4 ports for fragments
4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: 배석진 <[email protected]>
[ Upstream commit 62230715fd2453b3ba948c9d83cfb3ada9169169 ]
Only first fragment has the sport/dport information, not the following ones.
If we want consistent hash for all fragments, we need to ignore ports even for first fragment.
This bug is visible for IPv6 traffic, if incoming fragments do not have a flow label, since skb_get_hash() will give different results for first fragment and following ones.
It is also visible if any routing rule wants dissection and sport or dport.
See commit 5e5d6fed3741 ("ipv6: route: dissect flow in input path if fib rules need it") for details.
[edumazet] rewrote the changelog completely.
--- net/core/flow_dissector.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
net/core/flow_dissector.c +2 -2
@@ -838,8 +838,8 @@ ip_proto_again:break ; } -if (dissector_uses_key (flow_dissector, -FLOW_DISSECTOR_KEY_PORTS )) { +if (dissector_uses_key (flow_dissector,FLOW_DISSECTOR_KEY_PORTS ) && + !(key_control->flags &FLOW_DIS_IS_FRAGMENT )) { key_ports =skb_flow_dissector_target (flow_dissector,FLOW_DISSECTOR_KEY_PORTS , target_container);
Greg Kroah-Hartman
maintainerPATCH 2/21 ibmvnic: fix accelerated VLAN handling
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Michał Mirosław" <[email protected]>
[ Upstream commit e84b47941e15e6666afb8ee8b21d1c3fc1a013af ]
Don't request tag insertion when it isn't present in outgoing skb.
--- drivers/net/ethernet/ibm/ibmvnic.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/ibm/ibmvnic.c +1 -1
@@ -1259,7 +1259,7 @@ static int ibmvnic_xmit(struct sk_buff * tx_crq.v1.sge_len =cpu_to_be32 (skb->len); tx_crq.v1.ioba =cpu_to_be64 (data_dma_addr); -if (adapter->vlan_header_insertion) { +if (adapter->vlan_header_insertion &&skb_vlan_tag_present (skb)) { tx_crq.v1.flags2 |=IBMVNIC_TX_VLAN_INSERT ; tx_crq.v1.vlan_id =cpu_to_be16 (skb->vlan_tci); }
Greg Kroah-Hartman
maintainerPATCH 3/21 ip_tunnel: dont force DF when MTU is locked
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sabrina Dubroca <[email protected]>
[ Upstream commit 16f7eb2b77b55da816c4e207f3f9440a8cafc00a ]
The various types of tunnels running over IPv4 can ask to set the DF bit to do PMTU discovery. However, PMTU discovery is subject to the threshold set by the net.ipv4.route.min_pmtu sysctl, and is also disabled on routes with "mtu lock". In those cases, we shouldn't set the DF bit.
This patch makes setting the DF bit conditional on the route's MTU locking state.
This issue seems to be older than git history.
--- net/ipv4/ip_tunnel_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ipv4/ip_tunnel_core.c +1 -1
@@ -80,7 +80,7 @@ void iptunnel_xmit(struct sock *sk, stru iph->version =4 ; iph->ihl =sizeof (struct iphdr ) >>2 ; - iph->frag_off = df; + iph->frag_off =ip_mtu_locked (&rt->dst) ?0 : df; iph->protocol = proto; iph->tos = tos; iph->daddr = dst;
Greg Kroah-Hartman
maintainerPATCH 4/21 ipv6: Fix PMTU updates for UDP/raw sockets in presence of VRF
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Ahern <[email protected]>
[ Upstream commit 7ddacfa564870cdd97275fd87decb6174abc6380 ]
Preethi reported that PMTU discovery for UDP/raw applications is not working in the presence of VRF when the socket is not bound to a device. The problem is that ip6_sk_update_pmtu does not consider the L3 domain of the skb device if the socket is not bound. Update the function to set oif to the L3 master device if relevant.
--- net/ipv6/route.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
net/ipv6/route.c +5 -2
@@ -1547,10 +1547,13 @@ EXPORT_SYMBOL_GPL(ip6_update_pmtu);void ip6_sk_update_pmtu (struct sk_buff *skb,struct sock *sk,__be32 mtu) { +int oif = sk->sk_bound_dev_if;struct dst_entry *dst; -ip6_update_pmtu (skb,sock_net (sk), mtu, - sk->sk_bound_dev_if, sk->sk_mark, sk->sk_uid); +if (!oif && skb->dev) + oif =l3mdev_master_ifindex (skb->dev); + +ip6_update_pmtu (skb,sock_net (sk), mtu, oif, sk->sk_mark, sk->sk_uid); dst =__sk_dst_get (sk); if (!dst || !dst->obsolete ||
Greg Kroah-Hartman
maintainerPATCH 5/21 net-gro: reset skb->pkt_type in napi_reuse_skb()
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit 33d9a2c72f086cbf1087b2fd2d1a15aa9df14a7f ]
eth_type_trans() assumes initial value for skb->pkt_type is PACKET_HOST.
This is indeed the value right after a fresh skb allocation.
However, it is possible that GRO merged a packet with a different value (like PACKET_OTHERHOST in case macvlan is used), so we need to make sure napi->skb will have pkt_type set back to PACKET_HOST.
Otherwise, valid packets might be dropped by the stack because their pkt_type is not PACKET_HOST.
napi_reuse_skb() was added in commit 96e93eab2033 ("gro: Add internal interfaces for VLAN"), but this bug always has been there.
--- net/core/dev.c | 4 ++++ 1 file changed, 4 insertions(+)
net/core/dev.c +4 -0
@@ -4993,6 +4993,10 @@ static void napi_reuse_skb(struct napi_s skb->vlan_tci =0 ; skb->dev = napi->dev; skb->skb_iif =0 ; + +/* eth_type_trans() assumes pkt_type is PACKET_HOST */ + skb->pkt_type =PACKET_HOST ; + skb->encapsulation =0 ;skb_shinfo (skb)->gso_type =0 ; skb->truesize =SKB_TRUESIZE (skb_end_offset (skb));
Greg Kroah-Hartman
maintainerPATCH 6/21 sctp: not allow to set asoc prsctp_enable by sockopt
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Xin Long <[email protected]>
[ Upstream commit cc3ccf26f0649089b3a34a2781977755ea36e72c ]
As rfc7496#section4.5 says about SCTP_PR_SUPPORTED:
This socket option allows the enabling or disabling of the negotiation of PR-SCTP support for future associations. For existing associations, it allows one to query whether or not PR-SCTP support was negotiated on a particular association.
It means only sctp sock's prsctp_enable can be set.
Note that for the limitation of SCTP_{CURRENT|ALL}_ASSOC, we will add it when introducing SCTP_{FUTURE|CURRENT|ALL}_ASSOC for linux sctp in another patchset.
v1->v2:
- drop the params.assoc_id check as Neil suggested.
--- net/sctp/socket.c | 26 +++++--------------------- 1 file changed, 5 insertions(+), 21 deletions(-)
net/sctp/socket.c +5 -21
@@ -3750,32 +3750,16 @@ static int sctp_setsockopt_pr_supported( unsigned int optlen) {struct sctp_assoc_value params; -struct sctp_association *asoc; -int retval = -EINVAL ;if (optlen !=sizeof (params)) - goto out; +return -EINVAL ; -if (copy_from_user (¶ms, optval, optlen)) { - retval = -EFAULT ; - goto out; - } +if (copy_from_user (¶ms, optval, optlen)) +return -EFAULT ; - asoc =sctp_id2assoc (sk, params.assoc_id); -if (asoc) { - asoc->prsctp_enable = !!params.assoc_value; - }else if (!params.assoc_id) { -struct sctp_sock *sp =sctp_sk (sk); +sctp_sk (sk)->ep->prsctp_enable = !!params.assoc_value; - sp->ep->prsctp_enable = !!params.assoc_value; - }else { - goto out; - } - - retval =0 ; - -out: -return retval; +return 0 ; } static int sctp_setsockopt_default_prinfo(struct sock *sk,
Greg Kroah-Hartman
maintainerPATCH 7/21 tg3: Add PHY reset for 5717/5719/5720 in change ring and flow control paths
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Siva Reddy Kallam <[email protected]>
[ Upstream commit 59663e42199c93d1d7314d1446f6782fc4b1eb81 ]
This patch has the fix to avoid PHY lockup with 5717/5719/5720 in change ring and flow control paths. This patch solves the RX hang while doing continuous ring or flow control parameters with heavy traffic from peer.
--- drivers/net/ethernet/broadcom/tg3.c | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-)
drivers/net/ethernet/broadcom/tg3.c +16 -2
@@ -12395,6 +12395,7 @@ static int tg3_set_ringparam(struct net_ {struct tg3 *tp =netdev_priv (dev);int i, irq_sync =0 , err =0 ; +bool reset_phy = false; if ((ering->rx_pending > tp->rx_std_ring_mask) || (ering->rx_jumbo_pending > tp->rx_jmb_ring_mask) ||
@@ -12426,7 +12427,13 @@ static int tg3_set_ringparam(struct net_if (netif_running (dev)) {tg3_halt (tp,RESET_KIND_SHUTDOWN ,1 ); - err =tg3_restart_hw (tp, false); +/* Reset PHY to avoid PHY lock up */ +if (tg3_asic_rev (tp) ==ASIC_REV_5717 || +tg3_asic_rev (tp) ==ASIC_REV_5719 || +tg3_asic_rev (tp) ==ASIC_REV_5720 ) + reset_phy = true; + + err =tg3_restart_hw (tp, reset_phy);if (!err)tg3_netif_start (tp); }
@@ -12460,6 +12467,7 @@ static int tg3_set_pauseparam(struct net {struct tg3 *tp =netdev_priv (dev);int err =0 ; +bool reset_phy = false;if (tp->link_config.autoneg ==AUTONEG_ENABLE )tg3_warn_mgmt_link_flap (tp);
@@ -12550,7 +12558,13 @@ static int tg3_set_pauseparam(struct netif (netif_running (dev)) {tg3_halt (tp,RESET_KIND_SHUTDOWN ,1 ); - err =tg3_restart_hw (tp, false); +/* Reset PHY to avoid PHY lock up */ +if (tg3_asic_rev (tp) ==ASIC_REV_5717 || +tg3_asic_rev (tp) ==ASIC_REV_5719 || +tg3_asic_rev (tp) ==ASIC_REV_5720 ) + reset_phy = true; + + err =tg3_restart_hw (tp, reset_phy);if (!err)tg3_netif_start (tp); }
Greg Kroah-Hartman
maintainerPATCH 8/21 tuntap: fix multiqueue rx
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Matthew Cover <[email protected]>
[ Upstream commit 8ebebcba559a1bfbaec7bbda64feb9870b9c58da ]
When writing packets to a descriptor associated with a combined queue, the packets should end up on that queue.
Before this change all packets written to any descriptor associated with a tap interface end up on rx-0, even when the descriptor is associated with a different queue.
The rx traffic can be generated by either of the following.
1. a simple tap program which spins up multiple queues and writes packets to each of the file descriptors
2. tx from a qemu vm with a tap multiqueue netdev
The queue for rx traffic can be observed by either of the following (done on the hypervisor in the qemu case).
1. a simple netmap program which opens and reads from per-queue descriptors
2. configuring RPS and doing per-cpu captures with rxtxcpu
Alternatively, if you printk() the return value of skb_get_rx_queue() just before each instance of netif_receive_skb() in tun.c, you will get 65535 for every skb.
Calling skb_record_rx_queue() to set the rx queue to the queue_index fixes the association between descriptor and rx queue.
--- drivers/net/tun.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/net/tun.c +5 -1
@@ -1214,6 +1214,7 @@ static void tun_rx_batched(struct tun_stif (!rx_batched || (!more &&skb_queue_empty (queue))) {local_bh_disable (); +skb_record_rx_queue (skb, tfile->queue_index);netif_receive_skb (skb);local_bh_enable ();return ;
@@ -1233,8 +1234,11 @@ static void tun_rx_batched(struct tun_ststruct sk_buff *nskb;local_bh_disable (); -while ((nskb =__skb_dequeue (&process_queue))) +while ((nskb =__skb_dequeue (&process_queue))) { +skb_record_rx_queue (nskb, tfile->queue_index);netif_receive_skb (nskb); + } +skb_record_rx_queue (skb, tfile->queue_index);netif_receive_skb (skb);local_bh_enable (); }
Greg Kroah-Hartman
maintainerPATCH 9/21 net: systemport: Protect stop from timeout
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Florian Fainelli <[email protected]>
[ Upstream commit 7cb6a2a2c72c1ed8f42fb01f1a661281b568dead ]
A timing hazard exists when the network interface is stopped that allows a watchdog timeout to be processed by a separate core in parallel. This creates the potential for the timeout handler to wake the queues while the driver is shutting down, or access registers after their clocks have been removed.
The more common case is that the watchdog timeout will produce a warning message which doesn't lead to a crash. The chances of this are greatly increased by the fact that bcm_sysport_netif_stop stops the transmit queues which can easily precipitate a watchdog time- out because of stale trans_start data in the queues.
This commit corrects the behavior by ensuring that the watchdog timeout is disabled before enterring bcm_sysport_netif_stop. There are currently only two users of the bcm_sysport_netif_stop function:
close and suspend.
The close case already handles the issue by exiting the RUNNING state before invoking the driver close service.
The suspend case now performs the netif_device_detach to exit the PRESENT state before the call to bcm_sysport_netif_stop rather than after it.
These behaviors prevent any future scheduling of the driver timeout service during the window. The netif_tx_stop_all_queues function in bcm_sysport_netif_stop is replaced with netif_tx_disable to ensure synchronization with any transmit or timeout threads that may already be executing on other cores.
For symmetry, the netif_device_attach call upon resume is moved to after the call to bcm_sysport_netif_start. Since it wakes the transmit queues it is not necessary to invoke netif_tx_start_all_queues from bcm_sysport_netif_start so it is moved into the driver open service.
--- drivers/net/ethernet/broadcom/bcmsysport.c | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-)
drivers/net/ethernet/broadcom/bcmsysport.c +7 -8
@@ -1774,9 +1774,6 @@ static void bcm_sysport_netif_start(struintrl2_1_mask_clear (priv,0xffffffff ); elseintrl2_0_mask_clear (priv ,INTRL2_0_TDMA_MBDONE_MASK ); - -/* Last call before we start the real business */ -netif_tx_start_all_queues (dev); }static void rbuf_init (struct bcm_sysport_priv *priv)
@@ -1922,6 +1919,8 @@ static int bcm_sysport_open(struct net_dbcm_sysport_netif_start (dev); +netif_tx_start_all_queues (dev); +return 0 ; out_clear_rx_int:
@@ -1945,7 +1944,7 @@ static void bcm_sysport_netif_stop(strucstruct bcm_sysport_priv *priv =netdev_priv (dev);/* stop all software from updating hardware */ -netif_tx_stop_all_queues (dev); +netif_tx_disable (dev);napi_disable (&priv->napi);phy_stop (dev->phydev);
@@ -2267,12 +2266,12 @@ static int bcm_sysport_suspend(struct deif (!netif_running (dev))return 0 ; +netif_device_detach (dev); +bcm_sysport_netif_stop (dev);phy_suspend (dev->phydev); -netif_device_detach (dev); -/* Disable UniMAC RX */ umac_enable_set (priv,CMD_RX_EN ,0 );
@@ -2356,8 +2355,6 @@ static int bcm_sysport_resume(struct dev goto out_free_rx_ring; } -netif_device_attach (dev); -/* RX pipe enable */ topctrl_writel (priv,0 ,RX_FLUSH_CNTL );
@@ -2402,6 +2399,8 @@ static int bcm_sysport_resume(struct devbcm_sysport_netif_start (dev); +netif_device_attach (dev); +return 0 ; out_free_rx_ring:
Greg Kroah-Hartman
maintainerPATCH 10/21 net: qualcomm: rmnet: Fix incorrect assignment of real_dev
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Subash Abhinov Kasiviswanathan <[email protected]>
[ Upstream commit d02854dc1999ed3e7fd79ec700c64ac23ac0c458 ]
A null dereference was observed when a sysctl was being set from userspace and rmnet was stuck trying to complete some actions in the NETDEV_REGISTER callback. This is because the real_dev is set only after the device registration handler completes.
sysctl call stack -
<6> Unable to handle kernel NULL pointer dereference at
virtual address 00000108 <2> pc : rmnet_vnd_get_iflink+0x1c/0x28 <2> lr : dev_get_iflink+0x2c/0x40 <2> rmnet_vnd_get_iflink+0x1c/0x28 <2> inet6_fill_ifinfo+0x15c/0x234 <2> inet6_ifinfo_notify+0x68/0xd4 <2> ndisc_ifinfo_sysctl_change+0x1b8/0x234 <2> proc_sys_call_handler+0xac/0x100 <2> proc_sys_write+0x3c/0x4c <2> __vfs_write+0x54/0x14c <2> vfs_write+0xcc/0x188 <2> SyS_write+0x60/0xc0 <2> el0_svc_naked+0x34/0x38
device register call stack -
<2> notifier_call_chain+0x84/0xbc <2> raw_notifier_call_chain+0x38/0x48 <2> call_netdevice_notifiers_info+0x40/0x70 <2> call_netdevice_notifiers+0x38/0x60 <2> register_netdevice+0x29c/0x3d8 <2> rmnet_vnd_newlink+0x68/0xe8 <2> rmnet_newlink+0xa0/0x160 <2> rtnl_newlink+0x57c/0x6c8 <2> rtnetlink_rcv_msg+0x1dc/0x328 <2> netlink_rcv_skb+0xac/0x118 <2> rtnetlink_rcv+0x24/0x30 <2> netlink_unicast+0x158/0x1f0 <2> netlink_sendmsg+0x32c/0x338 <2> sock_sendmsg+0x44/0x60 <2> SyS_sendto+0x150/0x1ac <2> el0_svc_naked+0x34/0x38
--- drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c +3 -3
@@ -102,12 +102,14 @@ int rmnet_vnd_newlink(u8 id, struct net_struct rmnet_port *port, struct net_device *real_dev) { - struct rmnet_priv *priv; + struct rmnet_priv *priv = netdev_priv(rmnet_dev);int rc;if (port->rmnet_devices[id])return -EINVAL ; + priv->real_dev = real_dev; + rc =register_netdevice (rmnet_dev);if (!rc) { port->rmnet_devices[id] = rmnet_dev;
@@ -115,9 +117,7 @@ int rmnet_vnd_newlink(u8 id, struct net_ rmnet_dev->rtnl_link_ops = &rmnet_link_ops; - priv =netdev_priv (rmnet_dev); priv->mux_id = id; - priv->real_dev = real_dev;netdev_dbg (rmnet_dev,"rmnet dev created\n" ); }
Greg Kroah-Hartman
maintainerPATCH 11/21 net: dsa: microchip: initialize mutex before use
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tristram Ha <[email protected]>
[ Upstream commit 284fb78ed7572117846f8e1d1d8e3dbfd16880c2 ]
Initialize mutex before use. Avoid kernel complaint when CONFIG_DEBUG_LOCK_ALLOC is enabled.
--- drivers/net/dsa/microchip/ksz_common.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/net/dsa/microchip/ksz_common.c +5 -5
@@ -1104,11 +1104,6 @@ static int ksz_switch_init(struct ksz_de {int i; -mutex_init (&dev->reg_mutex); -mutex_init (&dev->stats_mutex); -mutex_init (&dev->alu_mutex); -mutex_init (&dev->vlan_mutex); - dev->ds->ops = &ksz_switch_ops;for (i =0 ; i <ARRAY_SIZE (ksz_switch_chips); i++) {
@@ -1193,6 +1188,11 @@ int ksz_switch_register(struct ksz_devicif (dev->pdata) dev->chip_id = dev->pdata->chip_id; +mutex_init (&dev->reg_mutex); +mutex_init (&dev->stats_mutex); +mutex_init (&dev->alu_mutex); +mutex_init (&dev->vlan_mutex); +if (ksz_switch_detect (dev))return -EINVAL ;
Greg Kroah-Hartman
maintainerPATCH 12/21 sctp: fix strchange_flags name for Stream Change Event
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Xin Long <[email protected]>
[ Upstream commit fd82d61ba142f0b83463e47064bf5460aac57b6e ]
As defined in rfc6525#section-6.1.3, SCTP_STREAM_CHANGE_DENIED and SCTP_STREAM_CHANGE_FAILED should be used instead of SCTP_ASSOC_CHANGE_DENIED and SCTP_ASSOC_CHANGE_FAILED.
To keep the compatibility, fix it by adding two macros.
--- include/uapi/linux/sctp.h | 2 ++ 1 file changed, 2 insertions(+)
include/uapi/linux/sctp.h +2 -0
@@ -519,6 +519,8 @@ struct sctp_assoc_reset_event {#define SCTP_ASSOC_CHANGE_DENIED 0x0004#define SCTP_ASSOC_CHANGE_FAILED 0x0008 +#define SCTP_STREAM_CHANGE_DENIED SCTP_ASSOC_CHANGE_DENIED +#define SCTP_STREAM_CHANGE_FAILED SCTP_ASSOC_CHANGE_FAILEDstruct sctp_stream_change_event {__u16 strchange_type;__u16 strchange_flags;
Greg Kroah-Hartman
maintainerPATCH 13/21 net: phy: mdio-gpio: Fix working over slow can_sleep GPIOs
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Martin Schiller <[email protected]>
[ Upstream commit df5a8ec64eed7fe45b556cfff503acd6429ab817 ]
Up until commit 7e5fbd1e0700 ("net: mdio-gpio: Convert to use gpiod functions where possible"), the _cansleep variants of the gpio_ API was used. After that commit and the change to gpiod_ API, the _cansleep() was dropped. This then results in WARN_ON() when used with GPIO devices which do sleep. Add back the _cansleep() to avoid this.
--- drivers/net/phy/mdio-gpio.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/net/phy/mdio-gpio.c +5 -5
@@ -79,7 +79,7 @@ static void mdio_dir(struct mdiobb_ctrl* assume the pin serves as pull-up. If direction is * output, the default value is high. */ -gpiod_set_value (bitbang->mdo,1 ); +gpiod_set_value_cansleep (bitbang->mdo,1 );return ; }
@@ -94,7 +94,7 @@ static int mdio_get(struct mdiobb_ctrl *struct mdio_gpio_info *bitbang = container_of(ctrl, struct mdio_gpio_info, ctrl); -return gpiod_get_value (bitbang->mdio); +return gpiod_get_value_cansleep (bitbang->mdio); }static void mdio_set (struct mdiobb_ctrl *ctrl,int what)
@@ -103,9 +103,9 @@ static void mdio_set(struct mdiobb_ctrl container_of(ctrl, struct mdio_gpio_info, ctrl);if (bitbang->mdo) -gpiod_set_value (bitbang->mdo, what); +gpiod_set_value_cansleep (bitbang->mdo, what);else -gpiod_set_value (bitbang->mdio, what); +gpiod_set_value_cansleep (bitbang->mdio, what); }static void mdc_set (struct mdiobb_ctrl *ctrl,int what)
@@ -113,7 +113,7 @@ static void mdc_set(struct mdiobb_ctrl *struct mdio_gpio_info *bitbang = container_of(ctrl, struct mdio_gpio_info, ctrl); -gpiod_set_value (bitbang->mdc, what); +gpiod_set_value_cansleep (bitbang->mdc, what); }static const struct mdiobb_ops mdio_gpio_ops = {
Greg Kroah-Hartman
maintainerPATCH 14/21 sctp: not increase streams incnt before sending addstrm_in request
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Xin Long <[email protected]>
[ Upstream commit e1e46479847e66f78f79d8c24d5169a5954b3fc2 ]
Different from processing the addstrm_out request, The receiver handles an addstrm_in request by sending back an addstrm_out request to the sender who will increase its stream's in and incnt later.
Now stream->incnt has been increased since it sent out the addstrm_in request in sctp_send_add_streams(), with the wrong stream->incnt will even cause crash when copying stream info from the old stream's in to the new one's in sctp_process_strreset_addstrm_out().
This patch is to fix it by simply removing the stream->incnt change from sctp_send_add_streams().
--- net/sctp/stream.c | 1 - 1 file changed, 1 deletion(-)
net/sctp/stream.c +0 -1
@@ -310,7 +310,6 @@ int sctp_send_add_streams(struct sctp_as goto out; } - stream->incnt = incnt; stream->outcnt = outcnt; asoc->strreset_outstanding = !!out + !!in;
Greg Kroah-Hartman
maintainerPATCH 15/21 mlxsw: spectrum: Fix IP2ME CPU policer configuration
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Shalom Toledo <[email protected]>
[ Upstream commit 96801552f846460fe9ac10f1b189602992f004e1 ]
The CPU policer used to police packets being trapped via a local route (IP2ME) was incorrectly configured to police based on bytes per second instead of packets per second.
Change the policer to police based on packets per second and avoid packet loss under certain circumstances.
--- drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 1 - 1 file changed, 1 deletion(-)
drivers/net/ethernet/mellanox/mlxsw/spectrum.c +0 -1
@@ -3471,7 +3471,6 @@ static int mlxsw_sp_cpu_policers_set(str burst_size =7 ;break ;case MLXSW_REG_HTGT_TRAP_GROUP_SP_IP2ME : - is_bytes = true; rate =4 *1024 ; burst_size =4 ;break ;
Greg Kroah-Hartman
maintainerPATCH 16/21 net: smsc95xx: Fix MTU range
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stefan Wahren <[email protected]>
[ Upstream commit 85b18b0237ce9986a81a1b9534b5e2ee116f5504 ]
The commit f77f0aee4da4 ("net: use core MTU range checking in USB NIC drivers") introduce a common MTU handling for usbnet. But it's missing the necessary changes for smsc95xx. So set the MTU range accordingly.
This patch has been tested on a Raspberry Pi 3.
--- drivers/net/usb/smsc95xx.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/net/usb/smsc95xx.c +2 -0
@@ -1321,6 +1321,8 @@ static int smsc95xx_bind(struct usbnet * dev->net->ethtool_ops = &smsc95xx_ethtool_ops; dev->net->flags |=IFF_MULTICAST ; dev->net->hard_header_len +=SMSC95XX_TX_OVERHEAD_CSUM ; + dev->net->min_mtu =ETH_MIN_MTU ; + dev->net->max_mtu =ETH_DATA_LEN ; dev->hard_mtu = dev->net->mtu + dev->net->hard_header_len; pdata->dev = dev;
Greg Kroah-Hartman
maintainerPATCH 17/21 usbnet: smsc95xx: disable carrier check while suspending
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Frieder Schrempf <[email protected]>
[ Upstream commit 7b900ead6cc66b2ee873cb042dfba169aa68b56c ]
We need to make sure, that the carrier check polling is disabled while suspending. Otherwise we can end up with usbnet_read_cmd() being issued when only usbnet_read_cmd_nopm() is allowed. If this happens, read operations lock up.
--- drivers/net/usb/smsc95xx.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/net/usb/smsc95xx.c +7 -0
@@ -1600,6 +1600,8 @@ static int smsc95xx_suspend(struct usb_ireturn ret; } +cancel_delayed_work_sync (&pdata->carrier_check); +if (pdata->suspend_flags) {netdev_warn (dev->net,"error during last resume\n" ); pdata->suspend_flags =0 ;
@@ -1842,6 +1844,11 @@ done:*/ if (ret &&PMSG_IS_AUTO (message))usbnet_resume (intf); + +if (ret) +schedule_delayed_work (&pdata->carrier_check, +CARRIER_CHECK_DELAY ); +return ret; }
Greg Kroah-Hartman
maintainerPATCH 18/21 inet: frags: better deal with smp races
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit 0d5b9311baf27bb545f187f12ecfd558220c607d ]
Multiple cpus might attempt to insert a new fragment in rhashtable, if for example RPS is buggy, as reported by 배석진 in
https://patchwork.ozlabs.org/patch/994601/
We use rhashtable_lookup_get_insert_key() instead of rhashtable_insert_fast() to let cpus losing the race free their own inet_frag_queue and use the one that was inserted by another cpu.
--- net/ipv4/inet_fragment.c | 28 +++++++++++++++------------- 1 file changed, 15 insertions(+), 13 deletions(-)
net/ipv4/inet_fragment.c +15 -13
@@ -180,21 +180,22 @@ static struct inet_frag_queue *inet_frag }static struct inet_frag_queue *inet_frag_create (struct netns_frags *nf, -void *arg) +void *arg, +struct inet_frag_queue **prev) {struct inet_frags *f = nf->f;struct inet_frag_queue *q; -int err; q =inet_frag_alloc (nf, f, arg); -if (!q) +if (!q) { + *prev =ERR_PTR (-ENOMEM );return NULL ; - + }mod_timer (&q->timer, jiffies + nf->timeout); - err =rhashtable_insert_fast (&nf->rhashtable, &q->node, - f->rhash_params); -if (err <0 ) { + *prev =rhashtable_lookup_get_insert_key (&nf->rhashtable, &q->key, + &q->node, f->rhash_params); +if (*prev) { q->flags |=INET_FRAG_COMPLETE ;inet_frag_kill (q);inet_frag_destroy (q);
@@ -206,19 +207,20 @@ static struct inet_frag_queue *inet_frag/* TODO : call from rcu_read_lock() and no longer use refcount_inc_not_zero() */ struct inet_frag_queue *inet_frag_find (struct netns_frags *nf,void *key) { -struct inet_frag_queue *fq; +struct inet_frag_queue *fq =NULL , *prev;rcu_read_lock (); - fq =rhashtable_lookup (&nf->rhashtable, key, nf->f->rhash_params); -if (fq) { + prev =rhashtable_lookup (&nf->rhashtable, key, nf->f->rhash_params); +if (!prev) + fq =inet_frag_create (nf, key, &prev); +if (prev && !IS_ERR (prev)) { + fq = prev;if (!refcount_inc_not_zero (&fq->refcnt)) fq =NULL ; -rcu_read_unlock (); -return fq; }rcu_read_unlock (); -return inet_frag_create (nf, key); +return fq; }EXPORT_SYMBOL (inet_frag_find);
Greg Kroah-Hartman
maintainerPATCH 19/21 Revert "x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation"
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Greg Kroah-Hartman <[email protected]>
This reverts commit 8a13906ae519b3ed95cd0fb73f1098b46362f6c4 which is commit 53c613fe6349994f023245519265999eed75957f upstream.
It's not ready for the stable trees as there are major slowdowns involved with this patch.
--- arch/x86/kernel/cpu/bugs.c | 57 ++++----------------------------------------- kernel/cpu.c | 11 -------- 2 files changed, 7 insertions(+), 61 deletions(-)
arch/x86/kernel/cpu/bugs.c +6 -51
@@ -34,10 +34,12 @@ static void __init spectre_v2_select_mitstatic void __init ssb_select_mitigation (void );static void __init l1tf_select_mitigation (void ); -/* The base value of the SPEC_CTRL MSR that always has to be preserved. */ -u64 x86_spec_ctrl_base; +/* +* Our boot-time value of the SPEC_CTRL MSR. We read it once so that any +* writes to SPEC_CTRL contain whatever reserved bits have been set. +*/ +u64 __ro_after_init x86_spec_ctrl_base;EXPORT_SYMBOL_GPL (x86_spec_ctrl_base); -static DEFINE_MUTEX (spec_ctrl_mutex);/* * The vendor and possibly platform specific bits which can be modified in
@@ -321,46 +323,6 @@ static enum spectre_v2_mitigation_cmd __return cmd; } -static bool stibp_needed (void ) -{ -if (spectre_v2_enabled ==SPECTRE_V2_NONE ) -return false; - -if (!boot_cpu_has (X86_FEATURE_STIBP )) -return false; - -return true; -} - -static void update_stibp_msr (void *info) -{ -wrmsrl (MSR_IA32_SPEC_CTRL , x86_spec_ctrl_base); -} - -void arch_smt_update (void ) -{ -u64 mask; - -if (!stibp_needed ()) -return ; - -mutex_lock (&spec_ctrl_mutex); - mask = x86_spec_ctrl_base; -if (cpu_smt_control ==CPU_SMT_ENABLED ) - mask |=SPEC_CTRL_STIBP ; -else - mask &= ~SPEC_CTRL_STIBP ; - -if (mask != x86_spec_ctrl_base) { -pr_info ("Spectre v2 cross-process SMT mitigation: %s STIBP\n" , - cpu_smt_control ==CPU_SMT_ENABLED ? -"Enabling" :"Disabling" ); - x86_spec_ctrl_base = mask; -on_each_cpu (update_stibp_msr,NULL ,1 ); - } -mutex_unlock (&spec_ctrl_mutex); -} -static void __init spectre_v2_select_mitigation (void ) {enum spectre_v2_mitigation_cmd cmd =spectre_v2_parse_cmdline ();
@@ -460,9 +422,6 @@ specv2_set_mode:setup_force_cpu_cap (X86_FEATURE_USE_IBRS_FW );pr_info ("Enabling Restricted Speculation for firmware calls\n" ); } - -/* Enable STIBP if appropriate */ -arch_smt_update (); }#undef pr_fmt
@@ -855,8 +814,6 @@ static ssize_t l1tf_show_state(char *bufstatic ssize_t cpu_show_common (struct device *dev,struct device_attribute *attr,char *buf,unsigned int bug) { -int ret; -if (!boot_cpu_has_bug (bug))return sprintf (buf,"Not affected\n" );
@@ -871,12 +828,10 @@ static ssize_t cpu_show_common(struct dereturn sprintf (buf,"Mitigation: __user pointer sanitization\n" );case X86_BUG_SPECTRE_V2 : - ret =sprintf (buf,"%s%s%s%s%s\n" , spectre_v2_strings[spectre_v2_enabled], +return sprintf (buf,"%s%s%s%s\n" , spectre_v2_strings[spectre_v2_enabled],boot_cpu_has (X86_FEATURE_USE_IBPB ) ?", IBPB" :"" ,boot_cpu_has (X86_FEATURE_USE_IBRS_FW ) ?", IBRS_FW" :"" , - (x86_spec_ctrl_base &SPEC_CTRL_STIBP ) ?", STIBP" :"" ,spectre_v2_module_string ()); -return ret;case X86_BUG_SPEC_STORE_BYPASS :return sprintf (buf,"%s\n" , ssb_strings[ssb_mode]);
kernel/cpu.c +1 -10
@@ -2045,12 +2045,6 @@ static void cpuhp_online_cpu_device(unsikobject_uevent (&dev->kobj,KOBJ_ONLINE ); } -/* -* Architectures that need SMT-specific errata handling during SMT hotplug -* should override this. -*/ -void __weak arch_smt_update (void ) { }; -static int cpuhp_smt_disable (enum cpuhp_smt_control ctrlval) {int cpu, ret =0 ;
@@ -2077,10 +2071,8 @@ static int cpuhp_smt_disable(enum cpuhp_*/ cpuhp_offline_cpu_device (cpu); } -if (!ret) { +if (!ret) cpu_smt_control = ctrlval; -arch_smt_update (); - }cpu_maps_update_done ();return ret; }
@@ -2091,7 +2083,6 @@ static int cpuhp_smt_enable(void)cpu_maps_update_begin (); cpu_smt_control =CPU_SMT_ENABLED ; -arch_smt_update ();for_each_present_cpu (cpu) {/* Skip online CPUs and CPUs on offline nodes */ if (cpu_online (cpu) || !node_online (cpu_to_node (cpu)))
Greg Kroah-Hartman
maintainerPATCH 20/21 ARM: dts: r8a7791: Correct critical CPU temperature
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chris Paterson <[email protected]>
commit e4fdf59bcce3b490bbc7197145bcb9f9d5a18cd3 upstream.
The R-Car M2W hardware manual states that Tc = –40°C to +105°C. The thermal sensor has an accuracy of ±5°C and there can be a temperature difference of 1 or 2 degrees between Tjmax and the thermal sensor due to the location of the latter.
This means that 95°C is a safer value to use.
--- arch/arm/boot/dts/r8a7791.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/boot/dts/r8a7791.dtsi +1 -1
@@ -91,7 +91,7 @@ trips { cpu-crit { - temperature = <115000>; + temperature = <95000>; hysteresis = <0>; type = "critical"; };
Greg Kroah-Hartman
maintainerPATCH 21/21 ARM: dts: r8a7793: Correct critical CPU temperature
In reply to Greg Kroah-Hartman4.14-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chris Paterson <[email protected]>
commit 1dfc65cef481ac6af64380f26186d5cc585b46eb upstream.
The R-Car M2N hardware manual states that Tc = –40°C to +105°C. The thermal sensor has an accuracy of ±5°C and there can be a temperature difference of 1 or 2 degrees between Tjmax and the thermal sensor due to the location of the latter.
This means that 95°C is a safer value to use.
--- arch/arm/boot/dts/r8a7793.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/boot/dts/r8a7793.dtsi +1 -1
@@ -88,7 +88,7 @@ trips { cpu-crit { - temperature = <115000>; + temperature = <95000>; hysteresis = <0>; type = "critical"; };
stable-rc/linux-4.14.y boot: 92 boots: 0 failed, 89 passed with 3 offline (v4.14.82-22-gaa2838d50dfb)
stable-rc/linux-4.14.y boot: 92 boots: 0 failed, 89 passed with 3 offline (v4.14.82-22-gaa2838d50dfb)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.82-22-gaa2838d50dfb/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.82-22-gaa2838d50dfb/
Tree: stable-rc
Branch: linux-4.14.y
Git Describe: v4.14.82-22-gaa2838d50dfb
Git Commit: aa2838d50dfbecf82e5ba9e1013d3057c54590b2
Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 53 unique boards, 21 SoC families, 15 builds out of 197
Offline Platforms:
arm:
multi_v7_defconfig:
stih410-b2120: 1 offline labarm64:
defconfig:
meson-gxl-s905d-p230: 1 offline lab
meson-gxl-s905x-p212: 1 offline lab---
For more info write to <[email protected]>
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.83 release. There are 21 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Fri Nov 23 18:34:13 UTC 2018. Anything received after that time might be too late.
Build results:
total: 150 pass: 150 fail: 0 Qemu test results: total: 293 pass: 293 fail: 0
Details are available at https://kerneltests.org/builders/.
Guenter
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.83 release. There are 21 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Fri Nov 23 18:34:13 UTC 2018. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.83-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.14.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
Summary
------------------------------------------------------------------------
kernel: 4.14.83-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.14.y
git commit: aa2838d50dfbecf82e5ba9e1013d3057c54590b2
git describe: v4.14.82-22-gaa2838d50dfb
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.82-22-gaa2838d50dfb
No regressions (compared to build v4.14.82)
No fixes (compared to build v4.14.82)
Ran 21240 total tests in the following environments and test suites.
Environments
--------------
- dragonboard-410c - arm64
- hi6220-hikey - arm64
- i386
- juno-r2 - arm64
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15 - arm
- x86_64
Test Suites
-----------
* boot
* install-android-platform-tools-r2600
* kselftest
* libhugetlbfs
* ltp-cap_bounds-tests
* ltp-containers-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-nptl-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-timers-tests
* ltp-cve-tests
* ltp-fsx-tests
* ltp-open-posix-tests
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Greg Kroah-Hartman
maintainerQuoted 17 lines · Naresh Kamboju
Quoted 15 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.83 release. There are 21 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Fri Nov 23 18:34:13 UTC 2018. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.83-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.14.y
and the diffstat can be found below.
Quoted 6 lines
Quoted 3 lines
thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm,x86_64, and i386.
Thanks for testing this and letting me know.
greg k-h
Jon Hunter
maintainerQuoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.83 release. There are 21 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Fri Nov 23 18:34:13 UTC 2018. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.83-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.14.y
and the diffstat can be found below.thanks,
greg k-h
All tests are passing for Tegra ...
Test results for stable-v4.14:
8 builds: 8 pass, 0 fail
16 boots: 16 pass, 0 fail
14 tests: 14 pass, 0 failLinux version: 4.14.83-rc1-gaa2838d
Boards tested: tegra124-jetson-tk1, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a04
Cheers
Jon
Signature · 1 line
nvpublic