[PATCH 4.19 152/190] KVM: x86: optimize check for valid PAT value

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 674ea351cdeb01d2740edce31db7f2d79ce6095d ] This check will soon be done on every nested vmentry and vmexit, "parallelize" it using bitwise operations. Reviewed-by: Sean Christopherson Signed-off-by: Paolo Bonzini Signed-off-by: Sasha Levin --- arch/x86/kvm/mtrr.c | 10 +-

[PATCH 4.19 148/190] scsi: zfcp: fix request object use-after-free in send path causing wrong traces

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 106d45f350c7cac876844dc685845cba4ffdb70b ] When tracing instances where we open and close WKA ports, we also pass the request-ID of the respective FSF command. But after successfully sending the FSF command we must not use the request-object anymore, as this might result in an u

[PATCH 4.19 121/190] ARM: dts: qcom: ipq4019: enlarge PCIe BAR range

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit f3e35357cd460a8aeb48b8113dc4b761a7d5c828 ] David Bauer reported that the VDSL modem (attached via PCIe) on his AVM Fritz!Box 7530 was complaining about not having enough space in the BAR. A closer inspection of the old qcom-ipq40xx.dtsi pulled from the GL-iNet repository listed:

[PATCH 4.19 147/190] staging: wilc1000: fix error path cleanup in wilc_wlan_initialize()

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 6419f818ababebc1116fb2d0e220bd4fe835d0e3 ] For the error path in wilc_wlan_initialize(), the resources are not cleanup in the correct order. Reverted the previous changes and use the correct order to free during error condition. Fixes: b46d68825c2d ("staging: wilc1000: remove CO

[PATCH 4.19 138/190] drm/amdgpu/{uvd,vcn}: fetch rings read_ptr after alloc

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 517b91f4cde3043d77b2178548473e8545ef07cb ] [What] readptr read always returns zero, since most likely these blocks are either power or clock gated. [How] fetch rptr after amdgpu_ring_alloc() which informs the power management code that the block is about to be used and hence the

[PATCH 4.19 112/190] IB/mlx5: Reset access mask when looping inside page fault handler

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 1abe186ed8a6593069bc122da55fc684383fdc1c ] If page-fault handler spans multiple MRs then the access mask needs to be reset before each MR handling or otherwise write access will be granted to mapped pages instead of read-only. Cc: # 3.19 Fixes: 7bdf65d411c1 ("IB/mlx5: Handle pa

[PATCH 4.19 117/190] media: i2c: tda1997x: select V4L2_FWNODE

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 5f2efda71c09b12012053f457fac7692f268b72c ] Building tda1997x fails now unless V4L2_FWNODE is selected: drivers/media/i2c/tda1997x.o: in function `tda1997x_parse_dt' undefined reference to `v4l2_fwnode_endpoint_parse' While at it, also sort the selections alphabetically Fixes:

[PATCH 4.19 119/190] ARM: dts: qcom: ipq4019: fix PCI range

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit da89f500cb55fb3f19c4b399b46d8add0abbd4d6 ] The PCI range is invalid and PCI attached devices doen't work. Signed-off-by: Mathias Kresin Signed-off-by: John Crispin Signed-off-by: Andy Gross Signed-off-by: Sasha Levin --- arch/arm/boot/dts/qcom-ipq4019.dtsi | 2 +- 1 file ch

[PATCH 4.19 116/190] cifs: Fix lease buffer length error

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit b57a55e2200ede754e4dc9cce4ba9402544b9365 ] There is a KASAN slab-out-of-bounds: BUG: KASAN: slab-out-of-bounds in _copy_from_iter_full+0x783/0xaa0 Read of size 80 at addr 88810c35e180 by task mount.cifs/539 CPU: 1 PID: 539 Comm: mount.cifs Not tainted 4.19 #10 Hardware name:

[PATCH 4.19 115/190] KVM: x86: Always use 32-bit SMRAM save state for 32-bit kernels

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit b68f3cc7d978943fcf85148165b00594c38db776 ] Invoking the 64-bit variation on a 32-bit kenrel will crash the guest, trigger a WARN, and/or lead to a buffer overrun in the host, e.g. rsm_load_state_64() writes r8-r15 unconditionally, but enum kvm_reg and thus x86_emulate_ctxt._regs

[PATCH 4.19 136/190] kvm: Check irqchip mode before assign irqfd

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 654f1f13ea56b92bacade8ce2725aea0457f91c0 ] When assigning kvm irqfd we didn't check the irqchip mode but we allow KVM_IRQFD to succeed with all the irqchip modes. However it does not make much sense to create irqfd even without the kernel chips. Let's provide a arch-dependent h

[PATCH 4.19 135/190] drm/amdkfd: Add missing Polaris10 ID

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 0a5a9c276c335870a1cecc4f02b76d6d6f663c8b ] This was added to amdgpu but was missed in amdkfd Signed-off-by: Kent Russell Reviewed-by: Alex Deucher Signed-off-by: Alex Deucher Cc: sta...@vger.kernel.rg Signed-off-by: Sasha Levin --- drivers/gpu/drm/amd/amdkfd/kfd_device.c |

[PATCH 4.19 132/190] signal/arc: Use force_sig_fault where appropriate

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 15773ae938d8d93d982461990bebad6e1d7a1830 ] Acked-by: Vineet Gupta Signed-off-by: "Eric W. Biederman" Signed-off-by: Sasha Levin --- arch/arc/mm/fault.c | 20 +--- 1 file changed, 5 insertions(+), 15 deletions(-) diff --git a/arch/arc/mm/fault.c b/arch/arc/mm/

[PATCH 4.19 133/190] ARC: mm: fix uninitialised signal code in do_page_fault

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 121e38e5acdc8e1e4cdb750fcdcc72f94e420968 ] Commit 15773ae938d8 ("signal/arc: Use force_sig_fault where appropriate") introduced undefined behaviour by leaving si_code unitiailized and leaking random kernel values to user space. Fixes: 15773ae938d8 ("signal/arc: Use force_sig_fau

[PATCH 4.19 131/190] dm crypt: move detailed message into debug level

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 7a1cd7238fde6ab367384a4a2998cba48330c398 ] The information about tag size should not be printed without debug info set. Also print device major:minor in the error message to identify the device instance. Also use rate limiting and debug level for info about used crypto API imple

[PATCH 4.19 129/190] PCI: dwc: Use devm_pci_alloc_host_bridge() to simplify code

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit e6fdd3bf5aecd8615f31a5128775b9abcf3e0d86 ] Use devm_pci_alloc_host_bridge() to simplify the error code path. This also fixes a leak in the dw_pcie_host_init() error path. Signed-off-by: Jisheng Zhang Signed-off-by: Lorenzo Pieralisi Signed-off-by: Bjorn Helgaas Acked-by: Gus

[PATCH 4.19 114/190] x86/kvm: move kvm_load/put_guest_xcr0 into atomic context

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 1811d979c71621aafc7b879477202d286f7e863b ] guest xcr0 could leak into host when MCE happens in guest mode. Because do_machine_check() could schedule out at a few places. For example: kvm_load_guest_xcr0 ... kvm_x86_ops->run(vcpu) { vmx_vcpu_run vmx_complete_atomic_exit

[PATCH 4.19 122/190] dt-bindings: mmc: Add supports-cqe property

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit c7fddbd5db5cffd10ed4d18efa20e36803d1899f ] Add supports-cqe optional property for MMC hosts. This property is used to identify the specific host controller supporting command queue. Signed-off-by: Sowjanya Komatineni Reviewed-by: Thierry Reding Reviewed-by: Rob Herring Signe

[PATCH 4.19 128/190] mmc: sdhci-pci: Add support for Intel CML

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 765c59675ab571caf7ada456bbfd23a73136b535 ] Add PCI Ids for Intel CML. Signed-off-by: Adrian Hunter Signed-off-by: Ulf Hansson Signed-off-by: Sasha Levin --- drivers/mmc/host/sdhci-pci-core.c | 2 ++ drivers/mmc/host/sdhci-pci.h | 2 ++ 2 files changed, 4 insertions(+)

[PATCH 4.19 126/190] dm mpath: fix missing call of path selector type->end_io

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 5de719e3d01b4abe0de0d7b857148a880ff2a90b ] After commit 396eaf21ee17 ("blk-mq: improve DM's blk-mq IO merging via blk_insert_cloned_request feedback"), map_request() will requeue the tio when issued clone request return BLK_STS_RESOURCE or BLK_STS_DEV_RESOURCE. Thus, if device d

[PATCH 4.19 113/190] kvm: mmu: Fix overflow on kvm mmu page limit calculation

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit bc8a3d8925a8fa09fa550e0da115d95851ce33c6 ] KVM bases its memory usage limits on the total number of guest pages across all memslots. However, those limits, and the calculations to produce them, use 32 bit unsigned integers. This can result in overflow if a VM has more guest pages

[PATCH 4.19 127/190] blk-mq: free hw queues resource in hctxs release handler

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit c7e2d94b3d1634988a95ac4d77a72dc7487ece06 ] Once blk_cleanup_queue() returns, tags shouldn't be used any more, because blk_mq_free_tag_set() may be called. Commit 45a9c9d909b2 ("blk-mq: Fix a use-after-free") fixes this issue exactly. However, that commit introduces another issue

[PATCH 4.19 089/190] dt-bindings: iio: adc: exynos-adc: Add S5PV210 variant

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit a9b0a2a7c19316588421b94946c8e2e5a84ac14e ] Add information about new compatible for S5PV210 Signed-off-by: Jonathan Bakker Signed-off-by: Paweł Chmiel Signed-off-by: Jonathan Cameron Signed-off-by: Sasha Levin --- .../devicetree/bindings/iio/adc/samsung,exynos-adc.txt

[PATCH 4.19 091/190] mt76: fix corrupted software generated tx CCMP PN

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 906d2d3f874a54183df5a609fda180adf0462428 ] Since ccmp_pn is u8 *, the second half needs to start at array index 4 instead of 0. Fixes a connection stall after a certain amount of traffic Fixes: 23405236460b9 ("mt76: fix transmission of encrypted management frames") Cc: sta...@vg

[PATCH 4.19 109/190] drm/i915: Sanity check mmap length against object size

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 000c4f90e3f0194eef218ff2c6a8fd8ca1de4313 ] We assumed that vm_mmap() would reject an attempt to mmap past the end of the filp (our object), but we were wrong. Applications that tried to use the mmap beyond the end of the object would be greeted by a SIGBUS. After this patch, tho

[PATCH 4.19 102/190] btrfs: init csum_list before possible free

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit e49be14b8d80e23bb7c53d78c21717a474ade76b ] The scrub_ctx csum_list member must be initialized before scrub_free_ctx is called. If the csum_list is not initialized beforehand, the list_empty call in scrub_free_csums will result in a null deref if the allocation fails in the for lo

[PATCH 4.19 098/190] mmc: renesas_sdhi: Fix card initialization failure in high speed mode

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit d30ae056adb81e1d2b8b953efa74735a020b8e3b ] This fixes card initialization failure in high speed mode. If U-Boot uses SDR or HS200/400 mode before starting Linux and Linux DT does not enable SDR/HS200/HS400 mode, card initialization fails in high speed mode. It is necessary to i

[PATCH 4.19 097/190] powerpc/kvm: Save and restore host AMR/IAMR/UAMOR

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit c3c7470c75566a077c8dc71dcf8f1948b8ddfab4 ] When the hash MMU is active the AMR, IAMR and UAMOR are used for pkeys. The AMR is directly writable by user space, and the UAMOR masks those writes, meaning both registers are effectively user register state. The IAMR is used to create

[PATCH 4.19 104/190] PCI: qcom: Dont deassert reset GPIO during probe

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 02b485e31d98265189b91f3e69c43df2ed50610c ] Acquiring the reset GPIO low means that reset is being deasserted, this is followed almost immediately with qcom_pcie_host_init() asserting it, initializing it and then finally deasserting it again, for the link to come up. Some PCIe de

[PATCH 4.19 096/190] spi: spi-gpio: fix SPI_CS_HIGH capability

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit b89fefda7d4e3a649129584d855be233c7465264 ] spi-gpio is capable of dealing with active-high chip-selects. Unfortunately, commit 4b859db2c606 ("spi: spi-gpio: add SPI_3WIRE support") broke this by setting master->mode_bits, which overrides the setting in the spi-bitbang code. Fix

[PATCH 4.19 095/190] x86/kvmclock: set offset for kvm unstable clock

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit b5179ec4187251a751832193693d6e474d3445ac ] VMs may show incorrect uptime and dmesg printk offsets on hypervisors with unstable clock. The problem is produced when VM is rebooted without exiting from qemu. The fix is to calculate clock offset not only for stable clock but for uns

[PATCH 4.19 110/190] usb: typec: tcpm: Try PD-2.0 if sink does not respond to 3.0 source-caps

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 976daf9d1199932df80e7b04546d1a1bd4ed5ece ] PD 2.0 sinks are supposed to accept src-capabilities with a 3.0 header and simply ignore any src PDOs which the sink does not understand such as PPS but some 2.0 sinks instead ignore the entire PD_DATA_SOURCE_CAP message, causing contrac

[PATCH 4.19 076/190] ARC: show_regs: lockdep: re-enable preemption

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit f731a8e89f8c78985707c626680f3e24c7a60772 ] signal handling core calls show_regs() with preemption disabled which on ARC takes mmap_sem for mm/vma access, causing lockdep splat. | [ARCLinux]# ./segv-null-ptr | potentially unexpected fatal signal 11. | BUG: sleeping function calle

[PATCH 4.19 107/190] CIFS: Fix leaking locked VFS cache pages in writeback retry

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 165df9a080b6863ae286fa01780c13d87cd81076 ] If we don't find a writable file handle when retrying writepages we break of the loop and do not unlock and put pages neither from wdata2 nor from the original wdata. Fix this by walking through all the remaining pages and cleanup them p

[PATCH 4.19 100/190] btrfs: scrub: move scrub_setup_ctx allocation out of device_list_mutex

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 0e94c4f45d14cf89d1f40c91b0a8517e791672a7 ] The scrub context is allocated with GFP_KERNEL and called from btrfs_scrub_dev under the fs_info::device_list_mutex. This is not safe regarding reclaim that could try to flush filesystem data in order to get the memory. And the device_li

[PATCH 4.19 092/190] drm/nouveau: Dont WARN_ON VCPI allocation failures

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit b513a18cf1d705bd04efd91c417e79e4938be093 ] This is much louder then we want. VCPI allocation failures are quite normal, since they will happen if any part of the modesetting process is interrupted by removing the DP MST topology in question. So just print a debugging message on V

[PATCH 4.19 101/190] btrfs: scrub: fix circular locking dependency warning

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 1cec3f27168d7835ff3d23ab371cd548440131bb ] This fixes a longstanding lockdep warning triggered by fstests/btrfs/011. Circular locking dependency check reports warning[1], that's because the btrfs_scrub_dev() calls the stack #0 below with, the fs_info::scrub_lock held. The test c

[PATCH 4.19 105/190] drm: add __user attribute to ptr_to_compat()

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit e552f0851070fe4975d610a99910be4e9bf5d7bd ] The ptr_to_compat() call takes a "void __user *", so cast the compat drm calls that use it to avoid the following warnings from sparse: drivers/gpu/drm/drm_ioc32.c:188:39: warning: incorrect type in argument 1 (different address spaces

[PATCH 4.19 108/190] drm/i915: Handle vm_mmap error during I915_GEM_MMAP ioctl with WC set

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit ebfb6977801da521d8d5d752d373a187e2a2b9b3 ] Add err goto label and use it when VMA can't be established or changes underneath. v2: - Dropping Fixes: as it's indeed impossible to race an object to the error address. (Chris) v3: - Use IS_ERR_VALUE (Chris) Reported-by: Adam Zabro

[PATCH 4.19 067/190] btrfs: Remove extent_io_ops::fill_delalloc

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 5eaad97af8aeff38debe7d3c69ec3a0d71f8350f ] This callback is called only from writepage_delalloc which in turn is guaranteed to be called from the data page writeout path. In the end there is no reason to have the call to this function to be indrected via the extent_io_ops structu

[PATCH 4.19 090/190] iio: adc: exynos-adc: Use proper number of channels for Exynos4x12

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 103cda6a3b8d2c10d5f8cd7abad118e9db8f4776 ] Exynos4212 and Exynos4412 have only four ADC channels so using "samsung,exynos-adc-v1" compatible (for eight channels ADCv1) on them is wrong. Add a new compatible for Exynos4x12. Signed-off-by: Krzysztof Kozlowski Cc: Signed-off-by:

[PATCH 4.19 099/190] btrfs: scrub: pass fs_info to scrub_setup_ctx

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 92f7ba434f51e8e9317f1d166105889aa230abd2 ] We can pass fs_info directly as this is the only member of btrfs_device that's bing used inside scrub_setup_ctx. Reviewed-by: Nikolay Borisov Signed-off-by: David Sterba Signed-off-by: Sasha Levin --- fs/btrfs/scrub.c | 9 -

[PATCH 4.19 094/190] iwlwifi: add new card for 9260 series

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 3941310cf665b8a7965424d2a185c80782faa030 ] Add one PCI ID for 9260 series. CC: # 4.14+ Signed-off-by: Ihab Zhaika Signed-off-by: Luca Coelho Signed-off-by: Sasha Levin --- drivers/net/wireless/intel/iwlwifi/pcie/drv.c | 1 + 1 file changed, 1 insertion(+) diff --git a/driv

[PATCH 4.19 073/190] btrfs: volumes: Make sure no dev extent is beyond device boundary

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 05a37c48604c19b50873fd9663f9140c150469d1 ] Add extra dev extent end check against device boundary. Signed-off-by: Qu Wenruo Reviewed-by: David Sterba Signed-off-by: David Sterba Signed-off-by: Sasha Levin --- fs/btrfs/volumes.c | 17 + 1 file changed, 17 ins

[PATCH 4.19 103/190] PCI: qcom: Fix error handling in runtime PM support

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 6e5da6f7d82474e94c2d4a38cf9ca4edbb3e03a0 ] The driver does not cope with the fact that probe can fail in a number of cases after enabling runtime PM on the device; this results in warnings about "Unbalanced pm_runtime_enable". Furthermore if probe fails after invoking qcom_pcie_h

Re: [Patch 08/13] media: am437x-vpfe: Maintain a reference to the current vpfe_fmt

2019-09-13 Thread Hans Verkuil
On 9/9/19 6:27 PM, Benoit Parrot wrote: > Keep a reference to the currently selected struct vpfe_fmt * object. > By doing so we rename the current struct v4l2_format * member from > fmt to v_fmt. > The added struct vpfe_fmt * reference is set to "const" so we also > constify all accesses and relate

[PATCH 4.19 070/190] scsi: megaraid_sas: Add check for reset adapter bit

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit de93b40d98ead27ee2f7f7df93fdd4914a6c8d8d ] For SAS3 and later controllers, FW sets the reset adapter bit indicating the driver to perform a controller reset. Driver needs to check if this bit is set before doing a reset. This reduces the driver probe failure time to 180seconds

[PATCH 4.19 083/190] mfd: Kconfig: Fix I2C_DESIGNWARE_PLATFORM dependencies

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 09fdc98577120d4f47601c3127efde726a2300c6 ] INTEL_SOC_PMIC, INTEL_SOC_PMIC_CHTWC and MFD_TPS68470 select the I2C_DESIGNWARE_PLATFORM without its dependencies making it possible to see warning and build error like below: WARNING: unmet direct dependencies detected for I2C_DESIGNWA

[PATCH 4.19 088/190] iio: adc: exynos-adc: Add S5PV210 variant

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 882bf52fdeab47dbe991cc0e564b0b51c571d0a3 ] S5PV210's ADC variant is almost the same as v1 except that it has 10 channels and doesn't require the pmu register Signed-off-by: Jonathan Bakker Signed-off-by: Paweł Chmiel Signed-off-by: Jonathan Cameron Signed-off-by: Sasha Levin

[PATCH 4.19 072/190] powerpc/pkeys: Fix handling of pkey state across fork()

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 2cd4bd192ee94848695c1c052d87913260e10f36 ] Protection key tracking information is not copied over to the mm_struct of the child during fork(). This can cause the child to erroneously allocate keys that were already allocated. Any allocated execute-only key is lost aswell. Add co

[PATCH 4.19 086/190] bcache: treat stale && dirty keys as bad keys

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 58ac323084ebf44f8470eeb8b82660f9d0ee3689 ] Stale && dirty keys can be produced in the follow way: After writeback in write_dirty_finish(), dirty keys k1 will replace by clean keys k2 ==>ret = bch_btree_insert(dc->disk.c, &keys, NULL, &w->key); ==>btree_insert_fn(struct btree_op *

[PATCH 4.19 080/190] crypto: ccree - add missing inline qualifier

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit f1071c3e2473ae19a7f5d892a187c4cab1a61f2e ] Commit 1358c13a48c4 ("crypto: ccree - fix resume race condition on init") was missing a "inline" qualifier for stub function used when CONFIG_PM is not set causing a build warning. Fixes: 1358c13a48c4 ("crypto: ccree - fix resume race c

[PATCH 4.19 082/190] drm/i915/ilk: Fix warning when reading emon_status with no output

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit cab870b7fdf3c4be747d88de5248b28db7d4055e ] When there is no output no one will hold a runtime_pm reference causing a warning when trying to read emom_status in debugfs. [22.756480] [ cut here ] [22.756489] RPM wakelock ref not held during HW access [22.75

[PATCH 4.19 069/190] scsi: megaraid_sas: Fix combined reply queue mode detection

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit e29c322133472628c6de85efb99ccd3b3df5571e ] For Invader series, if FW supports more than 8 MSI-x vectors, driver needs to enable combined reply queue mode. For Ventura series, driver enables combined reply queue mode in case of more than 16 MSI-x vectors. Signed-off-by: Sumit Sax

[PATCH 4.19 071/190] scsi: megaraid_sas: Use 63-bit DMA addressing

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 894169db12463cea08d0e2a9e35f42b291340e5a ] Although MegaRAID controllers support 64-bit DMA addressing, as per hardware design, DMA address with all 64-bits set (0x-) results in a firmware fault. Driver will set 63-bit DMA mask to ensure the above address will no

[PATCH 4.19 084/190] tpm: Fix some name collisions with drivers/char/tpm.h

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 8ab547a2dcfac6ec184a5e036e1093eb3f7a215c ] * Rename TPM_BUFSIZE defined in drivers/char/tpm/st33zp24/st33zp24.h to ST33ZP24_BUFSIZE. * Rename TPM_BUFSIZE defined in drivers/char/tpm/tpm_i2c_infineon.c to TPM_I2C_INFINEON_BUFSIZE. * Rename TPM_RETRY in tpm_i2c_nuvoton to TPM_I

[PATCH 4.19 044/190] x86/kvm/lapic: preserve gfn_to_hva_cache len on cache reinit

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit a7c42bb6da6b1b54b2e7bd567636d72d87b10a79 ] vcpu->arch.pv_eoi is accessible through both HV_X64_MSR_VP_ASSIST_PAGE and MSR_KVM_PV_EOI_EN so on migration userspace may try to restore them in any order. Values match, however, kvm_lapic_enable_pv_eoi() uses different length: for Hype

[PATCH 4.19 041/190] KVM: x86: hyperv: consistently use hv_vcpu for struct kvm_vcpu_hv variables

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 1779a39f786397760ae7a7cc03cf37697d8ae58d ] Rename 'hv' to 'hv_vcpu' in kvm_hv_set_msr/kvm_hv_get_msr(); 'hv' is 'reserved' for 'struct kvm_hv' variables across the file. Signed-off-by: Vitaly Kuznetsov Reviewed-by: Roman Kagan Signed-off-by: Paolo Bonzini Signed-off-by: Sasha

[PATCH 4.19 068/190] btrfs: Fix error handling in btrfs_cleanup_ordered_extents

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit d1051d6ebf8ef3517a5a3cf82bba8436d190f1c2 ] Running btrfs/124 in a loop hung up on me sporadically with the following call trace: btrfs D0 5760 5324 0x Call Trace: ? __schedule+0x243/0x800 schedule+0x33/0x90 btrf

[PATCH 4.19 077/190] ARC: mm: do_page_fault fixes #1: relinquish mmap_sem if signal arrives while handle_mm_fault

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 4d447455e73b47c43dd35fcc38ed823d3182a474 ] do_page_fault() forgot to relinquish mmap_sem if a signal came while handling handle_mm_fault() - due to say a ctl+c or oom etc. This would later cause a deadlock by acquiring it twice. This came to light when running libc testsuite tst

[PATCH 4.19 050/190] Drivers: hv: kvp: Fix the recent regression caused by incorrect clean-up

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit e670de54c813b5bc3672dd1c67871dc60e9206f4 ] In kvp_send_key(), we do need call process_ib_ipinfo() if message->kvp_hdr.operation is KVP_OP_GET_IP_INFO, because it turns out the userland hv_kvp_daemon needs the info of operation, adapter_id and addr_family. With the incorrect fc62c

[PATCH 4.19 078/190] IB/uverbs: Fix OOPs upon device disassociation

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 425784aa5b029eeb80498c73a68f62c3ad1d3b3f ] The async_file might be freed before the disassociation has been ended, causing qp shutdown to use after free on it. Since uverbs_destroy_ufile_hw is not a fence, it returns if a disassociation is ongoing in another thread. It has to be

[PATCH 4.19 079/190] crypto: ccree - fix resume race condition on init

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 1358c13a48c43f5e4de0c1835291837a27b9720c ] We were enabling autosuspend, which is using data set by the hash module, prior to the hash module being inited, casuing a crash on resume as part of the startup sequence if the race was lost. This was never a real problem because the P

[PATCH 4.19 048/190] drm/atomic_helper: Disallow new modesets on unregistered connectors

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 4d80273976bf880c4bed9359b8f2d45663140c86 ] With the exception of modesets which would switch the DPMS state of a connector from on to off, we want to make sure that we disallow all modesets which would result in enabling a new monitor or a new mode configuration on a monitor if t

[PATCH 4.19 049/190] Drivers: hv: kvp: Fix the indentation of some "break" statements

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit d544c22d6951be3386ac59bb9a99c9bc566b3f09 ] No functional change. Signed-off-by: Dexuan Cui Cc: K. Y. Srinivasan Cc: Haiyang Zhang Cc: Stephen Hemminger Signed-off-by: K. Y. Srinivasan Signed-off-by: Greg Kroah-Hartman Signed-off-by: Sasha Levin --- drivers/hv/hv_kvp.c |

[PATCH 4.19 066/190] Btrfs: fix deadlock with memory reclaim during scrub

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit a5fb11429167ee6ddeeacc554efaf5776b36433a ] When a transaction commit starts, it attempts to pause scrub and it blocks until the scrub is paused. So while the transaction is blocked waiting for scrub to pause, we can not do memory allocation with GFP_KERNEL from scrub, otherwise w

[PATCH 4.19 063/190] drm/i915: Cleanup gt powerstate from gem

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 30b710840e4b9c9699d3d4b33fb19ad8880d4614 ] Since the gt powerstate is allocated by i915_gem_init, clean it from i915_gem_fini for symmetry and to correct the imbalance on error. Signed-off-by: Chris Wilson Reviewed-by: Mika Kuoppala Link: https://patchwork.freedesktop.org/pat

[PATCH 4.19 065/190] Btrfs: clean up scrub is_dev_replace parameter

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 32934280967d00dc2b5c4d3b63b21a9c8638326e ] struct scrub_ctx has an ->is_dev_replace member, so there's no point in passing around is_dev_replace where sctx is available. Signed-off-by: Omar Sandoval Signed-off-by: David Sterba Signed-off-by: Sasha Levin --- fs/btrfs/scrub.c

[PATCH 4.19 064/190] KVM: PPC: Book3S HV: Fix race between kvm_unmap_hva_range and MMU mode switch

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 234ff0b729ad882d20f7996591a964965647addf ] Testing has revealed an occasional crash which appears to be caused by a race between kvmppc_switch_mmu_to_hpt and kvm_unmap_hva_range_hv. The symptom is a NULL pointer dereference in __find_linux_pte() called from kvm_unmap_radix() with

[PATCH 4.19 061/190] media: vim2m: use cancel_delayed_work_sync instead of flush_schedule_work

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 52117be68b82ee05c96da0a7beec319906ccf6cc ] The use of flush_schedule_work() made no sense and caused a syzkaller error. Replace with the correct cancel_delayed_work_sync(). Signed-off-by: Hans Verkuil Reported-by: syzbot+69780d144754b8071...@syzkaller.appspotmail.com Cc:

[PATCH 4.19 062/190] drm/i915: Restore sane defaults for KMS on GEM error load

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 7ed43df720c007d60bee6d81da07bcdc7e4a55ae ] If we fail during GEM initialisation, we scrub the HW state by performing a device level GPU resuet. However, we want to leave the system in a usable state (with functioning KMS but no GEM) so after scrubbing the HW state, we need to res

[PATCH 4.19 043/190] KVM: hyperv: define VP assist page helpers

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 72bbf9358c3676bd89dc4bd8fb0b1f2a11c288fc ] The state related to the VP assist page is still managed by the LAPIC code in the pv_eoi field. Signed-off-by: Ladi Prosek Signed-off-by: Vitaly Kuznetsov Reviewed-by: Liran Alon Signed-off-by: Paolo Bonzini Signed-off-by: Sasha Lev

[PATCH 4.19 060/190] media: vim2m: use workqueue

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 144bd0ee304c7d0690eec285aee93019d3f30fc8 ] v4l2_ctrl uses mutexes, so we can't setup a ctrl_handler in interrupt context. Switch to a workqueue instead and drop the timer. Signed-off-by: Hans Verkuil Reviewed-by: Mauro Carvalho Chehab Signed-off-by: Mauro Carvalho Chehab Sign

[PATCH 4.19 054/190] ARM: davinci: da8xx: define gpio interrupts as separate resources

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 58a0afbf4c99ac355df16773af835b919b9432ee ] Since commit eb3744a2dd01 ("gpio: davinci: Do not assume continuous IRQ numbering") the davinci GPIO driver fails to probe if we boot in legacy mode from any of the board files. Since the driver now expects every interrupt to be defined

[PATCH 4.19 055/190] ARM: davinci: dm365: define gpio interrupts as separate resources

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 193c04374e281a56c7d4f96e66d329671945bebe ] Since commit eb3744a2dd01 ("gpio: davinci: Do not assume continuous IRQ numbering") the davinci GPIO driver fails to probe if we boot in legacy mode from any of the board files. Since the driver now expects every interrupt to be defined

[PATCH 4.19 053/190] drm/amd/dm: Understand why attaching path/tile properties are needed

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 04ac4b0ed412f65230b456fcd9aa07e13befff89 ] Path property is used for userspace to know what MST connector goes to what actual DRM DisplayPort connector, the tiling property is for tiling configurations. Not sure what else there is to figure out. Signed-off-by: Lyude Paul Revi

[PATCH 4.19 058/190] ARM: davinci: dm644x: define gpio interrupts as separate resources

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit adcf60ce14c8250761af9de907eb6c7d096c26d3 ] Since commit eb3744a2dd01 ("gpio: davinci: Do not assume continuous IRQ numbering") the davinci GPIO driver fails to probe if we boot in legacy mode from any of the board files. Since the driver now expects every interrupt to be defined

[PATCH 4.19 052/190] drm/amd/pp: Fix truncated clock value when set watermark

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 4d454e9ffdb1ef5a51ebc147b5389c96048db683 ] the clk value should be tranferred to MHz first and then transfer to uint16. otherwise, the clock value will be truncated. Reviewed-by: Alex Deucher Reported-by: Hersen Wu Signed-off-by: Rex Zhu Signed-off-by: Alex Deucher Cc: sta..

[PATCH 4.19 051/190] powerplay: Respect units on max dcfclk watermark

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit f191415b24a3ad3fa22088af7cd7fc328a2f469f ] In a refactor, the watermark clock inputs to powerplay from DC were changed from units of 10kHz to kHz clocks. One division by 100 was not converted into a division by 1000. Signed-off-by: David Francis Reviewed-by: Harry Wentland Si

[PATCH 4.19 056/190] ARM: davinci: dm646x: define gpio interrupts as separate resources

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 2c9c83491f30afbce25796e185cd4d5e36080e31 ] Since commit eb3744a2dd01 ("gpio: davinci: Do not assume continuous IRQ numbering") the davinci GPIO driver fails to probe if we boot in legacy mode from any of the board files. Since the driver now expects every interrupt to be defined

[PATCH 4.19 030/190] drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse"

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 3cf71bc9904d7ee4a25a822c5dcb54c7804ea388 ] This re-applies the workaround for "some DP sinks, [which] are a little nuts" from commit 1a36147bb939 ("drm/i915: Perform link quality check unconditionally during long pulse"). It makes the secondary AOC E2460P monitor connected via DP

[PATCH 4.19 026/190] clk: s2mps11: Add used attribute to s2mps11_dt_match

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 9c940bbe2bb47e03ca5e937d30b6a50bf9c0e671 ] Clang warns after commit 8985167ecf57 ("clk: s2mps11: Fix matching when built as module and DT node contains compatible"): drivers/clk/clk-s2mps11.c:242:34: warning: variable 's2mps11_dt_match' is not needed and will not be emitted [-Wu

[PATCH 4.19 025/190] nvme-fc: use separate work queue to avoid warning

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 8730c1ddb69bdeeb10c1f613a4e15e95862b1981 ] When tearing down a controller the following warning is issued: WARNING: CPU: 0 PID: 30681 at ../kernel/workqueue.c:2418 check_flush_dependency This happens as the err_work workqueue item is scheduled on the system workqueue (which has

[PATCH 4.19 028/190] modules: always page-align module section allocations

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 38f054d549a869f22a02224cd276a27bf14b6171 ] Some arches (e.g., arm64, x86) have moved towards non-executable module_alloc() allocations for security hardening reasons. That means that the module loader will need to set the text section of a module to executable, regardless of whet

[PATCH 4.19 021/190] media: stm32-dcmi: fix irq = 0 case

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit dbb9fcc8c2d8d4ea1104f51d4947a8a8199a2cb5 ] Manage the irq = 0 case, where we shall return an error. Fixes: b5b5a27bee58 ("media: stm32-dcmi: return appropriate error codes during probe") Signed-off-by: Fabien Dessenne Reported-by: Pavel Machek Acked-by: Pavel Machek Signed-

[PATCH 4.19 029/190] kernel/module: Fix mem leak in module_add_modinfo_attrs

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit bc6f2a757d525e001268c3658bd88822e768f8db ] In module_add_modinfo_attrs if sysfs_create_file fails, we forget to free allocated modinfo_attrs and roll back the sysfs files. Fixes: 03e88ae1b13d ("[PATCH] fix module sysfs files reference counting") Reviewed-by: Miroslav Benes Sign

[PATCH 4.19 027/190] remoteproc: qcom: q6v5: shore up resource probe handling

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 1e2517d126171a41f801738ffd19687836cd178a ] Commit d5269c4553a6 ("remoteproc: qcom: q6v5: Propagate EPROBE_DEFER") fixed up our probe code to handle -EPROBE_DEFER, but it ignored one of our interrupts, and it also didn't really handle all the other error codes you might get (e.g.,

[PATCH 4.19 039/190] drm/amdgpu: Update gc_9_0 golden settings.

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit c55045adf7210d246a016c961916f078ed31a951 ] Add mmDB_DEBUG3 settings. Signed-off-by: Feifei Xu Reviewed-by: Evan Quan Signed-off-by: Alex Deucher Cc: sta...@vger.kernel.org Signed-off-by: Sasha Levin --- drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 1 + 1 file changed, 1 insertio

[PATCH 4.19 038/190] drm/amdgpu/gfx9: Update gfx9 golden settings.

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 54d682d9a5b357eb711994fa94ef1bc44d7ce9d9 ] Update the goldensettings for vega20. Signed-off-by: Feifei Xu Signed-off-by: Evan Quan Reviewed-by: Hawking Zhang Reviewed-by: Alex Deucher Signed-off-by: Alex Deucher Signed-off-by: Sasha Levin --- drivers/gpu/drm/amd/amdgpu/gf

[PATCH 4.19 024/190] riscv: remove unused variable in ftrace

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 397182e0db56b8894a43631ce72de14d90a29834 ] Noticed while building kernel-4.20.0-0.rc5.git2.1.fc30 for Fedora 30/RISCV. [..] BUILDSTDERR: arch/riscv/kernel/ftrace.c: In function 'prepare_ftrace_return': BUILDSTDERR: arch/riscv/kernel/ftrace.c:135:6: warning: unused variable 'err'

[PATCH 4.19 040/190] KVM: x86: hyperv: enforce vp_index < KVM_MAX_VCPUS

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 9170200ec0ebad70e5b9902bc93e2b1b11456a3b ] Hyper-V TLFS (5.0b) states: > Virtual processors are identified by using an index (VP index). The > maximum number of virtual processors per partition supported by the > current implementation of the hypervisor can be obtained through C

[PATCH 4.19 023/190] scripts/decode_stacktrace: match basepath using shell prefix operator, not regex

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 31013836a71e07751a6827f9d2ad41ef502ddaff ] The basepath may contain special characters, which would confuse the regex matcher. ${var#prefix} does the right thing. Link: http://lkml.kernel.org/r/20190518055946.181563-1-drink...@chromium.org Fixes: 67a28de47faa8358 ("scripts/deco

[PATCH 4.19 035/190] Drivers: hv: kvp: Fix two "this statement may fall through" warnings

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit fc62c3b1977d62e6374fd6e28d371bb42dfa5c9d ] We don't need to call process_ib_ipinfo() if message->kvp_hdr.operation is KVP_OP_GET_IP_INFO in kvp_send_key(), because here we just need to pass on the op code from the host to the userspace; when the userspace returns the info request

[PATCH 4.19 036/190] x86, hibernate: Fix nosave_regions setup for hibernation

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit cc55f7537db6af371e9c1c6a71161ee40f918824 ] On 32bit systems, nosave_regions(non RAM areas) located between max_low_pfn and max_pfn are not excluded from hibernation snapshot currently, which may result in a machine check exception when trying to access these unsafe regions during

[PATCH 4.19 034/190] keys: Fix the use of the C++ keyword "private" in uapi/linux/keyctl.h

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 2ecefa0a15fd0ef88b9cd5d15ceb813008136431 ] The keyctl_dh_params struct in uapi/linux/keyctl.h contains the symbol "private" which means that the header file will cause compilation failure if #included in to a C++ program. Further, the patch that added the same struct to the keyu

[PATCH 4.19 033/190] scsi: qla2xxx: Move log messages before issuing command to firmware

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 9fe278f44b4bc06cc61e33b2af65f87d507d13d0 ] There is a probability that the SRB structure might have been released by the time the debug log message dereferences it. This patch moved the log messages before the command is issued to the firmware to prevent unknown behavior and ker

[PATCH 4.19 031/190] media: cec/v4l2: move V4L2 specific CEC functions to V4L2

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 9cfd2753f8f3923f89cbb15f940f3aa0e7202d3e ] Several CEC functions are actually specific for use with receivers, i.e. they should be part of the V4L2 subsystem, not CEC. These functions deal with validating and modifying EDIDs for (HDMI) receivers, and they do not actually have an

[PATCH 4.19 022/190] arm64: dts: rockchip: enable usb-host regulators at boot on rk3328-rock64

2019-09-13 Thread Greg Kroah-Hartman
[ Upstream commit 26e2d7b03ea7ff254bf78305aa44dda62e70b78e ] After commit ef05bcb60c1a, boot from USB drives is broken. Fix this problem by enabling usb-host regulators during boot time. Fixes: ef05bcb60c1a ("arm64: dts: rockchip: fix vcc_host1_5v pin assign on rk3328-rock64") Cc: sta...@vger.ke

[PATCH 4.19 003/190] ALSA: hda/realtek - Add quirk for HP Pavilion 15

2019-09-13 Thread Greg Kroah-Hartman
From: Sam Bazley commit d33cd42d86671bed870827aa399aeb9f1da74119 upstream. HP Pavilion 15 (AMD Ryzen-based model) with 103c:84e7 needs the same quirk like HP Envy/Spectre x360 for enabling the mute LED over Mic3 pin. [ rearranged in the SSID number order by tiwai ] Signed-off-by: Sam Bazley C

[PATCH 4.19 010/190] powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction

2019-09-13 Thread Greg Kroah-Hartman
From: Gustavo Romero commit 8205d5d98ef7f155de211f5e2eb6ca03d95a5a60 upstream. When we take an FP unavailable exception in a transaction we have to account for the hardware FP TM checkpointed registers being incorrect. In this case for this process we know the current and checkpointed FP registe

<    2   3   4   5   6   7   8   9   10   >