[PATCH 4.14 028/183] NFS: Dont use page_file_mapping after removing the page

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d2ceb7e57086750ea6198a31fd942d98099a0786 ] If nfs_page_async_flush() removes the page from the mapping, then we can't use page_file_mapping() on it as nfs_updatepate() is wont to do

[PATCH 4.14 016/183] Input: pwm-vibra - stop regulator after disabling pwm, not before

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 94803aef3533676194c772383472636c453e3147 ] This patch fixes order of disable calls in pwm_vibrator_stop. Currently when starting device, we first enable vcc regulator and then setup

[PATCH 4.14 013/183] gpu: ipu-v3: Fix CSI offsets for imx53

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bb867d219fda7fbaabea3314702474c4eac2b91d ] The CSI offsets are wrong for both CSI0 and CSI1. They are at physical address 0x1e03 and 0x1e038000 respectively. Fixes: 2ffd48f2e7 (

[PATCH 4.14 034/183] i2c: bcm2835: Clear current buffer pointers and counts after a transfer

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f275a4659484716259cc46268d9043424e51cf0f ] The driver's interrupt handler checks whether a message is currently being handled with the curr_msg pointer. When it is NULL, the interrup

[PATCH 4.14 017/183] ARM: OMAP2+: Variable "reg" in function omap4_dsi_mux_pads() could be uninitialized

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dc30e70391376ba3987aeb856ae6d9c0706534f1 ] In function omap4_dsi_mux_pads(), local variable "reg" could be uninitialized if function regmap_read() returns -EINVAL. However, it will b

[PATCH 4.14 050/183] ASoC: topology: free created components in tplg load error

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 304017d31df36fb61eb2ed3ebf65fb6870b3c731 ] Topology resources are no longer needed if any element failed to load. Signed-off-by: Bard liao Signed-off-by: Mark Brown Signed-off-by:

[PATCH 4.14 022/183] Input: cap11xx - switch to using set_brightness_blocking()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 628442880af8c201d307a45f3862a7a17df8a189 ] Updating LED state requires access to regmap and therefore we may sleep, so we could not do that directly form set_brightness() method. His

[PATCH 4.14 021/183] ARM: OMAP2+: fix lack of timer interrupts on CPU1 after hotplug

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 50d6b3cf9403879911e06d69c7ef41e43f8f7b4b ] If we have a kernel configured for periodic timer interrupts, and we have cpuidle enabled, then we end up with CPU1 losing timer interupts

[PATCH 4.14 043/183] keys: Fix dependency loop between construction record and auth key

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 822ad64d7e46a8e2c8b8a796738d7b657cbb146d ] In the request_key() upcall mechanism there's a dependency loop by which if a key type driver overrides the ->request_key hook and the user

[PATCH 4.14 045/183] net: systemport: Fix reception of BPDUs

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a40061ea2e39494104602b3048751341bda374a1 ] SYSTEMPORT has its RXCHK parser block that attempts to validate the packet structures, unfortunately setting the L2 header check bit will c

[PATCH 4.14 019/183] ASoC: rsnd: fixup rsnd_ssi_master_clk_start() user count check

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d9111d36024de07784f2e1ba2ccf70b16035f378 ] commit 4d230d1271064 ("ASoC: rsnd: fixup not to call clk_get/set under non-atomic") added new rsnd_ssi_prepare() and moved rsnd_ssi_master_

[PATCH 4.14 018/183] ASoC: dapm: fix out-of-bounds accesses to DAPM lookup tables

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c16e12010060c6c7a31f08b4a99513064cb53b7d ] KASAN reports and additional traces point to out-of-bounds accesses to the dapm_up_seq and dapm_down_seq lookup tables. The indices used ar

[PATCH 4.14 051/183] qed: Fix iWARP syn packet mac address validation.

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8be3dadf04050c2907760ec1955ca1c8fbc25585 ] The ll2 forwards all syn packets to the driver without validating the mac address. Add validation check in the driver's iWARP listener flow

[PATCH 4.14 038/183] clk: sunxi: A31: Fix wrong AHB gate number

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ee0b27a3a4da0b0ed2318aa092f8856896e9450b ] According to the manual the gate clock for MMC3 is at bit 11, and NAND1 is controlled by bit 12. Fix the gate bit definitions in the clock

[PATCH 4.14 039/183] esp: Skip TX bytes accounting when sending from a request socket

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 09db51241118aeb06e1c8cd393b45879ce099b36 ] On ESP output, sk_wmem_alloc is incremented for the added padding if a socket is associated to the skb. When replying with TCP SYNACKs over

[PATCH 4.14 046/183] pinctrl: meson: meson8b: fix the sdxc_a data 1..3 pins

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c17abcfa93bf0be5e48bb011607d237ac2bfc839 ] Fix the mismatch between the "sdxc_d13_1_a" pin group definition from meson8b_cbus_groups and the entry in sdxc_a_groups ("sdxc_d0_13_1_a")

[PATCH 4.14 047/183] qmi_wwan: apply SET_DTR quirk to Sierra WP7607

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 97dc47a1308a3af46a09b1546cfb869f2e382a81 ] The 1199:68C0 USB ID is reused by Sierra WP7607 which requires the DTR quirk to be detected. Apply QMI_QUIRK_SET_DTR unconditionally as alr

[PATCH 4.14 049/183] mailbox: bcm-flexrm-mailbox: Fix FlexRM ring flush timeout issue

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d7bf31a0f85faaf63c63c39d55154825a1eaaea9 ] RING_CONTROL reg was not written due to wrong address, hence all the subsequent ring flush was timing out. Fixes: a371c10ea4b3 ("mailbox:

[PATCH 4.14 040/183] ARM: 8824/1: fix a migrating irq bug when hotplug cpu

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1b5ba350784242eb1f899bcffd95d2c7cff61e84 ] Arm TC2 fails cpu hotplug stress test. This issue was tracked down to a missing copy of the new affinity cpumask for the vexpress-spc inte

[PATCH 4.14 035/183] auxdisplay: ht16k33: fix potential user-after-free on module unload

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 69ef9bc54715fb1cb7786ada15774e469e822209 ] On module unload/remove, we need to ensure that work does not run after we have freed resources. Concretely, cancel_delayed_work() may retu

[PATCH 4.14 065/183] tmpfs: fix uninitialized return value in shmem_link

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 29b00e609960ae0fcff382f4c7079dd0874a5311 ] When we made the shmem_reserve_inode call in shmem_link conditional, we forgot to update the declaration for ret so that it always has a kn

[PATCH 4.14 036/183] Input: st-keyscan - fix potential zalloc NULL dereference

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2439d37e1bf8a34d437573c086572abe0f3f1b15 ] This patch fixes the following static checker warning: drivers/input/keyboard/st-keyscan.c:156 keyscan_probe() error: potential zalloc NUL

[PATCH 4.14 042/183] assoc_array: Fix shortcut creation

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bb2ba2d75a2d673e76ddaf13a9bd30d6a8b1bb08 ] Fix the creation of shortcuts for which the length of the index key value is an exact multiple of the machine word size. The problem is th

[PATCH 4.14 054/183] tmpfs: fix link accounting when a tmpfile is linked in

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1062af920c07f5b54cf5060fde3339da6df0cf6b ] tmpfs has a peculiarity of accounting hard links as if they were separate inodes: so that when the number of inodes is limited, as it is by

[PATCH 4.14 064/183] net: set static variable an initial value in atl2_probe()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4593403fa516a5a4cffe6883c5062d60932cbfbe ] cards_found is a static variable, but when it enters atl2_probe(), cards_found is set to zero, the value is not consistent with last probe,

[PATCH 4.14 033/183] i2c: cadence: Fix the hold bit setting

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d358def706880defa4c9e87381c5bf086a97d5f9 ] In case the hold bit is not needed we are carrying the old values. Fix the same by resetting the bit when not needed. Fixes the sporadic i

[PATCH 4.14 063/183] nfp: bpf: fix ALU32 high bits clearance bug

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f036ebd9bfbe1e91a3d855e85e05fc5ff156b641 ] NFP BPF JIT compiler is doing a couple of small optimizations when jitting ALU imm instructions, some of these optimizations could save cod

[PATCH 4.14 066/183] media: videobuf2-v4l2: drop WARN_ON in vb2_warn_zero_bytesused()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 5e99456c20f712dcc13d9f6ca4278937d5367355 upstream. Userspace shouldn't set bytesused to 0 for output buffers. vb2_warn_zero_bytesused() warns about this (only once!), but i

[PATCH 4.14 057/183] ARC: uacces: remove lp_start, lp_end from clobber list

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d5e3c55e01d8b1774b37b4647c30fb22f1d39077 ] Newer ARC gcc handles lp_start, lp_end in a different way and doesn't like them in the clobber list. Signed-off-by: Vineet Gupta Signed-o

[PATCH 4.14 056/183] ARCv2: lib: memcpy: fix doing prefetchw outside of buffer

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f8a15f97664178f27dfbf86a38f780a532cb6df0 ] ARCv2 optimized memcpy uses PREFETCHW instruction for prefetching the next cache line but doesn't ensure that the line is not past the end

[PATCH 4.14 061/183] net: thunderx: make CFG_DONE message to run through generic send-ack sequence

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0dd563b9a62c4cbabf5d4fd6596440c2491e72b1 ] At the end of NIC VF initialization VF sends CFG_DONE message to PF without using nicvf_msg_send_to_pf routine. This potentially could re-w

[PATCH 4.14 087/183] spi: pxa2xx: Setup maximum supported DMA transfer length

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit ef070b4e4aa25bb5f8632ad196644026c11903bf upstream. When the commit b6ced294fb61 ("spi: pxa2xx: Switch to SPI core DMA mapping functionality") switches to SPI core p

[PATCH 4.14 074/183] crypto: arm64/crct10dif - revert to C code for short inputs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit d72b9d4acd548251f55b16843fc7a05dc5c80de8 upstream. The SIMD routine ported from x86 used to have a special code path for inputs < 16 bytes, which got lost somewhere along

[PATCH 4.14 069/183] libnvdimm, pfn: Fix over-trim in trim_pfn_device()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yang commit f101ada7da6551127d192c2f1742c1e9e0f62799 upstream. When trying to see whether current nd_region intersects with others, trim_pfn_device() has already calculated the *size* to b

[PATCH 4.14 084/183] ACPI / device_sysfs: Avoid OF modalias creation for removed device

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit f16eb8a4b096514ac06fb25bf599dcc792899b3d upstream. If SSDT overlay is loaded via ConfigFS and then unloaded the device, we would like to have OF modalias for, already go

[PATCH 4.14 083/183] xen: fix dom0 boot on huge systems

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Juergen Gross commit 01bd2ac2f55a1916d81dace12fa8d7ae1c79b5ea upstream. Commit f7c90c2aa40048 ("x86/xen: don't write ptes directly in 32-bit PV guests") introduced a regression for booting dom

[PATCH 4.14 060/183] mac80211_hwsim: propagate genlmsg_reply return code

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 17407715240456448e4989bee46ffc93991add83 ] genlmsg_reply can fail, so propagate its return code Signed-off-by: Li RongQing Signed-off-by: Johannes Berg Signed-off-by: Sasha Levin

[PATCH 4.14 071/183] libnvdimm: Fix altmap reservation size calculation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Oliver O'Halloran commit 07464e88365e9236febaca9ed1a2e2006d8bc952 upstream. Libnvdimm reserves the first 8K of pfn and devicedax namespaces to store a superblock describing the namespace. This

[PATCH 4.14 088/183] regulator: s2mps11: Fix steps for buck7, buck8 and LDO35

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 56b5d4ea778c1b0989c5cdb5406d4a488144c416 upstream. LDO35 uses 25 mV step, not 50 mV. Bucks 7 and 8 use 12.5 mV step instead of 6.25 mV. Wrong step caused over-volt

[PATCH 4.14 072/183] fix cgroup_do_mount() handling of failure exits

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 399504e21a10be16dd1408ba0147367d9d82a10c upstream. same story as with last May fixes in sysfs (7b745a4e4051 "unfuck sysfs_mount()"); new_sb is left uninitialized in case of earl

[PATCH 4.14 091/183] clocksource/drivers/exynos_mct: Move one-shot check from tick clear to ISR

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stuart Menefy commit a5719a40aef956ba704f2aa1c7b977224d60fa96 upstream. When a timer tick occurs and the clock is in one-shot mode, the timer needs to be stopped to prevent it triggering subse

[PATCH 4.14 093/183] s390/setup: fix early warning messages

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky commit 8727638426b0aea59d7f904ad8ddf483f9234f88 upstream. The setup_lowcore() function creates a new prefix page for the boot CPU. The PSW mask for the system_call, external

[PATCH 4.14 075/183] crypto: hash - set CRYPTO_TFM_NEED_KEY if ->setkey() fails

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit ba7d7433a0e998c902132bd47330e355a1eaa894 upstream. Some algorithms have a ->setkey() method that is not atomic, in the sense that setting a key can fail after changes were

[PATCH 4.14 089/183] regulator: max77620: Initialize values for DT properties

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mark Zhang commit 0ab66b3c326ef8f77dae9f528118966365757c0c upstream. If regulator DT node doesn't exist, its of_parse_cb callback function isn't called. Then all values for DT properties are f

[PATCH 4.14 081/183] tracing: Use strncpy instead of memcpy for string keys in hist triggers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tom Zanussi commit 9f0bbf3115ca9f91f43b7c74e9ac7d79f47fc6c2 upstream. Because there may be random garbage beyond a string's null terminator, it's not correct to copy the the complete character

[PATCH 4.14 079/183] CIFS: Do not reset lease state to NONE on lease break

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Shilovsky commit 7b9b9edb49ad377b1e06abf14354c227e9ac4b06 upstream. Currently on lease break the client sets a caching level twice: when oplock is detected and when oplock is processed.

[PATCH 4.14 078/183] crypto: arm64/aes-ccm - fix bugs in non-NEON fallback routine

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 969e2f59d589c15f6aaf306e590dde16f12ea4b3 upstream. Commit 5092fcf34908 ("crypto: arm64/aes-ce-ccm: add non-SIMD generic fallback") introduced C fallback code to replace t

[PATCH 4.14 077/183] crypto: arm64/aes-ccm - fix logical bug in AAD MAC handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit eaf46edf6ea89675bd36245369c8de5063a0272c upstream. The NEON MAC calculation routine fails to handle the case correctly where there is some data in the buffer, and the inp

[PATCH 4.14 073/183] crypto: arm/crct10dif - revert to C code for short inputs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 62fecf295e3c48be1b5f17c440b93875b9adb4d6 upstream. The SIMD routine ported from x86 used to have a special code path for inputs < 16 bytes, which got lost somewhere along

[PATCH 4.14 082/183] tracing: Do not free iter->trace in fail path of tracing_open_pipe()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: zhangyi (F) commit e7f0c424d0806b05d6f47be9f202b037eb701707 upstream. Commit d716ff71dd12 ("tracing: Remove taking of trace_types_lock in pipe files") use the current tracer instead of the cop

[PATCH 4.14 107/183] irqchip/gic-v3-its: Avoid parsing _indirect_ twice for Device table

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Zenghui Yu commit 8d565748b6035eeda18895c213396a4c9fac6a4c upstream. In current logic, its_parse_indirect_baser() will be invoked twice when allocating Device tables. Add a *break* to omit the

[PATCH 4.14 105/183] crypto: pcbc - remove bogus memcpy()s with src == dest

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 251b7aea34ba3c4d4fdfa9447695642eb8b8b098 upstream. The memcpy()s in the PCBC implementation use walk->iv as both the source and destination, which has undefined behavior.

[PATCH 4.14 095/183] scsi: virtio_scsi: dont send sc payload with tmfs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Felipe Franciosi commit 3722e6a52174d7c3a00e6f5efd006ca093f346c1 upstream. The virtio scsi spec defines struct virtio_scsi_ctrl_tmf as a set of device-readable records and a single device-writ

[PATCH 4.14 101/183] m68k: Add -ffreestanding to CFLAGS

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 28713169d879b67be2ef2f84dcf54905de238294 upstream. This patch fixes a build failure when using GCC 8.1: /usr/bin/ld: block/partitions/ldm.o: in function `ldm_parse_tocblock'

[PATCH 4.14 100/183] splice: dont merge into linked buffers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit a0ce2f0aa6ad97c3d4927bf2ca54bcebdf062d55 upstream. Before this patch, it was possible for two pipes to affect each other after data had been transferred between them with tee(

[PATCH 4.14 123/183] mm/vmalloc: fix size check for remap_vmalloc_range_partial()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Roman Penyaev commit 401592d2e095947344e10ec0623adbcd58934dd4 upstream. When VM_NO_GUARD is not set area->size includes adjacent guard page, thus for correct size checking get_vm_area_size() s

[PATCH 4.14 103/183] btrfs: ensure that a DUP or RAID1 block group has exactly two stripes

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn commit 349ae63f40638a28c6fce52e8447c2d14b84cc0c upstream. We recently had a customer issue with a corrupted filesystem. When trying to mount this image btrfs panicked with a

[PATCH 4.14 098/183] scsi: target/iscsi: Avoid iscsit_release_commands_from_conn() deadlock

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 32e36bfbcf31452a854263e7c7f32fbefc4b44d8 upstream. When using SCSI passthrough in combination with the iSCSI target driver then cmd->t_state_lock may be obtained from in

[PATCH 4.14 111/183] ext4: add mask of ext4 flags to swap

4.14-stable review patch. If anyone has any objections, please let me know. -- From: yangerkun commit abdc644e8cbac2e9b19763680e5a7cf9bab2bee7 upstream. The reason is that while swapping two inode, we swap the flags too. Some flags such as EXT4_JOURNAL_DATA_FL can really confu

[PATCH 4.14 109/183] cpufreq: tegra124: add missing of_node_put()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yangtao Li commit 446fae2bb5395f3028d8e3aae1508737e5a72ea1 upstream. of_cpu_device_node_get() will increase the refcount of device_node, it is necessary to call of_node_put() at the end to rel

[PATCH 4.14 122/183] mm: hwpoison: fix thp split handing in soft_offline_in_use_page()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: zhongjiang commit 46612b751c4941c5c0472ddf04027e877ae5990f upstream. When soft_offline_in_use_page() runs on a thp tail page after pmd is split, we trigger the following VM_BUG_ON_PAGE(): M

Re: [PATCH] dccp: Fix memleak in __feat_register_sp

On 3/21/2019 7:40 PM, Yue Haibing wrote: From: YueHaibing If dccp_feat_push_change fails, we forget free the mem which is alloced by kmemdup in dccp_feat_clone_sp_val. Reported-by: Hulk Robot Fixes: e8ef967a54f4 ("dccp: Registration routines for changing feature values") Signed-off-by: YueH

[PATCH 4.14 126/183] intel_th: Dont reference unassigned outputs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit 9ed3f3c33347ed963e7c7019cf2956dd4e37 upstream. When an output port driver is removed, also remove references to it from any masters. Failing to do this causes a N

[PATCH 4.14 097/183] scsi: sd: Optimal I/O size should be a multiple of physical block size

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Martin K. Petersen commit a83da8a4509d3ebfe03bb7fffce022e4d5d4764f upstream. It was reported that some devices report an OPTIMAL TRANSFER LENGTH of 0x blocks. That looks bogus, especially

[PATCH 4.14 096/183] scsi: aacraid: Fix performance issue on logical drives

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sagar Biradar commit 0015437cc046e5ec2b57b00ff8312b8d432eac7c upstream. Fix performance issue where the queue depth for SmartIOC logical volumes is set to 1, and allow the usual logical volume

[PATCH 4.14 116/183] clk: uniphier: Fix update register for CPU-gear

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kunihiko Hayashi commit 521282237b9d78b9bff423ec818becd4c95841c2 upstream. Need to set the update bit in UNIPHIER_CLK_CPUGEAR_UPD to update the CPU-gear value. Fixes: d08f1f0d596c ("clk: unip

[PATCH 4.14 115/183] ext2: Fix underflow in ext2_max_size()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 1c2d14212b15a60300a2d4f6364753e87394c521 upstream. When ext2 filesystem is created with 64k block size, ext2_max_size() will return value less than 0. Also, we cannot write any

[PATCH 4.14 125/183] device property: Fix the length used in PROPERTY_ENTRY_STRING()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heikki Krogerus commit 2b6e492467c78183bb629bb0a100ea3509b615a5 upstream. With string type property entries we need to use sizeof(const char *) instead of the number of characters as the lengt

[PATCH 4.14 118/183] clk: ingenic: Fix round_rate misbehaving with non-integer dividers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paul Cercueil commit bc5d922c93491878c44c9216e9d227c7eeb81d7f upstream. Take a parent rate of 180 MHz, and a requested rate of 4.285715 MHz. This results in a theorical divider of 41.93 wh

[PATCH 4.14 132/183] serial: 8250_of: assume reg-shift of 2 for mrvl,mmp-uart

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lubomir Rintel commit f4817843e39ce78aace0195a57d4e8500a65a898 upstream. There are two other drivers that bind to mrvl,mmp-uart and both of them assume register shift of 2 bits. There are devi

[PATCH 4.14 130/183] drm/i915: Relax mmap VMA check

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ca22f32a6296cbfa29de56328c8505560a18cfa8 ] Legacy behaviour was to allow non-page-aligned mmap requests, as does the linux mmap(2) implementation by virtue of automatically rounding

[PATCH 4.14 114/183] cxl: Wrap iterations over afu slices inside afu_list_lock

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vaibhav Jain commit edeb304f659792fb5bab90d7d6f3408b4c7301fb upstream. Within cxl module, iteration over array 'adapter->afu' may be racy at few points as it might be simultaneously read durin

[PATCH 4.14 131/183] serial: uartps: Fix stuck ISR if RX disabled with non-empty FIFO

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Anssi Hannula commit 7abab1605139bc41442864c18f9573440f7ca105 upstream. If RX is disabled while there are still unprocessed bytes in RX FIFO, cdns_uart_handle_rx() called from interrupt handle

[PATCH 4.14 129/183] crypto: arm64/aes-neonbs - fix returning final keystream block

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 12455e320e19e9cc7ad97f4ab89c280fe297387c upstream. The arm64 NEON bit-sliced implementation of AES-CTR fails the improved skcipher tests because it sometimes produces the w

[PATCH 4.14 146/183] powerpc/traps: Fix the message printed when stack overflows

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 9bf3d3c4e4fd82c7174f4856df372ab2a71005b9 upstream. Today's message is useless: [ 42.253267] Kernel stack overflow in process (ptrval), r1=c65500b0 This patch fixe

[PATCH 4.14 147/183] ARM: s3c24xx: Fix boolean expressions in osiris_dvs_notify

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit e2477233145f2156434afb799583bccd878f3e9f upstream. Fix boolean expressions by using logical AND operator '&&' instead of bitwise operator '&'. This issue was detect

[PATCH 4.14 121/183] nfit: acpi_nfit_ctl(): Check out_obj->type in the right place

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dexuan Cui commit 43f89877f26671c6309cd87d7364b1a3e66e71cf upstream. In the case of ND_CMD_CALL, we should also check out_obj->type. The patch uses out_obj->type, which is a short alias to ou

Re: [PATCH] block/mq: blk map queues by core id

On 03/22/2019 06:09 PM, luferry wrote: > under virtual machine environment, cpu topology may differ from normal Would mind share the name of virtual machine monitor, the command line if available, and which device to reproduce. For instance, I am not able to reproduce with qemu nvme or virtio-

[PATCH 4.14 143/183] powerpc/ptrace: Simplify vr_get/set() to avoid GCC warning

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit ca6d5149d2ad0a8d2f9c28cbe379802260a0a5e0 upstream. GCC 8 warns about the logic in vr_get/set(), which with -Werror breaks the build: In function ‘user_regset_copyin’

[PATCH 4.14 120/183] usb: chipidea: tegra: Fix missed ci_hdrc_remove_device()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Osipenko commit 563b9372f7ec57e44e8f9a8600c5107d7ffdd166 upstream. The ChipIdea's platform device need to be unregistered on Tegra's driver module removal. Fixes: dfebb5f43a78827a ("us

[PATCH 4.14 148/183] arm64: Fix HCR.TGE status for NMI contexts

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Julien Thierry commit 5870970b9a828d8693aa6d15742573289d7dbcd0 upstream. When using VHE, the host needs to clear HCR_EL2.TGE bit in order to interact with guest TLBs, switching from EL2&0 tran

[PATCH 4.14 144/183] powerpc/hugetlb: Dont do runtime allocation of 16G pages in LPAR configuration

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Aneesh Kumar K.V commit 35f2806b481f5b9207f25e1886cba5d1c4d12cc7 upstream. We added runtime allocation of 16G pages in commit 4ae279c2c96a ("powerpc/mm/hugetlb: Allow runtime allocation of 16G

[PATCH 4.14 151/183] dm: fix to_sector() for 32bit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 0bdb50c531f7377a9da80d3ce2d61f389c84cb30 upstream. A dm-raid array with devices larger than 4GB won't assemble on a 32 bit host since _check_data_dev_sectors() was added in 4.

[PATCH 4.14 145/183] powerpc/traps: fix recoverability of machine check handling on book3s/32

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 0bbea75c476b77fa7d7811d6be911cc7583e640f upstream. Looks like book3s/32 doesn't set RI on machine check, so checking RI before calling die() will always be fatal alltho

[PATCH 4.14 149/183] arm64: debug: Ensure debug handlers check triggering exception level

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 6bd288569b50bc89fa5513031086746968f585cb upstream. Debug exception handlers may be called for exceptions generated both by user and kernel code. In many cases, this is check

[PATCH 4.14 139/183] powerpc/wii: properly disable use of BATs when requested.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 6d183ca8baec983dc4208ca45ece3c36763df912 upstream. 'nobats' kernel parameter or some options like CONFIG_DEBUG_PAGEALLOC deny the use of BATS for mapping memory. This

[PATCH 4.14 138/183] powerpc/32: Clear on-stack exception marker upon exception return

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 9580b71b5a7863c24a9bd18bcd2ad759b86b1eff upstream. Clear the on-stack STACK_FRAME_REGS_MARKER on exception exit in order to avoid confusing stacktrace like the one belo

[PATCH 4.14 133/183] serial: 8250_pci: Fix number of ports for ACCES serial cards

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jay Dolan commit b896b03bc7fce43a07012cc6bf5e2ab2fddf3364 upstream. Have the correct number of ports created for ACCES serial cards. Two port cards show up as four ports, and four port cards s

Re: [PATCH] usb: typec: tcpm: collision avoidance

On Fri, Mar 22, 2019 at 12:51 AM Kyle Tso wrote: > > On Wed, Mar 20, 2019 at 1:38 AM Guenter Roeck wrote: > > > > > static enum tcpm_state tcpm_default_state(struct tcpm_port *port) > > > { > > > if (port->port_type == TYPEC_PORT_DRP) { > > > @@ -600,6 +664,9 @@ static void tcpm_debugfs_

[PATCH 4.14 165/183] perf intel-pt: Fix overlap calculation for padding

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 5a99d99e3310a565b0cf63f785b347be9ee0da45 upstream. Auxtrace records might have up to 7 bytes of padding appended. Adjust the overlap accordingly. Signed-off-by: Adrian Hu

[PATCH 4.14 166/183] perf intel-pt: Fix divide by zero when TSC is not available

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 076333870c2f5bdd9b6d31e7ca1909cf0c84cbfa upstream. When TSC is not available, "timeless" decoding is used but a divide by zero occurs if perf_time_to_tsc() is called. Ens

[PATCH 4.14 163/183] perf intel-pt: Fix CYC timestamp calculation after OVF

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 03997612904866abe7cdcc992784ef65cb3a4b81 upstream. CYC packet timestamp calculation depends upon CBR which was being cleared upon overflow (OVF). That can cause errors due

[PATCH 4.14 168/183] tpm/tpm_crb: Avoid unaligned reads in crb_recv()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Sakkinen commit 3d7a850fdc1a2e4d2adbc95cc0fc962974725e88 upstream. The current approach to read first 6 bytes from the response and then tail of the response, can cause the 2nd memcpy_f

[PATCH 4.14 159/183] NFSv4.1: Reinitialise sequence results before retransmitting a request

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit c1dffe0bf7f9c3d57d9f237a7cb2a81e62babd2b upstream. If we have to retransmit a request, we should ensure that we reinitialise the sequence results structure, since in the

[PATCH 4.14 169/183] tpm: Unify the send callback behaviour

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Sakkinen commit f5595f5baa30e009bf54d0d7653a9a0cc465be60 upstream. The send() callback should never return length as it does not in every driver except tpm_crb in the success case. The

[PATCH 4.14 157/183] nfsd: fix memory corruption caused by readdir

4.14-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit b602345da6cbb135ba68cf042df8ec9a73da7981 upstream. If the result of an NFSv3 readdir{,plus} request results in the "offset" on one entry having to be split across 2 pages, and

[PATCH 4.14 173/183] media: vimc: Add vimc-streamer for stream control

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lucas A. M. Magalhães commit adc589d2a20808fb99d46a78175cd023f2040338 upstream. Add a linear pipeline logic for the stream control. It's created by walking backwards on the entity graph. When

[PATCH 4.14 155/183] NFS: Fix an I/O request leakage in nfs_do_recoalesce

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 4d91969ed4dbcefd0e78f77494f0cb8fada9048a upstream. Whether we need to exit early, or just reprocess the list, we must not lost track of the request which failed to get r

[PATCH 4.14 153/183] cpcap-charger: generate events for userspace

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Machek commit fd10606f93a149a9f3d37574e5385b083b4a7b32 upstream. The driver doesn't generate uevents on charger connect/disconnect. This leads to UPower not detecting when AC is on or of

[PATCH 4.14 158/183] nfsd: fix wrong check in write_v4_end_grace()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yihao Wu commit dd838821f0a29781b185cd8fb8e48d5c177bd838 upstream. Commit 62a063b8e7d1 "nfsd4: fix crash on writing v4_end_grace before nfsd startup" is trying to fix a NULL dereference issue,

<    1   2   3   4   5   6   7   8   9   10   >