[PATCH 5.10 645/663] dm writecache: fix performance degradation in ssd mode

2021-03-01 Thread Greg Kroah-Hartman
From: Mikulas Patocka commit cb728484a7710c202f02b96aa0962ce9b07aa5c2 upstream. Fix a thinko in ssd_commit_superblock. region.count is in sectors, not bytes. This bug doesn't corrupt data, but it causes performance degradation. Signed-off-by: Mikulas Patocka Fixes: dc8a01ae1dbd ("dm

[PATCH 5.10 412/663] drm/msm: Fix races managing the OOB state for timestamp vs timestamps.

2021-03-01 Thread Greg Kroah-Hartman
From: Eric Anholt [ Upstream commit 5f98b33b04c02c0d9088c7486c59d058696782f9 ] Now that we're not racing with GPU setup, also fix races of timestamps against other timestamps. In freedreno CI, we were seeing this path trigger timeouts on setting the GMU bit, producing: [drm:_a6xx_gmu_set_oob]

[PATCH 5.10 642/663] dm table: fix iterate_devices based device capability checks

2021-03-01 Thread Greg Kroah-Hartman
From: Jeffle Xu commit a4c8dd9c2d0987cf542a2a0c42684c9c6d78a04e upstream. According to the definition of dm_iterate_devices_fn: * This function must iterate through each section of device used by the * target until it encounters a non-zero return code, which it then returns. * Returns zero

[PATCH 5.11 377/775] watchdog: intel-mid_wdt: Postpone IRQ handler registration till SCU is ready

2021-03-01 Thread Greg Kroah-Hartman
From: Andy Shevchenko [ Upstream commit f285c9532b5bd3de7e37a6203318437cab79bd9a ] When SCU is not ready and CONFIG_DEBUG_SHIRQ=y we got deferred probe followed by fired test IRQ which immediately makes kernel panic. Fix this by delaying IRQ handler registration till SCU is ready. Fixes:

[PATCH 5.11 169/775] drm/gma500: Fix error return code in psb_driver_load()

2021-03-01 Thread Greg Kroah-Hartman
From: Jialin Zhang [ Upstream commit 6926872ae24452d4f2176a3ba2dee659497de2c4 ] Fix to return a negative error code from the error handling case instead of 0, as done elsewhere in this function. Fixes: 5c49fd3aa0ab ("gma500: Add the core DRM files and headers") Reported-by: Hulk Robot

[PATCH 5.11 163/775] net/mlx5e: Fix CQ params of ICOSQ and async ICOSQ

2021-03-01 Thread Greg Kroah-Hartman
From: Maxim Mikityanskiy [ Upstream commit ebf79b6be67c0a77a9ab7cdf74c43fd7d9619f0c ] The commit mentioned below has split the parameters of ICOSQ and async ICOSQ, but it contained a typo: the CQ parameters were swapped for ICOSQ and async ICOSQ. Async ICOSQ is longer than the normal ICOSQ, and

[PATCH 5.10 162/663] media: imx: Fix csc/scaler unregister

2021-03-01 Thread Greg Kroah-Hartman
From: Ezequiel Garcia [ Upstream commit 89b14485caa4b7b2eaf70be0064f0978e68ebeee ] The csc/scaler device private struct is released by ipu_csc_scaler_video_device_release(), which can be called by video_unregister_device() if there are no users of the underlying struct video device. Therefore,

[PATCH 5.10 108/663] net/mlx5: Disable devlink reload for multi port slave device

2021-03-01 Thread Greg Kroah-Hartman
From: Shay Drory [ Upstream commit d89ddaae1766f8fe571ea6eb63ec098ff556f1dd ] Devlink reload can't be allowed on a multi port slave device, because reload of slave device doesn't take effect. The right flow is to disable devlink reload for multi port slave device. Hence, disabling it in

[PATCH 5.10 368/663] regulator: bd718x7, bd71828, Fix dvs voltage levels

2021-03-01 Thread Greg Kroah-Hartman
From: Matti Vaittinen [ Upstream commit c294554111a835598b557db789d9ad2379b512a2 ] The ROHM BD718x7 and BD71828 drivers support setting HW state specific voltages from device-tree. This is used also by various in-tree DTS files. These drivers do incorrectly try to compose bit-map using enum

[PATCH 5.11 159/775] Bluetooth: hci_qca: Fixed issue during suspend

2021-03-01 Thread Greg Kroah-Hartman
From: Venkata Lakshmi Narayana Gubba [ Upstream commit 55c0bd77479b60ea29fd390faf4545cfb3a1d79e ] If BT SoC is running with ROM FW then just return in qca_suspend function as ROM FW does not support in-band sleep. Fixes: 2be43abac5a8 ("Bluetooth: hci_qca: Wait for timeout during suspend")

[PATCH 5.10 606/663] mmc: sdhci-pci-o2micro: Bug fix for SDR104 HW tuning failure

2021-03-01 Thread Greg Kroah-Hartman
From: Shirley Her commit 1ad9f88014ae1d5abccb6fe930bc4c5c311bdc05 upstream. Force chip enter L0 power state during SDR104 HW tuning to avoid tuning failure Signed-off-by: Shirley Her Link: https://lore.kernel.org/r/20210206014051.3418-1-shirley@bayhubtech.com Fixes: 7b7d897e8898 ("mmc:

[PATCH 5.10 635/663] spi: fsl: invert spisel_boot signal on MPC8309

2021-03-01 Thread Greg Kroah-Hartman
From: Rasmus Villemoes commit 9d2aa6dbf87af89c13cac2d1b4cccad83fb14a7e upstream. Commit 7a2da5d7960a ("spi: fsl: Fix driver breakage when SPI_CS_HIGH is not set in spi->mode") broke our MPC8309 board by effectively inverting the boolean value passed to fsl_spi_cs_control. The SPISEL_BOOT signal

[PATCH 5.11 010/775] PCI: qcom: Use PHY_REFCLK_USE_PAD only for ipq8064

2021-03-01 Thread Greg Kroah-Hartman
From: Ansuel Smith commit 2cfef1971aea6119ee27429181d6cb3383031ac2 upstream. The use of PHY_REFCLK_USE_PAD introduced a regression for apq8064 devices. It was tested that while apq doesn't require the padding, ipq SoC must use it or the kernel hangs on boot. Link:

[PATCH 5.11 226/775] media: atomisp: Fix a buffer overflow in debug code

2021-03-01 Thread Greg Kroah-Hartman
From: Dan Carpenter [ Upstream commit 625993166b551d633917ca35d4afb7b46d7451b4 ] The "pad" variable is a user controlled string and we haven't properly clamped it at this point so the debug code could print from beyond the of the array. Fixes: a49d25364dfb ("staging/atomisp: Add support for

[PATCH 5.10 655/663] drm/i915: Reject 446-480MHz HDMI clock on GLK

2021-03-01 Thread Greg Kroah-Hartman
From: Ville Syrjälä commit 7a6c6243b44a439bda4bf099032be35ebcf53406 upstream. The BXT/GLK DPLL can't generate certain frequencies. We already reject the 233-240MHz range on both. But on GLK the DPLL max frequency was bumped from 300MHz to 594MHz, so now we get to also worry about the 446-480MHz

[PATCH 5.10 566/663] media: smipcie: fix interrupt handling and IR timeout

2021-03-01 Thread Greg Kroah-Hartman
From: Sean Young commit 6532923237b427ed30cc7b4486f6f1ccdee3c647 upstream. After the first IR message, interrupts are no longer received. In addition, the code generates a timeout IR message of 10ms but sets the timeout value to 100ms, so no timeout was ever generated. Link:

[PATCH 5.10 483/663] cpufreq: ACPI: Set cpuinfo.max_freq directly if max boost is known

2021-03-01 Thread Greg Kroah-Hartman
From: Rafael J. Wysocki commit 538b0188da4653b9f4511a114f014354fb6fb7a5 upstream. Commit 3c55e94c0ade ("cpufreq: ACPI: Extend frequency tables to cover boost frequencies") attempted to address a performance issue involving acpi-cpufreq, the schedutil governor and scale-invariance on x86 by

[PATCH 4.19 030/247] ARM: dts: exynos: correct PMIC interrupt trigger level on Spring

2021-03-01 Thread Greg Kroah-Hartman
From: Krzysztof Kozlowski [ Upstream commit 77e6a5467cb8657cf8b5e610a30a4c502085e4f9 ] The Samsung PMIC datasheets describe the interrupt line as active low with a requirement of acknowledge from the CPU. Without specifying the interrupt type in Devicetree, kernel might apply some fixed

[PATCH 5.11 026/775] Bluetooth: Fix initializing response id after clearing struct

2021-03-01 Thread Greg Kroah-Hartman
From: Christopher William Snowhill [ Upstream commit a5687c644015a097304a2e47476c0ecab2065734 ] Looks like this was missed when patching the source to clear the structures throughout, causing this one instance to clear the struct after the response id is assigned. Fixes: eddb7732119d

[PATCH 5.10 639/663] gfs2: Lock imbalance on error path in gfs2_recover_one

2021-03-01 Thread Greg Kroah-Hartman
From: Andreas Gruenbacher commit 834ec3e1ee65029029225a86c12337a6cd385af7 upstream. In gfs2_recover_one, fix a sd_log_flush_lock imbalance when a recovery pass fails. Fixes: c9ebc4b73799 ("gfs2: allow journal replay to hold sd_log_flush_lock") Cc: sta...@vger.kernel.org # v5.7+ Signed-off-by:

[PATCH 5.11 283/775] crypto: ecdh_helper - Ensure len >= secret.len in decode_key()

2021-03-01 Thread Greg Kroah-Hartman
From: Daniele Alessandrelli [ Upstream commit a53ab94eb6850c3657392e2d2ce9b38c387a2633 ] The length ('len' parameter) passed to crypto_ecdh_decode_key() is never checked against the length encoded in the passed buffer ('buf' parameter). This could lead to an out-of-bounds access when the passed

[PATCH 5.10 549/663] soc: samsung: exynos-asv: dont defer early on not-supported SoCs

2021-03-01 Thread Greg Kroah-Hartman
From: Marek Szyprowski commit 0458b88267c637fb872b0359da9ff0b243081e9e upstream. Check if the SoC is really supported before gathering the needed resources. This fixes endless deferred probe on some SoCs other than Exynos5422 (like Exynos5410). Fixes: 5ea428595cc5 ("soc: samsung: Add Exynos

[PATCH 5.10 208/663] ASoC: cpcap: fix microphone timeslot mask

2021-03-01 Thread Greg Kroah-Hartman
From: Sebastian Reichel [ Upstream commit de5bfae2fd962a9da99f56382305ec7966a604b9 ] The correct mask is 0x1f8 (Bit 3-8), but due to missing BIT() 0xf (Bit 0-3) was set instead. This means setting of CPCAP_BIT_MIC1_RX_TIMESLOT0 (Bit 3) still worked (part of both masks). On the other hand the

[PATCH 5.10 097/663] ibmvnic: Set to CLOSED state even on error

2021-03-01 Thread Greg Kroah-Hartman
From: Sukadev Bhattiprolu [ Upstream commit d4083d3c00f60a09ad82e3bf17ff57fec69c8aa6 ] If set_link_state() fails for any reason, we still cleanup the adapter state and cannot recover from a partial close anyway. So set the adapter to CLOSED state. That way if a new soft/hard reset is processed,

[PATCH 5.10 200/663] perf/arm-cmn: Fix PMU instance naming

2021-03-01 Thread Greg Kroah-Hartman
From: Robin Murphy [ Upstream commit 79d7c3dca99fa96033695ddf5d495b775a3a137b ] Although it's neat to avoid the suffix for the typical case of a single PMU, it means systems with multiple CMN instances end up with inconsistent naming. I think it also breaks perf tool's "uncore alias" logic if

[PATCH 5.11 121/775] bpf: Fix bpf_fib_lookup helper MTU check for SKB ctx

2021-03-01 Thread Greg Kroah-Hartman
From: Jesper Dangaard Brouer [ Upstream commit 2c0a10af688c02adcf127aad29e923e0056c6b69 ] BPF end-user on Cilium slack-channel (Carlo Carraro) wants to use bpf_fib_lookup for doing MTU-check, but *prior* to extending packet size, by adjusting fib_params 'tot_len' with the packet length plus the

[PATCH 5.10 246/663] ima: Free IMA measurement buffer on error

2021-03-01 Thread Greg Kroah-Hartman
From: Lakshmi Ramasubramanian [ Upstream commit 6d14c6517885fa68524238787420511b87d671df ] IMA allocates kernel virtual memory to carry forward the measurement list, from the current kernel to the next kernel on kexec system call, in ima_add_kexec_buffer() function. In error code paths this

[PATCH 5.10 442/663] octeontx2-af: Fix an off by one in rvu_dbg_qsize_write()

2021-03-01 Thread Greg Kroah-Hartman
From: Dan Carpenter [ Upstream commit 3a2eb515d1367c0f667b76089a6e727279c688b8 ] This code does not allocate enough memory for the NUL terminator so it ends up putting it one character beyond the end of the buffer. Fixes: 8756828a8148 ("octeontx2-af: Add NPA aura and pool contexts to debugfs")

Re: [GIT PULL] Kmap conversions for 5.12, take 2

2021-03-01 Thread Linus Torvalds
On Mon, Mar 1, 2021 at 8:52 AM David Sterba wrote: > > Ira Weiny (6): > mm/highmem: Lift memcpy_[to|from]_page to core > mm/highmem: Convert memcpy_[to|from]_page() to kmap_local_page() > mm/highmem: Introduce memcpy_page(), memmove_page(), and memset_page() > mm/highmem:

[PATCH 5.11 257/775] KVM: nSVM: Dont strip hosts C-bit from guests CR3 when reading PDPTRs

2021-03-01 Thread Greg Kroah-Hartman
From: Sean Christopherson [ Upstream commit 2732be90235347a3be4babdc9f88a1ea93970b0b ] Don't clear the SME C-bit when reading a guest PDPTR, as the GPA (CR3) is in the guest domain. Barring a bizarre paravirtual use case, this is likely a benign bug. SME is not emulated by KVM, loading SEV

[PATCH 5.10 438/663] i40e: Fix VFs not created

2021-03-01 Thread Greg Kroah-Hartman
From: Sylwester Dziedziuch [ Upstream commit dc8812626440fa6a27f1f3f654f6dc435e042e42 ] When creating VFs they were sometimes not getting resources. It was caused by not executing i40e_reset_all_vfs due to flag __I40E_VF_DISABLE being set on PF. Because of this IAVF was never able to finish

[PATCH 5.10 037/663] staging: vchiq: Fix bulk userdata handling

2021-03-01 Thread Greg Kroah-Hartman
From: Phil Elwell [ Upstream commit 96ae327678eceabf455b11a88ba14ad540d4b046 ] The addition of the local 'userdata' pointer to vchiq_irq_queue_bulk_tx_rx omitted the case where neither BLOCKING nor WAITING modes are used, in which case the value provided by the caller is not returned to them as

[PATCH 5.10 177/663] media: imx7: csi: Fix pad link validation

2021-03-01 Thread Greg Kroah-Hartman
From: Rui Miguel Silva [ Upstream commit f5ffb81f51376eb5a12e8c4cb4871426c65bb2af ] We can not make the assumption that the bound subdev is always a CSI mux, in i.MX6UL/i.MX6ULL that is not the case. So, just get the entity selected by source directly upstream from the CSI. Fixes: 86e02d07871c

[PATCH 5.11 052/775] cpufreq: brcmstb-avs-cpufreq: Free resources in error path

2021-03-01 Thread Greg Kroah-Hartman
From: Christophe JAILLET [ Upstream commit 05f456286fd489558c72a4711d22a5612c965685 ] If 'cpufreq_register_driver()' fails, we must release the resources allocated in 'brcm_avs_prepare_init()' as already done in the remove function. To do that, introduce a new function

[PATCH 5.10 031/663] ARM: dts: exynos: correct PMIC interrupt trigger level on Arndale Octa

2021-03-01 Thread Greg Kroah-Hartman
From: Krzysztof Kozlowski [ Upstream commit 1ac8893c4fa3d4a34915dc5cdab568a39db5086c ] The Samsung PMIC datasheets describe the interrupt line as active low with a requirement of acknowledge from the CPU. The falling edge interrupt will mostly work but it's not correct. Fixes: 1fed2252713e

[PATCH 4.19 033/247] arm64: dts: exynos: correct PMIC interrupt trigger level on TM2

2021-03-01 Thread Greg Kroah-Hartman
From: Krzysztof Kozlowski [ Upstream commit e98e2367dfb4b6d7a80c8ce795c644124eff5f36 ] The Samsung PMIC datasheets describe the interrupt line as active low with a requirement of acknowledge from the CPU. Without specifying the interrupt type in Devicetree, kernel might apply some fixed

[PATCH 5.10 121/663] net: axienet: Handle deferred probe on clock properly

2021-03-01 Thread Greg Kroah-Hartman
From: Robert Hancock [ Upstream commit 57baf8cc70ea4cf5503c9d42f31f6a86d7f5ff1a ] This driver is set up to use a clock mapping in the device tree if it is present, but still work without one for backward compatibility. However, if getting the clock returns -EPROBE_DEFER, then we need to abort

[PATCH 5.10 259/663] power: supply: cpcap: Add missing IRQF_ONESHOT to fix regression

2021-03-01 Thread Greg Kroah-Hartman
From: Tony Lindgren [ Upstream commit e62333e26be649bfc3c167b9f2bbca38b92332c5 ] Commit 25d76fed7ffe ("phy: cpcap-usb: Use IRQF_ONESHOT") started causing errors loading phy-cpcap-usb driver: cpcap_battery cpcap_battery.0: failed to register power supply genirq: Flags mismatch irq 211. 2080

[PATCH 5.10 168/663] media: tm6000: Fix memleak in tm6000_start_stream

2021-03-01 Thread Greg Kroah-Hartman
From: Dinghao Liu [ Upstream commit 76aaf8a96771c16365b8510f1fb97738dc88026e ] When usb_clear_halt() fails, dvb->bulk_urb->transfer_buffer and dvb->bulk_urb should be freed just like when usb_submit_urb() fails. Fixes: 3169c9b26fffa ("V4L/DVB (12788): tm6000: Add initial DVB-T support")

[PATCH 5.10 277/663] dmaengine: fsldma: Fix a resource leak in an error handling path of the probe function

2021-03-01 Thread Greg Kroah-Hartman
From: Christophe JAILLET [ Upstream commit b202d4e82531a62a33a6b14d321dd2aad491578e ] In case of error, the previous 'fsl_dma_chan_probe()' calls must be undone by some 'fsl_dma_chan_remove()', as already done in the remove function. It was added in the remove function in commit 77cd62e8082b

[PATCH 5.10 494/663] usb: dwc3: gadget: Fix dep->interval for fullspeed interrupt

2021-03-01 Thread Greg Kroah-Hartman
From: Thinh Nguyen commit 4b049f55ed95cd889bcdb3034fd75e1f01852b38 upstream. The dep->interval captures the number of frames/microframes per interval from bInterval. Fullspeed interrupt endpoint bInterval is the number of frames per interval and not 2^(bInterval - 1). So fix it here. This

[PATCH 5.10 387/663] perf intel-pt: Fix IPC with CYC threshold

2021-03-01 Thread Greg Kroah-Hartman
From: Adrian Hunter [ Upstream commit 6af4b60033e0ce0332fcdf256c965ad41942821a ] The code assumed every CYC-eligible packet has a CYC packet, which is not the case when CYC thresholds are used. Fix by checking if a CYC packet is actually present in that case. Fixes: 5b1dc0fd1da06 ("perf

[PATCH 5.10 224/663] ASoC: SOF: debug: Fix a potential issue on string buffer termination

2021-03-01 Thread Greg Kroah-Hartman
From: Hui Wang [ Upstream commit 9037c3bde65d339017ef41d81cb58069ffc321d4 ] The function simple_write_to_buffer() doesn't add string termination at the end of buf, we need to handle it on our own. This change refers to the function tokenize_input() in debug.c and the function

[PATCH 5.10 063/663] usb: dwc2: Do not update data length if it is 0 on inbound transfers

2021-03-01 Thread Greg Kroah-Hartman
From: Guenter Roeck [ Upstream commit 415fa1c7305dedbb345e2cc8ac91769bc1c83f1a ] The DWC2 documentation states that transfers with zero data length should set the number of packets to 1 and the transfer length to 0. This is not currently the case for inbound transfers: the transfer length is

[PATCH 5.10 633/663] f2fs: flush data when enabling checkpoint back

2021-03-01 Thread Greg Kroah-Hartman
From: Jaegeuk Kim commit b0ff4fe746fd028eef920ddc8c7b0361c1ede6ec upstream. During checkpoint=disable period, f2fs bypasses all the synchronous IOs such as sync and fsync. So, when enabling it back, we must flush all of them in order to keep the data persistent. Otherwise, suddern power-cut

[PATCH 5.11 327/775] rtc: rx6110: fix build against modular I2C

2021-03-01 Thread Greg Kroah-Hartman
From: Arnd Bergmann [ Upstream commit def8550f543e6c9101f3e1a03160b2aab8c02e8a ] With CONFIG_I2C=m, the #ifdef section is disabled, as shown by this warning: drivers/rtc/rtc-rx6110.c:314:12: error: unused function 'rx6110_probe' [-Werror,-Wunused-function] Change the driver to use

[PATCH 5.10 006/663] scsi: qla2xxx: Fix mailbox Ch erroneous error

2021-03-01 Thread Greg Kroah-Hartman
From: Quinn Tran commit 044c218b04503858ca4e17f61899c8baa0ae9ba1 upstream. Mailbox Ch/dump ram extend expects mb register 10 to be set. If not set/clear, firmware can pick up garbage from previous invocation of this mailbox. Example: mctp dump can set mb10. On subsequent flash read which use

[PATCH 5.10 231/663] drm/vc4: hdmi: Fix up CEC registers

2021-03-01 Thread Greg Kroah-Hartman
From: Dom Cobley [ Upstream commit 5a32bfd563e8b5766e57475c2c81c769e5a13f5d ] The commit 311e305fdb4e ("drm/vc4: hdmi: Implement a register layout abstraction") forgot one CEC register, and made a copy and paste mistake for another one. Fix those mistakes. Fixes: 311e305fdb4e ("drm/vc4: hdmi:

[PATCH 5.11 114/775] net/mlx5: Disable devlink reload for lag devices

2021-03-01 Thread Greg Kroah-Hartman
From: Shay Drory [ Upstream commit edac23c2b3d3ac64cfcd351087295893671adbf5 ] Devlink reload can't be allowed on lag devices since reloading one lag device will cause traffic on the bond to get stucked. Users who wish to reload a lag device, need to remove the device from the bond, and only

[PATCH 5.10 144/663] crypto: sun4i-ss - linearize buffers content must be kept

2021-03-01 Thread Greg Kroah-Hartman
From: Corentin Labbe [ Upstream commit 583513510a7acd2306787865bcd19ebb2f629d42 ] When running the non-optimized cipher function, SS produce partial random output. This is due to linearize buffers being reseted after each loop. For preserving stack, instead of moving them back to start of

[PATCH 5.10 041/663] bpf: Add bpf_patch_call_args prototype to include/linux/bpf.h

2021-03-01 Thread Greg Kroah-Hartman
From: Andrii Nakryiko [ Upstream commit a643bff752dcf72a07e1b2ab2f8587e4f51118be ] Add bpf_patch_call_args() prototype. This function is called from BPF verifier and only if CONFIG_BPF_JIT_ALWAYS_ON is not defined. This fixes compiler warning about missing prototype in some kernel

[PATCH 5.10 174/663] sched/fair: Avoid stale CPU util_est value for schedutil in task dequeue

2021-03-01 Thread Greg Kroah-Hartman
From: Xuewen Yan [ Upstream commit 8c1f560c1ea3f19e22ba356f62680d9d449c9ec2 ] CPU (root cfs_rq) estimated utilization (util_est) is currently used in dequeue_task_fair() to drive frequency selection before it is updated. with: CPU_util: rq->cfs.avg.util_avg CPU_util_est:

[PATCH 5.10 059/663] Bluetooth: drop HCI device reference before return

2021-03-01 Thread Greg Kroah-Hartman
From: Pan Bian [ Upstream commit 5a3ef03afe7e12982dc3b978f4c5077c907f7501 ] Call hci_dev_put() to decrement reference count of HCI device hdev if fails to duplicate memory. Fixes: 0b26ab9dce74 ("Bluetooth: AMP: Handle Accept phylink command status evt") Signed-off-by: Pan Bian Signed-off-by:

[PATCH 5.11 340/775] RDMA/rtrs-srv: Use sysfs_remove_file_self for disconnect

2021-03-01 Thread Greg Kroah-Hartman
From: Jack Wang [ Upstream commit f991fdac813f1598a9bb17b602ce04812ba9148c ] Remove self first to avoid deadlock, we don't want to use close_work to remove sess sysfs. Fixes: 91b11610af8d ("RDMA/rtrs: server: sysfs interface functions") Link:

[PATCH 5.11 329/775] dmaengine: ti: k3-udma: Set rflow count for BCDMA split channels

2021-03-01 Thread Greg Kroah-Hartman
From: Vignesh Raghavendra [ Upstream commit aecf9d38361090857aa58708e500ee79bed1e273 ] BCDMA RX channels have one flow per channel, therefore set the rflow_cnt to rchan_cnt. Without this patch, request for BCDMA RX channel allocation fails as rflow_cnt is 0 thus fails to reserve a rflow for

[PATCH 5.10 109/663] net/mlx5: Disallow RoCE on multi port slave device

2021-03-01 Thread Greg Kroah-Hartman
From: Shay Drory [ Upstream commit c70f8597fcc1399ef6d5b5ce648a31d887d5dba2 ] In dual port mode, setting roce enabled/disable for the slave device have no effect. e.g.: the slave device roce status remain unchanged. Therefore disable it and add an error message. Enable or disable roce of the

[PATCH 5.10 054/663] usb: gadget: u_audio: Free requests only after callback

2021-03-01 Thread Greg Kroah-Hartman
From: Jack Pham [ Upstream commit 7de8681be2cde9f6953d3be1fa6ce05f9fe6e637 ] As per the kernel doc for usb_ep_dequeue(), it states that "this routine is asynchronous, that is, it may return before the completion routine runs". And indeed since v5.0 the dwc3 gadget driver updated its behavior to

[PATCH 5.11 219/775] bsg: free the request before return error code

2021-03-01 Thread Greg Kroah-Hartman
From: Pan Bian [ Upstream commit 0f7b4bc6bb1e57c48ef14f1818df947c1612b206 ] Free the request rq before returning error code. Fixes: 972248e9111e ("scsi: bsg-lib: handle bidi requests without block layer help") Signed-off-by: Pan Bian Reviewed-by: Christoph Hellwig Signed-off-by: Jens Axboe

[PATCH 5.11 251/775] mtd: parsers: afs: Fix freeing the part name memory in failure

2021-03-01 Thread Greg Kroah-Hartman
From: Manivannan Sadhasivam [ Upstream commit 7b844cf445f0a7daa68be0ce71eb2c88d68b0c5d ] In the case of failure while parsing the partitions, the iterator should be pre decremented by one before starting to free the memory allocated by kstrdup(). Because in the failure case, kstrdup() will not

[PATCH 5.11 039/775] staging: vchiq: Fix bulk userdata handling

2021-03-01 Thread Greg Kroah-Hartman
From: Phil Elwell [ Upstream commit 96ae327678eceabf455b11a88ba14ad540d4b046 ] The addition of the local 'userdata' pointer to vchiq_irq_queue_bulk_tx_rx omitted the case where neither BLOCKING nor WAITING modes are used, in which case the value provided by the caller is not returned to them as

[PATCH 5.11 235/775] sched/eas: Dont update misfit status if the task is pinned

2021-03-01 Thread Greg Kroah-Hartman
From: Qais Yousef [ Upstream commit 0ae78eec8aa64e645866e75005162603a77a0f49 ] If the task is pinned to a cpu, setting the misfit status means that we'll unnecessarily continuously attempt to migrate the task but fail. This continuous failure will cause the balance_interval to increase to a

[PATCH 5.10 124/663] bpf: Clear subreg_def for global function return values

2021-03-01 Thread Greg Kroah-Hartman
From: Ilya Leoshkevich [ Upstream commit 45159b27637b0fef6d5ddb86fc7c46b13c77960f ] test_global_func4 fails on s390 as reported by Yauheni in [1]. The immediate problem is that the zext code includes the instruction, whose result needs to be zero-extended, into the zero-extension patchlet, and

[PATCH 5.11 030/775] ARM: dts: exynos: correct PMIC interrupt trigger level on Monk

2021-03-01 Thread Greg Kroah-Hartman
From: Krzysztof Kozlowski [ Upstream commit 8528cda2b7c667e9cd173aef1a677c71b7d5a096 ] The Samsung PMIC datasheets describe the interrupt line as active low with a requirement of acknowledge from the CPU. Without specifying the interrupt type in Devicetree, kernel might apply some fixed

[PATCH 5.10 444/663] vfio/type1: Use follow_pte()

2021-03-01 Thread Greg Kroah-Hartman
From: Alex Williamson [ Upstream commit 07956b6269d3ed05d854233d5bb776dca91751dd ] follow_pfn() doesn't make sure that we're using the correct page protections, get the pte with follow_pte() so that we can test protections and get the pfn from the pte. Fixes: 5cbf3264bc71 ("vfio/type1: Fix

[PATCH 5.11 328/775] dmaengine: qcom: Always inline gpi_update_reg

2021-03-01 Thread Greg Kroah-Hartman
From: Nathan Chancellor [ Upstream commit 0a6d3038d914b51d6860f23ea2b508590e8340de ] When building with CONFIG_UBSAN_UNSIGNED_OVERFLOW, clang decides not to inline gpi_update_reg, which causes a linkage failure around __bad_mask: ld.lld: error: undefined symbol: __bad_mask >>> referenced by

[PATCH 5.10 531/663] btrfs: do not cleanup upper nodes in btrfs_backref_cleanup_node

2021-03-01 Thread Greg Kroah-Hartman
From: Josef Bacik commit 7e2a870a599d4699a626ec26430c7a1ab14a2a49 upstream. Zygo reported the following panic when testing my error handling patches for relocation: kernel BUG at fs/btrfs/backref.c:2545! invalid opcode: [#1] SMP KASAN PTI CPU: 3 PID: 8472 Comm: btrfs Tainted: G

[PATCH 5.10 196/663] sched/eas: Dont update misfit status if the task is pinned

2021-03-01 Thread Greg Kroah-Hartman
From: Qais Yousef [ Upstream commit 0ae78eec8aa64e645866e75005162603a77a0f49 ] If the task is pinned to a cpu, setting the misfit status means that we'll unnecessarily continuously attempt to migrate the task but fail. This continuous failure will cause the balance_interval to increase to a

[PATCH 5.10 395/663] phy: rockchip-emmc: emmc_phy_init() always return 0

2021-03-01 Thread Greg Kroah-Hartman
From: Chris Ruehl [ Upstream commit 39961bd6b70e5a5d7c4b5483ad8e1db6b5765c60 ] rockchip_emmc_phy_init() return variable is not set with the error value if clk_get() failed. 'emmcclk' is optional, thus use clk_get_optional() and if the return value != NULL make error processing and set the

[PATCH 5.11 243/775] crypto: talitos - Work around SEC6 ERRATA (AES-CTR mode data size error)

2021-03-01 Thread Greg Kroah-Hartman
From: Christophe Leroy [ Upstream commit 416b846757bcea20006a9197e67ba3a8b5b2a680 ] Talitos Security Engine AESU considers any input data size that is not a multiple of 16 bytes to be an error. This is not a problem in general, except for Counter mode that is a stream cipher and can have an

[PATCH 5.10 217/663] drm/mediatek: Fix aal size config

2021-03-01 Thread Greg Kroah-Hartman
[ Upstream commit 71dcadba34203d8dd35152e368720f977e9cdb81 ] The orginal setting is not correct, fix it to follow hardware data sheet. If keep this error setting, mt8173/mt8183 display ok but mt8192 display abnormal. Fixes: 0664d1392c26 ("drm/mediatek: Add AAL engine basic function")

[PATCH 5.11 216/775] MIPS: Compare __SYNC_loongson3_war against 0

2021-03-01 Thread Greg Kroah-Hartman
From: Nathan Chancellor [ Upstream commit 8790ccf8daf1a8c53b6cb8ce0c9a109274bd3fa8 ] When building with clang when CONFIG_CPU_LOONGSON3_WORKAROUNDS is enabled: In file included from lib/errseq.c:4: In file included from ./include/linux/atomic.h:7: ./arch/mips/include/asm/atomic.h:52:1:

[PATCH 5.10 326/663] powerpc/47x: Disable 256k page size

2021-03-01 Thread Greg Kroah-Hartman
From: Christophe Leroy [ Upstream commit 910a0cb6d259736a0c86e795d4c2f42af8d0d775 ] PPC47x_TLBE_SIZE isn't defined for 256k pages, leading to a build break if 256k pages is selected. So change the kconfig so that 256k pages can't be selected for 47x. Fixes: e7f75ad01d59 ("powerpc/47x: Base

[PATCH 5.10 074/663] Bluetooth: btusb: Fix memory leak in btusb_mtk_wmt_recv

2021-03-01 Thread Greg Kroah-Hartman
From: Jupeng Zhong [ Upstream commit de71a6cb4bf24d8993b9ca90d1ddb131b60251a1 ] In btusb_mtk_wmt_recv if skb_clone fails, the alocated skb should be released. Omit the labels “err_out” and “err_free_skb” in this function implementation so that the desired exception handling code would be

[PATCH 5.11 069/775] x86/MSR: Filter MSR writes through X86_IOC_WRMSR_REGS ioctl too

2021-03-01 Thread Greg Kroah-Hartman
From: Misono Tomohiro [ Upstream commit 02a16aa13574c8526beadfc9ae8cc9b66315fa2d ] Commit a7e1f67ed29f ("x86/msr: Filter MSR writes") introduced a module parameter to disable writing to the MSR device file and tainted the kernel upon writing. As MSR registers can be written by the

[PATCH 5.11 033/775] ARM: dts: exynos: correct PMIC interrupt trigger level on Arndale Octa

2021-03-01 Thread Greg Kroah-Hartman
From: Krzysztof Kozlowski [ Upstream commit 1ac8893c4fa3d4a34915dc5cdab568a39db5086c ] The Samsung PMIC datasheets describe the interrupt line as active low with a requirement of acknowledge from the CPU. The falling edge interrupt will mostly work but it's not correct. Fixes: 1fed2252713e

[PATCH 5.11 146/775] arm64: dts: qcom: sm8250: correct sdhc_2 xo clk

2021-03-01 Thread Greg Kroah-Hartman
From: Dmitry Baryshkov [ Upstream commit 74097d805edb9305a2a588a8ece82d2495ff5a88 ] sdhc_2 uses 1920 Hz clock rather than wrongly specified xo_board (3940 Hz). Specify correct clock to fix DLL setup for SDR104 mode. Signed-off-by: Dmitry Baryshkov Fixes: c4cf0300be84 ("arm64: dts:

[PATCH 5.10 497/663] USB: serial: mos7840: fix error code in mos7840_write()

2021-03-01 Thread Greg Kroah-Hartman
From: Dan Carpenter commit a70aa7dc60099bbdcbd6faca42a915d80f31161e upstream. This should return -ENOMEM instead of 0 if the kmalloc() fails. Fixes: 3f5429746d91 ("USB: Moschip 7840 USB-Serial Driver") Signed-off-by: Dan Carpenter Cc: sta...@vger.kernel.org Signed-off-by: Johan Hovold

[PATCH 5.11 058/775] soc: qcom: socinfo: Fix an off by one in qcom_show_pmic_model()

2021-03-01 Thread Greg Kroah-Hartman
From: Dan Carpenter [ Upstream commit 5fb33d8960dc7abdabc6fe599a30c2c99b082ef6 ] These need to be < ARRAY_SIZE() instead of <= ARRAY_SIZE() to prevent accessing one element beyond the end of the array. Acked-by: Dmitry Baryshkov Reviewed-by: Douglas Anderson Reviewed-by: Stephen Boyd Fixes:

[PATCH 5.4 316/340] um: mm: check more comprehensively for stub changes

2021-03-01 Thread Greg Kroah-Hartman
From: Johannes Berg commit 47da29763ec9a153b9b685bff9db659e4e09e494 upstream. If userspace tries to change the stub, we need to kill it, because otherwise it can escape the virtual machine. In a few cases the stub checks weren't good, e.g. if userspace just tries to mmap(0x10 -

[PATCH 5.4 263/340] tpm_tis: Clean up locality release

2021-03-01 Thread Greg Kroah-Hartman
From: James Bottomley commit e42acf104d6e0bd7ccd2f09103d5be5e6d3c637c upstream. The current release locality code seems to be based on the misunderstanding that the TPM interrupts when a locality is released: it doesn't, only when the locality is acquired. Furthermore, there seems to be no

[PATCH 5.10 498/663] USB: serial: mos7720: fix error code in mos7720_write()

2021-03-01 Thread Greg Kroah-Hartman
From: Dan Carpenter commit fea7372cbc40869876df0f045e367f6f97a1666c upstream. This code should return -ENOMEM if the kmalloc() fails but instead it returns success. Signed-off-by: Dan Carpenter Fixes: 0f64478cbc7a ("USB: add USB serial mos7720 driver") Cc: sta...@vger.kernel.org

[PATCH 5.11 215/775] MIPS: properly stop .eh_frame generation

2021-03-01 Thread Greg Kroah-Hartman
From: Alexander Lobakin [ Upstream commit 894ef530012fb5078466efdfb2c15d8b2f1565cd ] Commit 866b6a89c6d1 ("MIPS: Add DWARF unwinding to assembly") added -fno-asynchronous-unwind-tables to KBUILD_CFLAGS to prevent compiler from emitting .eh_frame symbols. However, as MIPS heavily uses CFI,

[PATCH 5.10 068/663] arm64: dts: renesas: beacon: Fix EEPROM compatible value

2021-03-01 Thread Greg Kroah-Hartman
From: Geert Uytterhoeven [ Upstream commit 74477936a828a7c91a61ba7e625b7ce2299c8c98 ] "make dtbs_check" fails with: arch/arm64/boot/dts/renesas/r8a774b1-beacon-rzg2n-kit.dt.yaml: eeprom@50: compatible: 'oneOf' conditional failed, one must be fixed: 'microchip,at24c64' does not

[PATCH 5.4 293/340] watchdog: qcom: Remove incorrect usage of QCOM_WDT_ENABLE_IRQ

2021-03-01 Thread Greg Kroah-Hartman
From: Sai Prakash Ranjan commit a4f3407c41605d14f09e490045d0609990cd5d94 upstream. As per register documentation, QCOM_WDT_ENABLE_IRQ which is BIT(1) of watchdog control register is wakeup interrupt enable bit and not related to bark interrupt at all, BIT(0) is used for that. So remove

[PATCH 5.11 229/775] media: mtk-vcodec: fix argument used when DEBUG is defined

2021-03-01 Thread Greg Kroah-Hartman
From: Tom Rix [ Upstream commit a04e187d231086a1313fd635ac42bdbc997137ad ] When DEBUG is defined this error occurs drivers/media/platform/mtk-vcodec/mtk_vcodec_enc_drv.c:306:41: error: ‘i’ undeclared (first use in this function) mtk_v4l2_debug(2, "reg[%d] base=0x%p", i,

[PATCH 5.10 285/663] of/fdt: Make sure no-map does not remove already reserved regions

2021-03-01 Thread Greg Kroah-Hartman
From: Nicolas Boichat [ Upstream commit 8a5a75e5e9e55de1cef5d83ca3589cb4899193ef ] If the device tree is incorrectly configured, and attempts to define a "no-map" reserved memory that overlaps with the kernel data/code, the kernel would crash quickly after boot, with no obvious clue about the

[PATCH 5.10 324/663] IB/umad: Return EPOLLERR in case of when device disassociated

2021-03-01 Thread Greg Kroah-Hartman
From: Shay Drory [ Upstream commit def4cd43f522253645b72c97181399c241b54536 ] Currently, polling a umad device will always works, even if the device was disassociated. A disassociated device should immediately return EPOLLERR from poll(). Otherwise userspace is endlessly hung on poll() with no

[PATCH 5.4 290/340] floppy: reintroduce O_NDELAY fix

2021-03-01 Thread Greg Kroah-Hartman
From: Jiri Kosina commit 8a0c014cd20516ade9654fc13b51345ec58e7be8 upstream. This issue was originally fixed in 09954bad4 ("floppy: refactor open() flags handling"). The fix as a side-effect, however, introduce issue for open(O_ACCMODE) that is being used for ioctl-only open. I wrote a fix for

[PATCH 5.10 095/663] ath9k: fix data bus crash when setting nf_override via debugfs

2021-03-01 Thread Greg Kroah-Hartman
From: Linus Lüssing [ Upstream commit 12c8f3d1cdd84f01ee777b756db9dddc1f1c9d17 ] When trying to set the noise floor via debugfs, a "data bus error" crash like the following can happen: [ 88.433133] Data bus error, epc == 80221c28, ra == 83314e60 [ 88.438895] Oops[#1]: [ 88.441246] CPU: 0

[PATCH 5.10 660/663] wireguard: queueing: get rid of per-peer ring buffers

2021-03-01 Thread Greg Kroah-Hartman
From: Jason A. Donenfeld commit 8b5553ace83cced775eefd0f3f18b5c6214ccf7a upstream. Having two ring buffers per-peer means that every peer results in two massive ring allocations. On an 8-core x86_64 machine, this commit reduces the per-peer allocation from 18,688 bytes to 1,856 bytes, which is

[PATCH 5.10 133/663] net: amd-xgbe: Fix network fluctuations when using 1G BELFUSE SFP

2021-03-01 Thread Greg Kroah-Hartman
From: Shyam Sundar S K [ Upstream commit 9eab3fdb419916f66a72d1572f68d82cd9b3f963 ] Frequent link up/down events can happen when a Bel Fuse SFP part is connected to the amd-xgbe device. Try to avoid the frequent link issues by resetting the PHY as documented in Bel Fuse SFP datasheets. Fixes:

[PATCH 4.19 074/247] drm/gma500: Fix error return code in psb_driver_load()

2021-03-01 Thread Greg Kroah-Hartman
From: Jialin Zhang [ Upstream commit 6926872ae24452d4f2176a3ba2dee659497de2c4 ] Fix to return a negative error code from the error handling case instead of 0, as done elsewhere in this function. Fixes: 5c49fd3aa0ab ("gma500: Add the core DRM files and headers") Reported-by: Hulk Robot

[PATCH 5.11 386/775] RDMA/mlx5: Allow creating all QPs even when non RDMA profile is used

2021-03-01 Thread Greg Kroah-Hartman
From: Mark Bloch [ Upstream commit 2614488d1f3cd5989375042286b11424208e20c8 ] The cited commit disallowed creating any QP which isn't raw ethernet, reg umr or the special UD qp for testing WC, this proved too strict. While modify can't be done (no GIDS/GID table for example) just creating a QP

[PATCH 5.10 618/663] exfat: fix shift-out-of-bounds in exfat_fill_super()

2021-03-01 Thread Greg Kroah-Hartman
From: Namjae Jeon commit 78c276f5495aa53a8beebb627e5bf6a54f0af34f upstream. syzbot reported a warning which could cause shift-out-of-bounds issue. Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x183/0x22e lib/dump_stack.c:120 ubsan_epilogue lib/ubsan.c:148 [inline]

[PATCH 5.10 519/663] drm/modes: Switch to 64bit maths to avoid integer overflow

2021-03-01 Thread Greg Kroah-Hartman
From: Ville Syrjälä commit 5b34ab52401f0f1f191bcb83a182c83b506f4763 upstream. The new >8k CEA modes have dotclocks reaching 5.94 GHz, which means our clock*1000 will now overflow the 32bit unsigned integer. Switch to 64bit maths to avoid it. Cc: sta...@vger.kernel.org Reported-by: Randy Dunlap

[PATCH 5.10 129/663] net: phy: mscc: adding LCPLL reset to VSC8514

2021-03-01 Thread Greg Kroah-Hartman
From: Bjarni Jonasson [ Upstream commit 3cc2c646be0b22037f31c958e96c0544a073d108 ] At Power-On Reset, transients may cause the LCPLL to lock onto a clock that is momentarily unstable. This is normally seen in QSGMII setups where the higher speed 6G SerDes is being used. This patch adds an

[PATCH 5.10 559/663] staging: gdm724x: Fix DMA from stack

2021-03-01 Thread Greg Kroah-Hartman
From: Amey Narkhede commit 7c3a0635cd008eaca9a734dc802709ee0b81cac5 upstream. Stack allocated buffers cannot be used for DMA on all architectures so allocate hci_packet buffer using kmalloc. Reviewed-by: Dan Carpenter Signed-off-by: Amey Narkhede Link:

[PATCH 5.10 471/663] mm/rmap: fix potential pte_unmap on an not mapped pte

2021-03-01 Thread Greg Kroah-Hartman
From: Miaohe Lin [ Upstream commit 5d5d19eda6b0ee790af89c45e3f678345be6f50f ] For PMD-mapped page (usually THP), pvmw->pte is NULL. For PTE-mapped THP, pvmw->pte is mapped. But for HugeTLB pages, pvmw->pte is not mapped and set to the relevant page table entry. So in

[PATCH 5.11 016/775] MIPS: vmlinux.lds.S: add missing PAGE_ALIGNED_DATA() section

2021-03-01 Thread Greg Kroah-Hartman
From: Alexander Lobakin commit 8ac7c87acdcac156670f9920c8acbd84308ff4b1 upstream. MIPS uses its own declaration of rwdata, and thus it should be kept in sync with the asm-generic one. Currently PAGE_ALIGNED_DATA() is missing from the linker script, which emits the following ld warnings:

[PATCH 5.10 624/663] cpufreq: intel_pstate: Get per-CPU max freq via MSR_HWP_CAPABILITIES if available

2021-03-01 Thread Greg Kroah-Hartman
From: Chen Yu commit 6f67e060083a84a4cc364eab6ae40c717165fb0c upstream. Currently, when turbo is disabled (either by BIOS or by the user), the intel_pstate driver reads the max non-turbo frequency from the package-wide MSR_PLATFORM_INFO(0xce) register. However, on asymmetric platforms it is

<    4   5   6   7   8   9   10   11   12   13   >