[PATCH 5.0 000/137] 5.0.17-stable review

2019-05-15 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.0.17 release. There are 137 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 17 May 2019 09:04:31 AM UTC. Anything

[PATCH 5.0 039/137] afs: Unlock pages for __pagevec_release()

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 21bd68f196ca91fc0f3d9bd1b32f6e530e8c1c88 ] __pagevec_release() complains loudly if any page in the vector is still locked. The pages need to be locked for generic_error_remove_page(), but that function doesn't actually unlock them. Unlock the pages afterwards. Signed-off-by:

[PATCH 5.0 037/137] vxge: fix return of a freed memblock on a failed dma mapping

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 0a2c34f18c94b596562bf3d019fceab998b8b584 ] Currently if a pci dma mapping failure is detected a free'd memblock address is returned rather than a NULL (that indicates an error). Fix this by ensuring NULL is returned on this error case. Addresses-Coverity: ("Use after free")

[PATCH 5.0 045/137] drm/amd/display: If one stream full updates, full update all planes

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit c238bfe0be9ef7420f7669a69e27c8c8f4d8a568 ] [Why] On some compositors, with two monitors attached, VT terminal switch can cause a graphical issue by the following means: There are two streams, one for each monitor. Each stream has one plane current state: M1:S1->P1

[PATCH 5.0 007/137] selftests/seccomp: Handle namespace failures gracefully

2019-05-15 Thread Greg Kroah-Hartman
From: Kees Cook commit 9dd3fcb0ab73cb1e00b8562ef027a38521aaff87 upstream. When running without USERNS or PIDNS the seccomp test would hang since it was waiting forever for the child to trigger the user notification since it seems the glibc() abort handler makes a call to getpid(), which would

[PATCH 5.0 009/137] virt: vbox: Sanity-check parameter types for hgcm-calls coming from userspace

2019-05-15 Thread Greg Kroah-Hartman
From: Hans de Goede commit cf4f2ad6b87dda2dbe0573b1ebeb0273f8d4aac6 upstream. Userspace can make host function calls, called hgcm-calls through the /dev/vboxguest device. In this case we should not accept all hgcm-function-parameter-types, some are only valid for in kernel calls. This commit

[PATCH 5.0 019/137] libnvdimm/btt: Fix a kmemdup failure check

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 486fa92df4707b5df58d6508728bdb9321a59766 ] In case kmemdup fails, the fix releases resources and returns to avoid the NULL pointer dereference. Signed-off-by: Aditya Pakki Signed-off-by: Dan Williams Signed-off-by: Sasha Levin --- drivers/nvdimm/btt_devs.c | 18

[PATCH 5.0 005/137] hwmon: (pwm-fan) Disable PWM if fetching cooling data fails

2019-05-15 Thread Greg Kroah-Hartman
From: Stefan Wahren commit 53f1647da3e8fb3e89066798f0fdc045064d353d upstream. In case pwm_fan_of_get_cooling_data() fails we should disable the PWM just like in the other error cases. Fixes: 2e5219c77183 ("hwmon: (pwm-fan) Read PWM FAN configuration from device tree") Cc: # 4.14+

[PATCH 5.0 006/137] hwmon: (occ) Fix extended status bits

2019-05-15 Thread Greg Kroah-Hartman
From: Lei YU commit b88c5049219a7f322bb1fd65fc30d17472a23563 upstream. The occ's extended status is checked and shown as sysfs attributes. But the code was incorrectly checking the "status" bits. Fix it by checking the "ext_status" bits. Cc: sta...@vger.kernel.org Fixes: df04ced684d4 ("hwmon

[PATCH 5.0 020/137] s390/dasd: Fix capacity calculation for large volumes

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 2cc9637ce825f3a9f51f8f78af7474e9e85bfa5f ] The DASD driver incorrectly limits the maximum number of blocks of ECKD DASD volumes to 32 bit numbers. Volumes with a capacity greater than 2^32-1 blocks are incorrectly recognized as smaller volumes. This results in the following

[PATCH 4.19 094/113] net: ethernet: stmmac: dwmac-sun8i: enable support of unicast filtering

2019-05-15 Thread Greg Kroah-Hartman
From: Corentin Labbe [ Upstream commit d4c26eb6e721683a0f93e346ce55bc8dc3cbb175 ] When adding more MAC addresses to a dwmac-sun8i interface, the device goes directly in promiscuous mode. This is due to IFF_UNICAST_FLT missing flag. So since the hardware support unicast filtering, let's add

[PATCH 5.0 018/137] HID: input: add mapping for "Toggle Display" key

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit c01908a14bf735b871170092807c618bb9dae654 ] According to HUT 1.12 usage 0xb5 from the generic desktop page is reserved for switching between external and internal display, so let's add the mapping. Signed-off-by: Dmitry Torokhov Signed-off-by: Sasha Levin ---

[PATCH 4.19 104/113] isdn: bas_gigaset: use usb_fill_int_urb() properly

2019-05-15 Thread Greg Kroah-Hartman
From: Paul Bolle [ Upstream commit 4014dfae3ccaaf3ec19c9ae0691a3f14e7132eae ] The switch to make bas_gigaset use usb_fill_int_urb() - instead of filling that urb "by hand" - missed the subtle ordering of the previous code. See, before the switch urb->dev was set to a member somewhere deep in a

[PATCH 4.19 103/113] tuntap: synchronize through tfiles array instead of tun->numqueues

2019-05-15 Thread Greg Kroah-Hartman
From: Jason Wang [ Upstream commit 9871a9e47a2646fe30ae7fd2e67668a8d30912f6 ] When a queue(tfile) is detached through __tun_detach(), we move the last enabled tfile to the position where detached one sit but don't NULL out last position. We expect to synchronize the datapath through

[PATCH 4.19 110/113] powerpc/booke64: set RI in default MSR

2019-05-15 Thread Greg Kroah-Hartman
From: Laurentiu Tudor commit 5266e58d6cd90ac85c187d673093ad9cb649e16d upstream. Set RI in the default kernel's MSR so that the architected way of detecting unrecoverable machine check interrupts has a chance to work. This is inline with the MSR setup of the rest of booke powerpc architectures

[PATCH 4.19 096/113] net: seeq: fix crash caused by not set dev.parent

2019-05-15 Thread Greg Kroah-Hartman
From: Thomas Bogendoerfer [ Upstream commit 5afcd14cfc7fed1bcc8abcee2cef82732772bfc2 ] The old MIPS implementation of dma_cache_sync() didn't use the dev argument, but commit c9eb6172c328 ("dma-mapping: turn dma_cache_sync into a dma_map_ops method") changed that, so we now need to set

[PATCH 4.19 100/113] vlan: disable SIOCSHWTSTAMP in container

2019-05-15 Thread Greg Kroah-Hartman
From: Hangbin Liu [ Upstream commit 873017af778439f2f8e3d87f28ddb1fcaf244a76 ] With NET_ADMIN enabled in container, a normal user could be mapped to root and is able to change the real device's rx filter via ioctl on vlan, which would affect the other ptp process on host. Fix it by disabling

[PATCH 4.19 086/113] um: Dont hardcode path as it is architecture dependent

2019-05-15 Thread Greg Kroah-Hartman
From: Ritesh Raj Sarraf commit 9ca19a3a3e2482916c475b90f3d7fa2a03d8e5ed upstream. The current code fails to run on amd64 because of hardcoded reference to i386 Signed-off-by: Ritesh Raj Sarraf Signed-off-by: Richard Weinberger Signed-off-by: Greg Kroah-Hartman ---

[PATCH 5.0 012/137] iio: adc: xilinx: fix potential use-after-free on probe

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 862e4644fd2d7df8998edc65e0963ea2f567bde9 ] If probe errors out after request_irq(), its error path does not explicitly cancel the delayed work, which may have been scheduled by the interrupt handler. This means the delayed work may still be running when the core frees the

[PATCH 5.0 024/137] mac80211: fix memory accounting with A-MSDU aggregation

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit eb9b64e3a9f8483e6e54f4e03b2ae14ae5db2690 ] skb->truesize can change due to memory reallocation or when adding extra fragments. Adjust fq->memory_usage accordingly Signed-off-by: Felix Fietkau Acked-by: Toke Høiland-Jørgensen Signed-off-by: Johannes Berg Signed-off-by: Sasha

[PATCH 4.19 102/113] tuntap: fix dividing by zero in ebpf queue selection

2019-05-15 Thread Greg Kroah-Hartman
From: Jason Wang [ Upstream commit a35d310f03a692bf4798eb309a1950a06a150620 ] We need check if tun->numqueues is zero (e.g for the persist device) before trying to use it for modular arithmetic. Reported-by: Eric Dumazet Fixes: 96f84061620c6("tun: add eBPF based queue selection method")

[PATCH 5.0 023/137] cfg80211: Handle WMM rules in regulatory domain intersection

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 08a75a887ee46828b54600f4bb7068d872a5edd5 ] The support added for regulatory WMM rules did not handle the case of regulatory domain intersections. Fix it. Signed-off-by: Ilan Peer Fixes: 230ebaa189af ("cfg80211: read wmm rules from regulatory database") Signed-off-by: Luca

[PATCH 4.19 111/113] PCI: hv: Fix a memory leak in hv_eject_device_work()

2019-05-15 Thread Greg Kroah-Hartman
From: Dexuan Cui commit 05f151a73ec2b23ffbff706e5203e729a995cdc2 upstream. When a device is created in new_pcichild_device(), hpdev->refs is set to 2 (i.e. the initial value of 1 plus the get_pcichild()). When we hot remove the device from the host, in a Linux VM we first call

[PATCH 5.0 010/137] USB: serial: fix unthrottle races

2019-05-15 Thread Greg Kroah-Hartman
From: Johan Hovold commit 3f5edd58d040bfa4b74fb89bc02f0bc6b9cd06ab upstream. Fix two long-standing bugs which could potentially lead to memory corruption or leave the port throttled until it is reopened (on weakly ordered systems), respectively, when read-URB completion races with unthrottle().

[PATCH 4.19 107/113] drivers/virt/fsl_hypervisor.c: prevent integer overflow in ioctl

2019-05-15 Thread Greg Kroah-Hartman
From: Dan Carpenter commit 6a024330650e24556b8a18cc654ad00cfecf6c6c upstream. The "param.count" value is a u64 thatcomes from the user. The code later in the function assumes that param.count is at least one and if it's not then it leads to an Oops when we dereference the ZERO_SIZE_PTR. Also

[PATCH 4.19 101/113] vrf: sit mtu should not be updated when vrf netdev is the link

2019-05-15 Thread Greg Kroah-Hartman
From: Stephen Suryaputra [ Upstream commit ff6ab32bd4e073976e4d8797b4d514a172cfe6cb ] VRF netdev mtu isn't typically set and have an mtu of 65536. When the link of a tunnel is set, the tunnel mtu is changed from 1480 to the link mtu minus tunnel header. In the case of VRF netdev is the link,

[PATCH 4.19 098/113] packet: Fix error path in packet_init

2019-05-15 Thread Greg Kroah-Hartman
From: YueHaibing [ Upstream commit 36096f2f4fa05f7678bc87397665491700bae757 ] kernel BUG at lib/list_debug.c:47! invalid opcode: [#1 CPU: 0 PID: 12914 Comm: rmmod Tainted: GW 5.1.0+ #47 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS

[PATCH 4.19 092/113] ipv4: Fix raw socket lookup for local traffic

2019-05-15 Thread Greg Kroah-Hartman
From: David Ahern [ Upstream commit 19e4e768064a87b073a4b4c138b55db70e0cfb9f ] inet_iif should be used for the raw socket lookup. inet_iif considers rt_iif which handles the case of local traffic. As it stands, ping to a local address with the '-I ' option fails ever since ping was changed to

[PATCH 5.0 022/137] mac80211: Increase MAX_MSG_LEN

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 78be2d21cc1cd3069c6138dcfecec62583130171 ] Looks that 100 chars isn't enough for messages, as we keep getting warnings popping from different places due to message shortening. Instead of trying to shorten the prints, just increase the buffer size. Signed-off-by: Andrei

[PATCH 4.19 087/113] powerpc/64s: Include cpu header

2019-05-15 Thread Greg Kroah-Hartman
From: Breno Leitao commit 42e2acde1237878462b028f5a27d9cc5bea7502c upstream. Current powerpc security.c file is defining functions, as cpu_show_meltdown(), cpu_show_spectre_v{1,2} and others, that are being declared at linux/cpu.h header without including the header file that contains these

[PATCH 5.0 011/137] iio: adc: xilinx: fix potential use-after-free on remove

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 62039b6aef63380ba7a37c113bbaeee8a55c5342 ] When cancel_delayed_work() returns, the delayed work may still be running. This means that the core could potentially free the private structure (struct xadc) while the delayed work is still using it. This is a potential use-after-free.

[PATCH 4.19 088/113] bonding: fix arp_validate toggling in active-backup mode

2019-05-15 Thread Greg Kroah-Hartman
From: Jarod Wilson [ Upstream commit a9b8a2b39ce65df45687cf9ef648885c2a99fe75 ] There's currently a problem with toggling arp_validate on and off with an active-backup bond. At the moment, you can start up a bond, like so: modprobe bonding mode=1 arp_interval=100 arp_validate=0

[PATCH 4.19 112/113] PCI: hv: Add hv_pci_remove_slots() when we unload the driver

2019-05-15 Thread Greg Kroah-Hartman
From: Dexuan Cui commit 15becc2b56c6eda3d9bf5ae993bafd5661c1fad1 upstream. When we unload the pci-hyperv host controller driver, the host does not send us a PCI_EJECT message. In this case we also need to make sure the sysfs PCI slot directory is removed, otherwise a command on a slot file eg:

[PATCH 5.0 015/137] libnvdimm/namespace: Fix a potential NULL pointer dereference

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 55c1fc0af29a6c1b92f217b7eb7581a882e0c07c ] In case kmemdup fails, the fix goes to blk_err to avoid NULL pointer dereference. Signed-off-by: Kangjie Lu Signed-off-by: Dan Williams Signed-off-by: Sasha Levin --- drivers/nvdimm/namespace_devs.c | 5 - 1 file changed, 4

[PATCH 4.19 043/113] scsi: aic7xxx: fix EISA support

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 144ec97493af34efdb77c5aba146e9c7de8d0a06 ] Instead of relying on the now removed NULL argument to pci_alloc_consistent, switch to the generic DMA API, and store the struct device so that we can pass it. Fixes: 4167b2ad5182 ("PCI: Remove NULL device handling from PCI DMA API")

[PATCH 4.19 083/113] mwl8k: Fix rate_idx underflow

2019-05-15 Thread Greg Kroah-Hartman
From: Petr Štetiar commit 6b583201fa219b7b1b6aebd8966c8fd9357ef9f4 upstream. It was reported on OpenWrt bug tracking system[1], that several users are affected by the endless reboot of their routers if they configure 5GHz interface with channel 44 or 48. The reboot loop is caused by the

[PATCH 4.19 048/113] netfilter: ctnetlink: dont use conntrack/expect object addresses as id

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 3c79107631db1f7fd32cf3f7368e4672004a3010 ] else, we leak the addresses to userspace via ctnetlink events and dumps. Compute an ID on demand based on the immutable parts of nf_conn struct. Another advantage compared to using an address is that there is no immediate re-use of

[PATCH 4.19 084/113] rtlwifi: rtl8723ae: Fix missing break in switch statement

2019-05-15 Thread Greg Kroah-Hartman
From: Gustavo A. R. Silva commit 84242b82d81c54e009a2aaa74d3d9eff70babf56 upstream. Add missing break statement in order to prevent the code from falling through to case 0x1025, and erroneously setting rtlhal->oem_id to RT_CID_819X_ACER when rtlefuse->eeprom_svid is equal to 0x10EC and none of

[PATCH 4.19 044/113] mm: fix inactive list balancing between NUMA nodes and cgroups

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 3b991208b897f52507168374033771a984b947b1 ] During !CONFIG_CGROUP reclaim, we expand the inactive list size if it's thrashing on the node that is about to be reclaimed. But when cgroups are enabled, we suddenly ignore the node scope and use the cgroup scope only. The result is

[PATCH 4.19 080/113] nfc: nci: Potential off by one in ->pipes[] array

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 6491d698396fd5da4941980a35ca7c162a672016 ] This is similar to commit e285d5bfb7e9 ("NFC: Fix the number of pipes") where we changed NFC_HCI_MAX_PIPES from 127 to 128. As the comment next to the define explains, the pipe identifier is 7 bits long. The highest possible pipe is

[PATCH 4.19 045/113] init: initialize jump labels before command line option parsing

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 6041186a32585fc7a1d0f6cfe2f138b05fdc3c82 ] When a module option, or core kernel argument, toggles a static-key it requires jump labels to be initialized early. While x86, PowerPC, and ARM64 arrange for jump_label_init() to be called before parse_args(), ARM does not. Kernel

[PATCH 4.19 047/113] ipvs: do not schedule icmp errors from tunnels

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 0261ea1bd1eb0da5c0792a9119b8655cf33c80a3 ] We can receive ICMP errors from client or from tunneling real server. While the former can be scheduled to real server, the latter should not be scheduled, they are decapsulated only when existing connection is found. Fixes:

[PATCH 4.19 039/113] KVM: x86: avoid misreporting level-triggered irqs as edge-triggered in tracing

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 7a223e06b1a411cef6c4cd7a9b9a33c8d225b10e ] In __apic_accept_irq() interface trig_mode is int and actually on some code paths it is set above u8: kvm_apic_set_irq() extracts it from 'struct kvm_lapic_irq' where trig_mode is u16. This is done on purpose as e.g. kvm_set_msi_irq()

[PATCH 4.19 079/113] NFC: nci: Add some bounds checking in nci_hci_cmd_received()

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit d7ee81ad09f072eab1681877fc71ec05f9c1ae92 ] This is similar to commit 674d9de02aa7 ("NFC: Fix possible memory corruption when handling SHDLC I-Frame commands"). I'm not totally sure, but I think that commit description may have overstated the danger. I was under the impression

Re: [PATCH V5 1/4] spi: tegra114: add support for gpio based CS

2019-05-15 Thread Sowjanya Komatineni
> > Tegra SPI doesn’t support inter byte delay directly to meet some SPI slave > > requirements. > > So we use GPIO control CS in parallel with a dummy HW CS and use inactive > > cycles delay of SPI controller to mimic inter byte delay. > Please fix your mail client to word wrap within

[PATCH 4.19 071/113] netfilter: nf_tables: add missing ->release_ops() in error path of newrule()

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit b25a31bf0ca091aa8bdb9ab329b0226257568bbe ] ->release_ops() callback releases resources and this is used in error path. If nf_tables_newrule() fails after ->select_ops(), it should release resources. but it can not call ->destroy() because that should be called after ->init(). At

[PATCH 4.19 074/113] mlxsw: core: Do not use WQ_MEM_RECLAIM for EMAD workqueue

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit a8c133b06183c529c51cd0d54eb57d6b7078370c ] The EMAD workqueue is used to handle retransmission of EMAD packets that contain configuration data for the device's firmware. Given the workers need to allocate these packets and that the code is not called as part of memory reclaim

[PATCH 4.19 077/113] net/tls: fix the IV leaks

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 5a03bc73abed6ae196c15e9950afde19d48be12c ] Commit f66de3ee2c16 ("net/tls: Split conf to rx + tx") made freeing of IV and record sequence number conditional to SW path only, but commit e8f69799810c ("net/tls: Add generic NIC offload infrastructure") also allocates that state for

[PATCH 4.19 075/113] mlxsw: core: Do not use WQ_MEM_RECLAIM for mlxsw ordered workqueue

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 4af0699782e2cc7d0d89db9eb6f8844dd3df82dc ] The ordered workqueue is used to offload various objects such as routes and neighbours in the order they are notified. It should not be called as part of memory reclaim path, so remove the WQ_MEM_RECLAIM flag. This can also result in a

[PATCH 4.19 068/113] mm/memory.c: fix modifying of page protection by insert_pfn()

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit cae85cb8add35f678cf487139d05e083ce2f570a ] Aneesh has reported that PPC triggers the following warning when excercising DAX code: IP set_pte_at+0x3c/0x190 LR insert_pfn+0x208/0x280 Call Trace: insert_pfn+0x68/0x280 dax_iomap_pte_fault.isra.7+0x734/0xa40

[PATCH 4.19 042/113] ocelot: Dont sleep in atomic context (irqs_disabled())

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit a8fd48b50deaa20808bbf0f6685f6f1acba6a64c ] Preemption disabled at: [] dev_set_rx_mode+0x1c/0x38 Call trace: [] dump_backtrace+0x0/0x3d0 [] show_stack+0x14/0x20 [] dump_stack+0xac/0xe4 [] ___might_sleep+0x164/0x238 [] __might_sleep+0x50/0x88 []

[PATCH 4.19 067/113] net: dsa: mv88e6xxx: fix few issues in mv88e6390x_port_set_cmode

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 5ceaeb99ffb4dc002d20f6ac243c19a85e2c7a76 ] This patches fixes few issues in mv88e6390x_port_set_cmode(). 1. When entering the function the old cmode may be 0, in this case mv88e6390x_serdes_get_lane() returns -ENODEV. As result we bail out and have no chance to set a new

[PATCH 4.19 072/113] net: fec: manage ahb clock in runtime pm

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit d7c3a206e6338e4ccdf030719dec028e26a521d5 ] Some SOC like i.MX6SX clock have some limits: - ahb clock should be disabled before ipg. - ahb and ipg clocks are required for MAC MII bus. So, move the ahb clock to runtime management together with ipg clock. Signed-off-by: Fugang

[PATCH 4.19 061/113] drm/sun4i: Unbind components before releasing DRM and memory

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit e02bc29b2cfa7806830d6da8b2322cddd67e8dfe ] Our components may still be using the DRM device driver (if only to access our driver's private data), so make sure to unbind them before the final drm_dev_put. Also release our reserved memory after component unbind instead of before

[PATCH 4.19 065/113] powerpc/smp: Fix NMI IPI timeout

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 1b5fc84aba170bdfe3533396ca9662ceea1609b7 ] The NMI IPI timeout logic is broken, if __smp_send_nmi_ipi() times out on the first condition, delay_us will be zero which will send it into the second spin loop with no timeout so it will spin forever. Fixes: 5b73151fff63 ("powerpc:

[PATCH 4.19 066/113] powerpc/smp: Fix NMI IPI xmon timeout

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 88b9a3d1425a436e95c41f09986fdae2daee437a ] The xmon debugger IPI handler waits in the callback function while xmon is still active. This means they don't complete the IPI, and the initiator always times out waiting for them. Things manage to work after the timeout because there

[PATCH 4.19 041/113] ipmi: ipmi_si_hardcode.c: init si_type array to fix a crash

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit a885bcfd152f97b25005298ab2d6b741aed9b49c ] The intended behavior of function ipmi_hardcode_init_one() is to default to kcs interface when no type argument is presented when initializing ipmi with hard coded addresses. However, the array of char pointers allocated on the stack

[PATCH 4.19 059/113] spi: Micrel eth switch: declare missing of table

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 2f23a2a768bee7ad2ff1e9527c3f7e279e794a46 ] Add missing table for SPI driver relying on SPI device match since compatible is in a DT binding or in a DTS. Before this patch: modinfo drivers/net/phy/spi_ks8995.ko | grep alias alias: spi:ksz8795 alias:

[PATCH 4.19 060/113] spi: ST ST95HF NFC: declare missing of table

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit d04830531d0c4a99c897a44038e5da3d23331d2f ] Add missing table for SPI driver relying on SPI device match since compatible is in a DT binding or in a DTS. Before this patch: modinfo drivers/nfc/st95hf/st95hf.ko | grep alias alias: spi:st95hf After this patch: modinfo

[PATCH 4.19 062/113] Input: synaptics-rmi4 - fix possible double free

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit bce1a78423961fce676ac65540a31b6ffd179e6d ] The RMI4 function structure has been released in rmi_register_function if error occurs. However, it will be released again in the function rmi_create_function, which may result in a double-free bug. Signed-off-by: Pan Bian

[PATCH 4.19 064/113] mm/memory_hotplug.c: drop memory device reference after find_memory_block()

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 89c02e69fc5245f8a2f34b58b42d43a737af1a5e ] Right now we are using find_memory_block() to get the node id for the pfn range to online. We are missing to drop a reference to the memory block device. While the device still gets unregistered via device_unregister(), resulting in

[PATCH 4.19 058/113] ARM: 8856/1: NOMMU: Fix CCR register faulty initialization when MPU is disabled

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit c3143967807adb1357c36b68a7563fc0c4e1f615 ] When CONFIG_ARM_MPU is not defined, the base address of v7M SCB register is not initialized with correct value. This prevents enabling I/D caches when the L1 cache poilcy is applied in kernel. Fixes:

[PATCH 4.19 055/113] netfilter: fix nf_l4proto_log_invalid to log invalid packets

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit d48668052b2603b6262459625c86108c493588dd ] It doesn't log a packet if sysctl_log_invalid isn't equal to protonum OR sysctl_log_invalid isn't equal to IPPROTO_RAW. This sentence is always true. I believe we need to replace OR to AND. Cc: Florian Westphal Fixes: c4f3db1595827

[PATCH 4.19 004/113] platform/x86: dell-laptop: fix rfkill functionality

2019-05-15 Thread Greg Kroah-Hartman
From: Mario Limonciello commit 6cc13c28da5beee0f706db6450e190709700b34a upstream. When converting the driver two arguments were transposed leading to rfkill not working. BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=201427 Reported-by: Pepijn de Vos Fixes: 549b49 ("platform/x86:

[PATCH 4.19 036/113] x86/build/lto: Fix truncated .bss with -fdata-sections

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 6a03469a1edc94da52b65478f1e00837add869a3 ] With CONFIG_LD_DEAD_CODE_DATA_ELIMINATION=y, we compile the kernel with -fdata-sections, which also splits the .bss section. The new section, with a new .bss.* name, which pattern gets missed by the main x86 linker script which only

[PATCH 4.19 038/113] KVM: fix spectrev1 gadgets

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c ] These were found with smatch, and then generalized when applicable. Signed-off-by: Paolo Bonzini Signed-off-by: Sasha Levin --- arch/x86/kvm/lapic.c | 4 +++- include/linux/kvm_host.h | 10 ++ virt/kvm/irqchip.c |

[PATCH 4.19 033/113] afs: Unlock pages for __pagevec_release()

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 21bd68f196ca91fc0f3d9bd1b32f6e530e8c1c88 ] __pagevec_release() complains loudly if any page in the vector is still locked. The pages need to be locked for generic_error_remove_page(), but that function doesn't actually unlock them. Unlock the pages afterwards. Signed-off-by:

[PATCH 4.19 007/113] virt: vbox: Sanity-check parameter types for hgcm-calls coming from userspace

2019-05-15 Thread Greg Kroah-Hartman
From: Hans de Goede commit cf4f2ad6b87dda2dbe0573b1ebeb0273f8d4aac6 upstream. Userspace can make host function calls, called hgcm-calls through the /dev/vboxguest device. In this case we should not accept all hgcm-function-parameter-types, some are only valid for in kernel calls. This commit

[PATCH 4.19 029/113] selftests: fib_tests: Fix Command line is not complete errors

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit a5f622984a623df9a84cf43f6b098d8dd76fbe05 ] A couple of tests are verifying a route has been removed. The helper expects the prefix as the first part of the expected output. When checking that a route has been deleted the prefix is empty leading to an invalid ip command: $ ip

[PATCH 4.19 050/113] MIPS: perf: ath79: Fix perfcount IRQ assignment

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit a1e8783db8e0d58891681bc1e6d9ada66eae8e20 ] Currently it's not possible to use perf on ath79 due to genirq flags mismatch happening on static virtual IRQ 13 which is used for performance counters hardware IRQ 5. On TP-Link Archer C7v5: CPU0 2: 0 MIPS

[PATCH 4.19 000/113] 4.19.44-stable review

2019-05-15 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.44 release. There are 113 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 17 May 2019 09:04:35 AM UTC. Anything

[PATCH 4.19 006/113] kernfs: fix barrier usage in __kernfs_new_node()

2019-05-15 Thread Greg Kroah-Hartman
From: Andrea Parri commit 998267900cee901c5d1dfa029a6304d00acbc29f upstream. smp_mb__before_atomic() can not be applied to atomic_set(). Remove the barrier and rely on RELEASE synchronization. Fixes: ba16b2846a8c6 ("kernfs: add an API to get kernfs node from inode number") Cc:

[PATCH 4.19 052/113] drm/sun4i: Set device driver data at bind time for use in unbind

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 02b92adbe33e6dbd15dc6e32540b22f47c4ff0a2 ] Our sun4i_drv_unbind gets the drm device using dev_get_drvdata. However, that driver data is never set in sun4i_drv_bind. Set it there to avoid getting a NULL pointer at unbind time. Fixes: 9026e0d122ac ("drm: Add Allwinner A10

[PATCH 4.19 008/113] USB: serial: fix unthrottle races

2019-05-15 Thread Greg Kroah-Hartman
From: Johan Hovold commit 3f5edd58d040bfa4b74fb89bc02f0bc6b9cd06ab upstream. Fix two long-standing bugs which could potentially lead to memory corruption or leave the port throttled until it is reopened (on weakly ordered systems), respectively, when read-URB completion races with unthrottle().

[PATCH 4.19 009/113] iio: adc: xilinx: fix potential use-after-free on remove

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 62039b6aef63380ba7a37c113bbaeee8a55c5342 ] When cancel_delayed_work() returns, the delayed work may still be running. This means that the core could potentially free the private structure (struct xadc) while the delayed work is still using it. This is a potential use-after-free.

[PATCH 4.19 034/113] drm/amd/display: If one stream full updates, full update all planes

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit c238bfe0be9ef7420f7669a69e27c8c8f4d8a568 ] [Why] On some compositors, with two monitors attached, VT terminal switch can cause a graphical issue by the following means: There are two streams, one for each monitor. Each stream has one plane current state: M1:S1->P1

[PATCH 4.19 026/113] drm/amd/display: extending AUX SW Timeout

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit f4bbebf8e7eb4d294b040ab2d2ba71e70e69b930 ] [Why] AUX takes longer to reply when using active DP-DVI dongle on some asics resulting in up to 2000+ us edid read (timeout). [How] 1. Adjust AUX poll to match spec 2. Extend the SW timeout. This does not affect normal operation since

[PATCH 4.19 032/113] qede: fix write to freed pointer error and double free of ptp

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 1dc2b3d65523780ed1972d446c76e62e13f3e8f5 ] The err2 error return path calls qede_ptp_disable that cleans up on an error and frees ptp. After this, the free'd ptp is dereferenced when ptp->clock is set to NULL and the code falls-through to error path err1 that frees ptp again.

[PATCH 4.19 030/113] mISDN: Check address length before reading address family

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 238ffdc49ef98b15819cfd5e3fb23194e3ea3d39 ] KMSAN will complain if valid address length passed to bind() is shorter than sizeof("struct sockaddr_mISDN"->family) bytes. Signed-off-by: Tetsuo Handa Signed-off-by: David S. Miller Signed-off-by: Sasha Levin ---

[PATCH 4.19 016/113] HID: input: add mapping for "Toggle Display" key

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit c01908a14bf735b871170092807c618bb9dae654 ] According to HUT 1.12 usage 0xb5 from the generic desktop page is reserved for switching between external and internal display, so let's add the mapping. Signed-off-by: Dmitry Torokhov Signed-off-by: Sasha Levin ---

[PATCH 4.19 021/113] cfg80211: Handle WMM rules in regulatory domain intersection

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 08a75a887ee46828b54600f4bb7068d872a5edd5 ] The support added for regulatory WMM rules did not handle the case of regulatory domain intersections. Fix it. Signed-off-by: Ilan Peer Fixes: 230ebaa189af ("cfg80211: read wmm rules from regulatory database") Signed-off-by: Luca

[PATCH 4.19 025/113] s390/3270: fix lockdep false positive on view->lock

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 5712f3301a12c0c3de9cc423484496b0464f2faf ] The spinlock in the raw3270_view structure is used by con3270, tty3270 and fs3270 in different ways. For con3270 the lock can be acquired in irq context, for tty3270 and fs3270 the highest context is bh. Lockdep sees the view->lock as

[PATCH 4.19 023/113] nl80211: Add NL80211_FLAG_CLEAR_SKB flag for other NL commands

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit d6db02a88a4aaa1cd7105137c67ddec7f3bdbc05 ] This commit adds NL80211_FLAG_CLEAR_SKB flag to other NL commands that carry key data to ensure they do not stick around on heap after the SKB is freed. Also introduced this flag for NL80211_CMD_VENDOR as there are sub commands which

[PATCH 4.19 015/113] HID: input: add mapping for keyboard Brightness Up/Down/Toggle keys

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 7975a1d6a7afeb3eb61c971a153d24dd8fa032f3 ] According to HUTRR73 usages 0x79, 0x7a and 0x7c from the consumer page correspond to Brightness Up/Down/Toggle keys, so let's add the mappings. Signed-off-by: Dmitry Torokhov Signed-off-by: Sasha Levin --- drivers/hid/hid-input.c |

[PATCH 4.14 109/115] vlan: disable SIOCSHWTSTAMP in container

2019-05-15 Thread Greg Kroah-Hartman
From: Hangbin Liu [ Upstream commit 873017af778439f2f8e3d87f28ddb1fcaf244a76 ] With NET_ADMIN enabled in container, a normal user could be mapped to root and is able to change the real device's rx filter via ioctl on vlan, which would affect the other ptp process on host. Fix it by disabling

[PATCH 4.19 019/113] mac80211: fix unaligned access in mesh table hash function

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 40586e3fc400c00c11151804dcdc93f8c831c808 ] The pointer to the last four bytes of the address is not guaranteed to be aligned, so we need to use __get_unaligned_cpu32 here Signed-off-by: Felix Fietkau Signed-off-by: Johannes Berg Signed-off-by: Sasha Levin ---

[PATCH 4.19 017/113] libnvdimm/btt: Fix a kmemdup failure check

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 486fa92df4707b5df58d6508728bdb9321a59766 ] In case kmemdup fails, the fix releases resources and returns to avoid the NULL pointer dereference. Signed-off-by: Aditya Pakki Signed-off-by: Dan Williams Signed-off-by: Sasha Levin --- drivers/nvdimm/btt_devs.c | 18

[PATCH 4.19 018/113] s390/dasd: Fix capacity calculation for large volumes

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 2cc9637ce825f3a9f51f8f78af7474e9e85bfa5f ] The DASD driver incorrectly limits the maximum number of blocks of ECKD DASD volumes to 32 bit numbers. Volumes with a capacity greater than 2^32-1 blocks are incorrectly recognized as smaller volumes. This results in the following

[PATCH 4.19 002/113] platform/x86: sony-laptop: Fix unintentional fall-through

2019-05-15 Thread Greg Kroah-Hartman
From: Gustavo A. R. Silva commit 1cbd7a64959d33e7a2a1fa2bf36a62b350a9fcbd upstream. It seems that the default case should return AE_CTRL_TERMINATE, instead of falling through to case ACPI_RESOURCE_TYPE_END_TAG and returning AE_OK; otherwise the line of code at the end of the function is

[PATCH 4.14 107/115] net: ucc_geth - fix Oops when changing number of buffers in the ring

2019-05-15 Thread Greg Kroah-Hartman
From: Christophe Leroy [ Upstream commit ee0df19305d9fabd9479b785918966f6e25b733b ] When changing the number of buffers in the RX ring while the interface is running, the following Oops is encountered due to the new number of buffers being taken into account immediately while their allocation

[PATCH 4.19 011/113] iio: adc: xilinx: prevent touching unclocked h/w on remove

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 2e4b88f73966adead360e47621df0183586fac32 ] In remove, the clock is disabled before canceling the delayed work. This means that the delayed work may be touching unclocked hardware. Fix by disabling the clock after the delayed work is fully canceled. This is consistent with the

[PATCH 4.14 104/115] net: dsa: Fix error cleanup path in dsa_init_module

2019-05-15 Thread Greg Kroah-Hartman
From: YueHaibing [ Upstream commit 68be930249d051fd54d3d99156b3dcadcb2a1f9b ] BUG: unable to handle kernel paging request at a01c5430 PGD 3270067 P4D 3270067 PUD 3271063 PMD 230bc5067 PTE 0 Oops: [#1 CPU: 0 PID: 6159 Comm: modprobe Not tainted 5.1.0+ #33 Hardware name: QEMU

[PATCH 4.14 102/115] fib_rules: return 0 directly if an exactly same rule exists when NLM_F_EXCL not supplied

2019-05-15 Thread Greg Kroah-Hartman
From: Hangbin Liu [ Upstream commit e9919a24d3022f72bcadc407e73a6ef17093a849 ] With commit 153380ec4b9 ("fib_rules: Added NLM_F_EXCL support to fib_nl_newrule") we now able to check if a rule already exists. But this only works with iproute2. For other tools like libnl, NetworkManager, it still

[PATCH 4.19 001/113] bfq: update internal depth state when queue depth changes

2019-05-15 Thread Greg Kroah-Hartman
commit 77f1e0a52d26242b6c2dba019f6ebebfb9ff701e upstream A previous commit moved the shallow depth and BFQ depth map calculations to be done at init time, moving it outside of the hotter IO path. This potentially causes hangs if the users changes the depth of the scheduler map, by writing to the

[PATCH 4.19 013/113] libnvdimm/namespace: Fix a potential NULL pointer dereference

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 55c1fc0af29a6c1b92f217b7eb7581a882e0c07c ] In case kmemdup fails, the fix goes to blk_err to avoid NULL pointer dereference. Signed-off-by: Kangjie Lu Signed-off-by: Dan Williams Signed-off-by: Sasha Levin --- drivers/nvdimm/namespace_devs.c | 5 - 1 file changed, 4

[PATCH 4.14 058/115] tracing/fgraph: Fix set_graph_function from showing interrupts

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 5cf99a0f3161bc3ae2391269d134d6bf7e26f00e ] The tracefs file set_graph_function is used to only function graph functions that are listed in that file (or all functions if the file is empty). The way this is implemented is that the function graph tracer looks at every function,

[PATCH 4.14 060/115] scsi: raid_attrs: fix unused variable warning

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 0eeec01488da9b1403c8c29e73eacac8af9e4bf2 ] I ran into a new warning on randconfig kernels: drivers/scsi/raid_class.c: In function 'raid_match': drivers/scsi/raid_class.c:64:24: error: unused variable 'i' [-Werror=unused-variable] This looks like a very old problem that for

[PATCH 4.14 057/115] net: dont keep lonely packets forever in the gro hash

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 605108acfe6233b72e2f803aa1cb59a2af3001ca ] Eric noted that with UDP GRO and NAPI timeout, we could keep a single UDP packet inside the GRO hash forever, if the related NAPI instance calls napi_gro_complete() at an higher frequency than the NAPI timeout. Willem noted that even

[PATCH 4.14 061/115] staging: olpc_dcon: add a missing dependency

2019-05-15 Thread Greg Kroah-Hartman
[ Upstream commit 33f49571d75024b1044cd02689ad2bdb4924cc80 ] WARNING: unmet direct dependencies detected for BACKLIGHT_CLASS_DEVICE Depends on [n]: HAS_IOMEM [=y] && BACKLIGHT_LCD_SUPPORT [=n] Selected by [y]: - FB_OLPC_DCON [=y] && STAGING [=y] && X86 [=y] && OLPC [=y] && FB [=y]

[PATCH 4.14 115/115] powerpc/booke64: set RI in default MSR

2019-05-15 Thread Greg Kroah-Hartman
From: Laurentiu Tudor commit 5266e58d6cd90ac85c187d673093ad9cb649e16d upstream. Set RI in the default kernel's MSR so that the architected way of detecting unrecoverable machine check interrupts has a chance to work. This is inline with the MSR setup of the rest of booke powerpc architectures

<    6   7   8   9   10   11   12   13   14   15   >