[PATCH 5.10 419/663] coresight: etm4x: Skip accessing TRCPDCR in save/restore

2021-03-01 Thread Greg Kroah-Hartman
From: Suzuki K Poulose [ Upstream commit df81b43802f43c0954a55e5d513e8750a1ab4d31 ] When the ETM is affected by Qualcomm errata, modifying the TRCPDCR could cause the system hang. Even though this is taken care of during enable/disable ETM, the ETM state save/restore could still access the

[PATCH 5.10 287/663] RDMA/rtrs-srv: Release lock before call into close_sess

2021-03-01 Thread Greg Kroah-Hartman
From: Jack Wang [ Upstream commit 99f0c3807973359bba8f37d9198eea59fe38c32a ] In this error case, we don't need hold mutex to call close_sess. Fixes: 9cb837480424 ("RDMA/rtrs: server: main functionality") Link: https://lore.kernel.org/r/20201217141915.56989-4-jinpu.w...@cloud.ionos.com

[PATCH 5.10 045/663] arm64: dts: allwinner: H6: properly connect USB PHY to port 0

2021-03-01 Thread Greg Kroah-Hartman
From: Andre Przywara [ Upstream commit da2fb8457f71138d455cba82edec0d34f858e506 ] In recent Allwinner SoCs the first USB host controller (HCI0) shares the first PHY with the MUSB controller. Probably to make this sharing work, we were avoiding to declare this in the DT. This has two

[PATCH 5.10 403/663] pwm: rockchip: Eliminate potential race condition when probing

2021-03-01 Thread Greg Kroah-Hartman
From: Simon South [ Upstream commit d21ba5d6217bd5a6a696678385906ed1994b380b ] Commit 48cf973cae33 ("pwm: rockchip: Avoid glitches on already running PWMs") introduced a potential race condition in rockchip_pwm_probe(): A consumer could enable an inactive PWM, or disable a running one, between

[PATCH 5.10 223/663] ASoC: rt5682: Fix panic in rt5682_jack_detect_handler happening during system shutdown

2021-03-01 Thread Greg Kroah-Hartman
From: Sathyanarayana Nujella [ Upstream commit 45a2702ce10993eda7a5b12690294782d565519c ] During Coldboot stress tests, system encountered the following panic. Panic logs depicts rt5682_i2c_shutdown() happened first and then later jack detect handler workqueue function triggered. This situation

[PATCH 5.10 409/663] drm/msm/dsi: Correct io_start for MSM8994 (20nm PHY)

2021-03-01 Thread Greg Kroah-Hartman
From: Konrad Dybcio [ Upstream commit 33a7808ce1aea6e2edc1af25db25928137940c02 ] The previous registers were *almost* correct, but instead of PHYs, they were pointing at DSI PLLs, resulting in the PHY id autodetection failing miserably. Fixes: dcefc117cc19 ("drm/msm/dsi: Add support for

[PATCH 5.10 417/663] ext4: fix potential htree index checksum corruption

2021-03-01 Thread Greg Kroah-Hartman
From: Theodore Ts'o [ Upstream commit b5776e7524afbd4569978ff790864755c438bba7 ] In the case where we need to do an interior node split, and immediately afterwards, we are unable to allocate a new directory leaf block due to ENOSPC, the directory index checksum's will not be filled in correctly

[PATCH 5.10 141/663] drm/fb-helper: Add missed unlocks in setcmap_legacy()

2021-03-01 Thread Greg Kroah-Hartman
From: Chuhong Yuan [ Upstream commit 0a260e731d6c4c17547ac275a2cde888a9eb4a3d ] setcmap_legacy() does not call drm_modeset_unlock_all() in some exits, add the missed unlocks with goto to fix it. Fixes: 964c60063bff ("drm/fb-helper: separate the fb_setcmap helper into atomic and legacy paths")

[PATCH 5.10 293/663] RDMA/rtrs-srv: Init wr_cnt as 1

2021-03-01 Thread Greg Kroah-Hartman
From: Jack Wang [ Upstream commit 6f5d1b3016d650f351e65c645a5eee5394547dd0 ] Fix up wr_avail accounting. if wr_cnt is 0, then we do SIGNAL for first wr, in completion we add queue_depth back, which is not right in the sense of tracking for available wr. So fix it by init wr_cnt to 1. Fixes:

[PATCH 5.10 143/663] drm/vc4: hdmi: Take into account the clock doubling flag in atomic_check

2021-03-01 Thread Greg Kroah-Hartman
From: Maxime Ripard [ Upstream commit 320e84dc6111ecc1c957e2b186d4d2bafee6bde2 ] Commit 63495f6b4aed ("drm/vc4: hdmi: Make sure our clock rate is within limits") was intended to compute the pixel rate to make sure we remain within the boundaries of what the hardware can provide. However,

[PATCH 5.10 258/663] HSI: Fix PM usage counter unbalance in ssi_hw_init

2021-03-01 Thread Greg Kroah-Hartman
From: Zhang Qilong [ Upstream commit aa57e77b3d28f0df07149d88c47bc0f3aa77330b ] pm_runtime_get_sync will increment pm usage counter even it failed. Forgetting to putting operation will result in reference leak here. We fix it by replacing it with pm_runtime_resume_and_get to keep usage counter

[PATCH 4.19 031/247] 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.10 333/663] ARM: 9046/1: decompressor: Do not clear SCTLR.nTLSMD for ARMv7+ cores

2021-03-01 Thread Greg Kroah-Hartman
From: Vladimir Murzin [ Upstream commit 2acb909750431030b65a0a2a17fd8afcbd813a84 ] It was observed that decompressor running on hardware implementing ARM v8.2 Load/Store Multiple Atomicity and Ordering Control (LSMAOC), say, as guest, would stuck just after: Uncompressing Linux... done,

[PATCH 5.10 521/663] drm/panel: kd35t133: allow using non-continuous dsi clock

2021-03-01 Thread Greg Kroah-Hartman
From: Heiko Stuebner commit d922d58fedcd98ba625e89b625a98e222b090b10 upstream. The panel is able to work when dsi clock is non-continuous, thus the system power consumption can be reduced using such feature. Add MIPI_DSI_CLOCK_NON_CONTINUOUS to panel's mode_flags. Also the flag actually

Re: [PATCH 5.10 000/663] 5.10.20-rc1 review

2021-03-01 Thread Holger Hoffstätte
On 2021-03-01 17:04, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 5.10.20 release. Since this is a big update I gave it a try on my two older SandyBridge server/desktop systems and a Lenovo AMD Ryzen7 laptop. Good news: all three still humming along nicely.

[PATCH 5.10 663/663] net_sched: fix RTNL deadlock again caused by request_module()

2021-03-01 Thread Greg Kroah-Hartman
From: Cong Wang commit d349f997686887906b1183b5be96933c5452362a upstream. tcf_action_init_1() loads tc action modules automatically with request_module() after parsing the tc action names, and it drops RTNL lock and re-holds it before and after request_module(). This causes a lot of troubles,

[PATCH 5.10 446/663] ice: Account for port VLAN in VF max packet size calculation

2021-03-01 Thread Greg Kroah-Hartman
From: Brett Creeley [ Upstream commit a6aa7c8f998f4afddd73410aa043dad38162ce9e ] Currently if an AVF driver doesn't account for the possibility of a port VLAN when determining its max packet size then packets at MTU will be dropped. It is not the VF driver's responsibility to account for a port

[PATCH 5.10 180/663] 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.11 179/775] crypto: arm64/aes-ce - really hide slower algos when faster ones are enabled

2021-03-01 Thread Greg Kroah-Hartman
From: Ard Biesheuvel [ Upstream commit 15deb4333cd6d4e1e3216582e4c531ec40a6b060 ] Commit 69b6f2e817e5b ("crypto: arm64/aes-neon - limit exposed routines if faster driver is enabled") intended to hide modes from the plain NEON driver that are also implemented by the faster bit sliced NEON one if

[PATCH 5.10 176/663] media: imx7: csi: Fix regression for parallel cameras on i.MX6UL

2021-03-01 Thread Greg Kroah-Hartman
From: Fabio Estevam [ Upstream commit 9bac67214fbf4b5f23463f7742ccf69bfe684cbd ] Commit 86e02d07871c ("media: imx5/6/7: csi: Mark a bound video mux as a CSI mux") made an incorrect assumption that for imx7-media-csi, the bound subdev must always be a CSI mux. On i.MX6UL/i.MX6ULL there is no CSI

[PATCH 5.10 522/663] drm/rockchip: Require the YTR modifier for AFBC

2021-03-01 Thread Greg Kroah-Hartman
From: Alyssa Rosenzweig commit 5f94e3571459abb626077aedb65d71264c2a58c0 upstream. The AFBC decoder used in the Rockchip VOP assumes the use of the YUV-like colourspace transform (YTR). YTR is lossless for RGB(A) buffers, which covers the RGBA8 and RGB565 formats supported in

[PATCH 5.10 378/663] RDMA/rtrs-srv: Fix stack-out-of-bounds

2021-03-01 Thread Greg Kroah-Hartman
From: Jack Wang [ Upstream commit e6daa8f61d8def10f0619fe51b4c794f69598e4f ] BUG: KASAN: stack-out-of-bounds in _mlx4_ib_post_send+0x1bd2/0x2770 [mlx4_ib] Read of size 4 at addr 8880d5a7f980 by task kworker/0:1H/565 CPU: 0 PID: 565 Comm: kworker/0:1H Tainted: G O

[PATCH 5.11 201/775] media: em28xx: Fix use-after-free in em28xx_alloc_urbs

2021-03-01 Thread Greg Kroah-Hartman
From: Dinghao Liu [ Upstream commit a26efd1961a18b91ae4cd2e433adbcf865b40fa3 ] When kzalloc() fails, em28xx_uninit_usb_xfer() will free usb_bufs->buf and set it to NULL. Thus the later access to usb_bufs->buf[i] will lead to null pointer dereference. Also the kfree(usb_bufs->buf) after that is

[PATCH 5.10 603/663] nvmem: qcom-spmi-sdam: Fix uninitialized pdev pointer

2021-03-01 Thread Greg Kroah-Hartman
From: Subbaraman Narayanamurthy commit e2057ee29973b9741d43d3f475a6b02fb46a0e61 upstream. "sdam->pdev" is uninitialized and it is used to print error logs. Fix it. Since device pointer can be used from sdam_config, use it directly thereby removing pdev pointer. Fixes: 40ce9798794f ("nvmem: add

[PATCH 5.10 093/663] iwlwifi: pnvm: set the PNVM again if it was already loaded

2021-03-01 Thread Greg Kroah-Hartman
From: Luca Coelho [ Upstream commit 4a81598f0f39cffbf1c29c4a184063d513661c4a ] When the interface goes up, we have already loaded the PNVM during init, so we don't load it anymore. But we still need to set the PNVM values in the context so that the FW can load it again. Call set_pnvm when the

[PATCH 5.11 096/775] iwlwifi: pnvm: increment the pointer before checking the TLV

2021-03-01 Thread Greg Kroah-Hartman
From: Luca Coelho [ Upstream commit ff11a8ee2d2d0f78514ac9b42fb50c525ca695c7 ] If the SKU_ID doesn't match, we don't increment the pointer and keep checking the same TLV over and over again. We need to increment the pointer in all situtations, namely if the TLV is not a SKU_ID, if the SKU_ID

[PATCH 5.11 091/775] iwlwifi: mvm: send stored PPAG command instead of local

2021-03-01 Thread Greg Kroah-Hartman
From: Luca Coelho [ Upstream commit 659844d391826bfc5c8b4d9a06869ed51d859c76 ] Some change conflicts apparently cause a confusion between a local variable being used to send the PPAG command and the introduction of a union for this command. Most parts of the local command were never copied

[PATCH 5.11 130/775] ibmvnic: serialize access to work queue on remove

2021-03-01 Thread Greg Kroah-Hartman
From: Sukadev Bhattiprolu [ Upstream commit 4a41c421f3676fdeea91733cf434dcf319c4c351 ] The work queue is used to queue reset requests like CHANGE-PARAM or FAILOVER resets for the worker thread. When the adapter is being removed the adapter state is set to VNIC_REMOVING and the work queue is

[PATCH 5.10 439/663] Take mmap lock in cacheflush syscall

2021-03-01 Thread Greg Kroah-Hartman
From: Jann Horn [ Upstream commit c26958cb5a0d9053d1358258827638773f3d36ed ] We need to take the mmap lock around find_vma() and subsequent use of the VMA. Otherwise, we can race with concurrent operations like munmap(), which can lead to use-after-free accesses to freed VMAs. Fixes:

memory leak in edge_startup

2021-03-01 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:29c395c7 Merge tag 'x86-entry-2021-02-24' of git://git.ker.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10d694dad0 kernel config: https://syzkaller.appspot.com/x/.config?x=66b7497b2c5acd67

[PATCH 5.10 012/663] bfq: Avoid false bfq queue merging

2021-03-01 Thread Greg Kroah-Hartman
From: Jan Kara commit 41e76c85660c022c6bf5713bfb6c21e64a487cec upstream. bfq_setup_cooperator() uses bfqd->in_serv_last_pos so detect whether it makes sense to merge current bfq queue with the in-service queue. However if the in-service queue is freshly scheduled and didn't dispatch any

[PATCH 5.11 262/775] ASoC: Intel: sof_sdw: add missing TGL_HDMI quirk for Dell SKU 0A32

2021-03-01 Thread Greg Kroah-Hartman
From: Pierre-Louis Bossart [ Upstream commit 45c92ec32b43c6cb42341ebf07577eefed9d87ec ] We missed adding the TGL_HDMI quirk which is very much needed to expose the 4 display pipelines and will be required on TGL topologies. Fixes: 488cdbd8931fe ('ASoC: Intel: sof_sdw: add quirk for new

[PATCH 5.10 485/663] HID: wacom: Ignore attempts to overwrite the touch_max value from HID

2021-03-01 Thread Greg Kroah-Hartman
From: Jason Gerecke commit 88f38846bfb1a452a3d47e38aeab20a4ceb74294 upstream. The `wacom_feature_mapping` function is careful to only set the the touch_max value a single time, but this care does not extend to the `wacom_wac_finger_event` function. In particular, if a device sends multiple

[PATCH 5.11 342/775] RDMA/rtrs-srv: Jump to dereg_mr label if allocate iu fails

2021-03-01 Thread Greg Kroah-Hartman
From: Guoqing Jiang [ Upstream commit f77c4839ee8f4612dcb6601602329096030bd813 ] The rtrs_iu_free is called in rtrs_iu_alloc if memory is limited, so we don't need to free the same iu again. Fixes: 9cb837480424 ("RDMA/rtrs: server: main functionality") Link:

[PATCH 5.10 647/663] dm writecache: fix writing beyond end of underlying device when shrinking

2021-03-01 Thread Greg Kroah-Hartman
From: Mikulas Patocka commit 4134455f2aafdfeab50cabb4cccb35e916034b93 upstream. Do not attempt to write any data beyond the end of the underlying data device while shrinking it. The DM writecache device must be suspended when the underlying data device is shrunk. Signed-off-by: Mikulas

[PATCH 5.11 007/775] 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 492/663] usb: musb: Fix runtime PM race in musb_queue_resume_work

2021-03-01 Thread Greg Kroah-Hartman
From: Paul Cercueil commit 0eaa1a3714db34a59ce121de5733c3909c529463 upstream. musb_queue_resume_work() would call the provided callback if the runtime PM status was 'active'. Otherwise, it would enqueue the request if the hardware was still suspended (musb->is_runtime_suspended is true). This

[PATCH 5.10 600/663] mm/vmscan: restore zone_reclaim_mode ABI

2021-03-01 Thread Greg Kroah-Hartman
From: Dave Hansen commit 519983645a9f2ec339cabfa0c6ef7b09be985dd0 upstream. I went to go add a new RECLAIM_* mode for the zone_reclaim_mode sysctl. Like a good kernel developer, I also went to go update the documentation. I noticed that the bits in the documentation didn't match the bits in

[PATCH 5.10 111/663] 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 511/663] bcache: Move journal work to new flush wq

2021-03-01 Thread Greg Kroah-Hartman
From: Kai Krakow commit afe78ab46f638ecdf80a35b122ffc92c20d9ae5d upstream. This is potentially long running and not latency sensitive, let's get it out of the way of other latency sensitive events. As observed in the previous commit, the `system_wq` comes easily congested by bcache, and this

[PATCH 5.10 273/663] clk: renesas: r8a779a0: Fix parent of CBFUSA clock

2021-03-01 Thread Greg Kroah-Hartman
From: Geert Uytterhoeven [ Upstream commit 80d3e07ec509c5098d44e4f1416cc9f133fd436f ] According to Figure 8.1.1 ("Block Diagram of CPG (R-Car V3U-AD)") in the R-Car V3U Series User's Manual Rev. 0.5, the parent of the CBFUSA clock is EXTAL. Fixes: 17bcc8035d2d19fc ("clk: renesas: cpg-mssr: Add

[PATCH 5.11 129/775] ibmvnic: skip send_request_unmap for timeout reset

2021-03-01 Thread Greg Kroah-Hartman
From: Lijun Pan [ Upstream commit 7d3a7b9ea59ddb223aec59b45fa1713c633aaed4 ] Timeout reset will trigger the VIOS to unmap it automatically, similarly as FAILVOER and MOBILITY events. If we unmap it in the linux side, we will see errors like "3003: Error 4 in REQUEST_UNMAP_RSP". So, don't

[PATCH 5.11 070/775] 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.10 576/663] entry/kvm: Explicitly flush pending rcuog wakeup before last rescheduling point

2021-03-01 Thread Greg Kroah-Hartman
From: Frederic Weisbecker commit 4ae7dc97f726ea95c58ac58af71cc034ad22d7de upstream. Following the idle loop model, cleanly check for pending rcuog wakeup before the last rescheduling point upon resuming to guest mode. This way we can avoid to do it from rcu_user_enter() with the last resort

[PATCH 5.10 410/663] drm/msm/mdp5: Fix wait-for-commit for cmd panels

2021-03-01 Thread Greg Kroah-Hartman
From: Iskren Chernev [ Upstream commit 68e4f01fddb4ead80e8c7084db489307f22c9cbb ] Before the offending commit in msm_atomic_commit_tail wait_flush was called once per frame, after the commit was submitted. After it wait_flush is also called at the beginning to ensure previous potentially async

[PATCH 5.11 255/775] f2fs: fix a wrong condition in __submit_bio

2021-03-01 Thread Greg Kroah-Hartman
From: Dehe Gu [ Upstream commit 39f71b7e40e21805d6b15fc7750bdd9cab6a5010 ] We should use !F2FS_IO_ALIGNED() to check and submit_io directly. Fixes: 8223ecc456d0 ("f2fs: fix to add missing F2FS_IO_ALIGNED() condition") Reviewed-by: Chao Yu Signed-off-by: Dehe Gu Signed-off-by: Ge Qiu

[PATCH 5.10 282/663] power: supply: cpcap-battery: Fix missing power_supply_put()

2021-03-01 Thread Greg Kroah-Hartman
From: Tony Lindgren [ Upstream commit 97456a24acb41b74ab6910f40fb8f09b206fd3b5 ] Fix missing power_supply_put(). Cc: Arthur Demchenkov Cc: Carl Philipp Klemm Cc: Merlijn Wajer Cc: Pavel Machek Fixes: 8b0134cc14b9 ("power: supply: cpcap-battery: Fix handling of lowered charger voltage")

[PATCH 5.11 188/775] drm/amdgpu: Fix macro name _AMDGPU_TRACE_H_ in preprocessor if condition

2021-03-01 Thread Greg Kroah-Hartman
From: Chenyang Li [ Upstream commit 956e20eb0fbb206e5e795539db5469db099715c8 ] Add an underscore in amdgpu_trace.h line 24 "_AMDGPU_TRACE_H". Fixes: d38ceaf99ed0 ("drm/amdgpu: add core driver (v4)") Reviewed-by: Guchun Chen Reviewed-by: Paul Menzel Signed-off-by: Chenyang Li Signed-off-by:

[PATCH 5.11 324/775] dmaengine: fsldma: Fix a resource leak in the remove function

2021-03-01 Thread Greg Kroah-Hartman
From: Christophe JAILLET [ Upstream commit cbc0ad004c03ad7971726a5db3ec84dba3dcb857 ] A 'irq_dispose_mapping()' call is missing in the remove function. Add it. This is needed to undo the 'irq_of_parse_and_map() call from the probe function and already part of the error handling path of the

[PATCH 5.10 504/663] ALSA: hda/realtek: Quirk for HP Spectre x360 14 amp setup

2021-03-01 Thread Greg Kroah-Hartman
From: Takashi Iwai commit c3bb2b521944ffbbc8c24b849f81977a9915fb5e upstream. HP Spectre x360 14 model (PCI SSID 103c:87f7) seems requiring a unique setup for its external amp: the GPIO0 needs to be toggled on and off shortly at each device initialization via runtime PM. This patch implements

[PATCH 5.10 125/663] ibmvnic: add memory barrier to protect long term buffer

2021-03-01 Thread Greg Kroah-Hartman
From: Lijun Pan [ Upstream commit 42557dab78edc8235aba5b441f2eb35f725a0ede ] dma_rmb() barrier is added to load the long term buffer before copying it to socket buffer; and dma_wmb() barrier is added to update the long term buffer before it being accessed by VIOS (virtual i/o server). Fixes:

[PATCH 5.10 086/663] soc: aspeed: snoop: Add clock control logic

2021-03-01 Thread Greg Kroah-Hartman
From: Jae Hyun Yoo [ Upstream commit 3f94cf15583be554df7aaa651b8ff8e1b68fbe51 ] If LPC SNOOP driver is registered ahead of lpc-ctrl module, LPC SNOOP block will be enabled without heart beating of LCLK until lpc-ctrl enables the LCLK. This issue causes improper handling on host interrupts when

[PATCH 5.10 482/663] ACPI: configfs: add missing check after configfs_register_default_group()

2021-03-01 Thread Greg Kroah-Hartman
From: Qinglang Miao commit 67e40054de86aae520ddc2a072d7f6951812a14f upstream. A list_add corruption is reported by Hulk Robot like this: == list_add corruption. Call Trace: link_obj+0xc0/0x1c0 link_group+0x21/0x140 configfs_register_subsystem+0xdb/0x380

[PATCH 5.10 370/663] spi: Skip zero-length transfers in spi_transfer_one_message()

2021-03-01 Thread Greg Kroah-Hartman
From: Nicolas Saenz Julienne [ Upstream commit b306320322c9cfaa465bc2c7367acf6072b1ac0e ] With the introduction of 26751de25d25 ("spi: bcm2835: Micro-optimise FIFO loops") it has become apparent that some users might initiate zero-length SPI transfers. A fact the micro-optimization omitted, and

[PATCH 5.11 181/775] media: allegro: Fix use after free on error

2021-03-01 Thread Greg Kroah-Hartman
From: Dan Carpenter [ Upstream commit ce814ad4bb52bfc7c0472e6da0aa742ab88f4361 ] The "channel" is added to the "dev->channels" but then if v4l2_m2m_ctx_init() fails then we free "channel" but it's still on the list so it could lead to a use after free. Let's not add it to the list until after

[PATCH 5.11 141/775] arm64: dts: broadcom: bcm4908: use proper NAND binding

2021-03-01 Thread Greg Kroah-Hartman
From: Rafał Miłecki [ Upstream commit 56098be85d19cd56b59d7b3854ea035cc8cb9e95 ] BCM4908 has controller that needs different IRQ handling just like the BCM63138. Describe it properly. On Linux this change fixes: brcmstb_nand ff801800.nand: timeout waiting for command 0x9 brcmstb_nand

[PATCH 5.11 339/775] RDMA/rtrs-srv: Release lock before call into close_sess

2021-03-01 Thread Greg Kroah-Hartman
From: Jack Wang [ Upstream commit 99f0c3807973359bba8f37d9198eea59fe38c32a ] In this error case, we don't need hold mutex to call close_sess. Fixes: 9cb837480424 ("RDMA/rtrs: server: main functionality") Link: https://lore.kernel.org/r/20201217141915.56989-4-jinpu.w...@cloud.ionos.com

[PATCH 5.11 347/775] RDMA/rtrs: Fix KASAN: stack-out-of-bounds bug

2021-03-01 Thread Greg Kroah-Hartman
From: Jack Wang [ Upstream commit 7fbc3c373eefc291ff96d48496106c106b7f81c6 ] When KASAN is enabled, we notice warning below: [ 483.436975] == [ 483.437234] BUG: KASAN: stack-out-of-bounds in _mlx5_ib_post_send+0x188a/0x2560

[PATCH 5.11 336/775] fdt: Properly handle "no-map" field in the memory region

2021-03-01 Thread Greg Kroah-Hartman
From: KarimAllah Ahmed [ Upstream commit 86588296acbfb1591e92ba60221e95677ecadb43 ] Mark the memory region with NOMAP flag instead of completely removing it from the memory blocks. That makes the FDT handling consistent with the EFI memory map handling. Cc: Rob Herring Cc: Frank Rowand Cc:

[PATCH 5.11 379/775] auxdisplay: Fix duplicate CHARLCD config symbol

2021-03-01 Thread Greg Kroah-Hartman
From: Geert Uytterhoeven [ Upstream commit b45616445a6e346daf8a173a0c51413aec067ebb ] A second CHARLCD config symbol was added instead of moving the existing one. Fix this by removing the old one. Fixes: 718e05ed92ecac0d ("auxdisplay: Introduce hd44780_common.[ch]") Signed-off-by: Geert

[PATCH 5.11 191/775] drm/virtio: make sure context is created in gem open

2021-03-01 Thread Greg Kroah-Hartman
From: Chia-I Wu [ Upstream commit 8aeef9d4f48917ce85710949b079548974b4a638 ] The context might still be missing when DRM_IOCTL_PRIME_FD_TO_HANDLE is the first ioctl on the drm_file. Fixes: 72b48ae800da ("drm/virtio: enqueue virtio_gpu_create_context after the first 3D ioctl") Cc: Gurchetan

[PATCH 5.11 032/775] 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.4 298/340] mtd: spi-nor: core: Add erase size check for erase command initialization

2021-03-01 Thread Greg Kroah-Hartman
From: Takahiro Kuwano commit 58fa22f68fcaff20ce4d08a6adffa64f65ccd37d upstream. Even if erase type is same as previous region, erase size can be different if the previous region is overlaid region. Since 'region->size' is assigned to 'cmd->size' for overlaid region, comparing 'erase->size' and

[PATCH 5.11 038/775] Bluetooth: hci_qca: Fix memleak in qca_controller_memdump

2021-03-01 Thread Greg Kroah-Hartman
From: Dinghao Liu [ Upstream commit 71f8e707557b9bc25dc90a59a752528d4e7c1cbf ] When __le32_to_cpu() fails, qca_memdump should be freed just like when vmalloc() fails. Fixes: d841502c79e3f ("Bluetooth: hci_qca: Collect controller memory dump during SSR") Signed-off-by: Dinghao Liu

[PATCH 5.10 406/663] PCI: Align checking of syscall user config accessors

2021-03-01 Thread Greg Kroah-Hartman
From: Heiner Kallweit [ Upstream commit ef9e4005cbaf022c6251263aa27836acccaef65d ] After 34e3207205ef ("PCI: handle positive error codes"), pci_user_read_config_*() and pci_user_write_config_*() return 0 or negative errno values, not PCIBIOS_* values like PCIBIOS_SUCCESSFUL or

[PATCH 5.11 199/775] media: camss: missing error code in msm_video_register()

2021-03-01 Thread Greg Kroah-Hartman
From: Dan Carpenter [ Upstream commit 9c67ed2ab299123872be14a3dc2ea44ce7e4538b ] This error path returns success but it should return -EINVAL. Fixes: cba3819d1e93 ("media: camss: Format configuration per hardware version") Signed-off-by: Dan Carpenter Reviewed-by: Robert Foss Signed-off-by:

[PATCH 5.11 256/775] ASoC: qcom: Fix typo error in HDMI regmap config callbacks

2021-03-01 Thread Greg Kroah-Hartman
From: Srinivasa Rao Mandadapu [ Upstream commit e681b1a6d706b4e54c3847bb822531b4660234f3 ] Had a typo in lpass platform driver that resulted in crash during suspend/resume with an HDMI dongle connected. The regmap read/write/volatile regesters validation callbacks in lpass-cpu were using MI2S

[PATCH 5.11 045/775] firmware: arm_scmi: Fix call site of scmi_notification_exit

2021-03-01 Thread Greg Kroah-Hartman
From: Cristian Marussi [ Upstream commit a90b6543bf062d65292b2c76f1630507d1c9d8ec ] Call scmi_notification_exit() only when SCMI platform driver instance has been really successfully removed. Link: https://lore.kernel.org/r/20210112191326.29091-1-cristian.maru...@arm.com Fixes: 6b8a69131dc63

[PATCH 5.10 160/663] media: i2c: ov5670: Fix PIXEL_RATE minimum value

2021-03-01 Thread Greg Kroah-Hartman
From: Jacopo Mondi [ Upstream commit dc1eb7c9c290cba52937c9a224b22a400bb0ffd7 ] The driver currently reports a single supported value for V4L2_CID_PIXEL_RATE and initializes the control's minimum value to 0, which is very risky, as userspace might accidentally use it as divider when calculating

[PATCH 5.11 013/775] bfq: Avoid false bfq queue merging

2021-03-01 Thread Greg Kroah-Hartman
From: Jan Kara commit 41e76c85660c022c6bf5713bfb6c21e64a487cec upstream. bfq_setup_cooperator() uses bfqd->in_serv_last_pos so detect whether it makes sense to merge current bfq queue with the in-service queue. However if the in-service queue is freshly scheduled and didn't dispatch any

[PATCH 5.4 300/340] fs/affs: release old buffer head on error path

2021-03-01 Thread Greg Kroah-Hartman
From: Pan Bian commit 70779b897395b330ba5a47bed84f94178da599f9 upstream. The reference count of the old buffer head should be decremented on path that fails to get the new buffer head. Fixes: 6b4657667ba0 ("fs/affs: add rename exchange") CC: sta...@vger.kernel.org # 4.14+ Signed-off-by: Pan

[PATCH 5.10 578/663] arm64: Extend workaround for erratum 1024718 to all versions of Cortex-A55

2021-03-01 Thread Greg Kroah-Hartman
From: Suzuki K Poulose commit c0b15c25d25171db4b70cc0b7dbc1130ee94017d upstream. The erratum 1024718 affects Cortex-A55 r0p0 to r2p0. However we apply the work around for r0p0 - r1p0. Unfortunately this won't be fixed for the future revisions for the CPU. Thus extend the work around for all

[PATCH 5.10 264/663] regulator: qcom-rpmh-regulator: add pm8009-1 chip revision

2021-03-01 Thread Greg Kroah-Hartman
From: Dmitry Baryshkov [ Upstream commit 951384cabc5dfb09251d440dbc26058eba86f97e ] PM8009 has special revision (P=1), which is to be used for sm8250 platform. The major difference is the S2 regulator which supplies 0.95 V instead of 2.848V. Declare regulators data to be used for this chip

[PATCH 5.11 087/775] ath11k: fix a locking bug in ath11k_mac_op_start()

2021-03-01 Thread Greg Kroah-Hartman
From: Dan Carpenter [ Upstream commit c202e2ebe1dc454ad54fd0018c023ec553d47284 ] This error path leads to a Smatch warning: drivers/net/wireless/ath/ath11k/mac.c:4269 ath11k_mac_op_start() error: double unlocked '>conf_mutex' (orig line 4251) We're not holding the lock when we

[PATCH 5.10 300/663] spi: imx: Dont print error on -EPROBEDEFER

2021-03-01 Thread Greg Kroah-Hartman
From: Guido Günther [ Upstream commit 8346633f2c87713a1852d802305e03555e9a9fce ] This avoids [0.962538] spi_imx 3082.spi: bitbang start failed with -517 durig driver probe. Fixes: 8197f489f4c4 ("spi: imx: Fix failure path leak on GPIO request error correctly") Signed-off-by: Guido

[PATCH 5.10 077/663] arm64: dts: meson: fix broken wifi node for Khadas VIM3L

2021-03-01 Thread Greg Kroah-Hartman
From: Artem Lapkin [ Upstream commit 39be8f441f78908e97ff913571e10ec03387a63a ] move _emmc_a ... from /* */ commented area, because cant load wifi fw without sd-uhs-sdr50 option on VIM3L [ 11.686590] brcmfmac: brcmf_chip_cores_check: CPU core not detected [ 11.696382] brcmfmac:

[PATCH 5.10 424/663] soundwire: export sdw_write/read_no_pm functions

2021-03-01 Thread Greg Kroah-Hartman
From: Bard Liao [ Upstream commit 167790abb90fa073d8341ee0e408ccad3d2109cd ] sdw_write_no_pm and sdw_read_no_pm are useful when we want to do IO without touching PM. Fixes: 0231453bc08f ('soundwire: bus: add clock stop helpers') Fixes: 60ee9be25571 ('soundwire: bus: add PM/no-PM versions of

[PATCH 5.11 292/775] ima: Free IMA measurement buffer after kexec syscall

2021-03-01 Thread Greg Kroah-Hartman
From: Lakshmi Ramasubramanian [ Upstream commit f31e3386a4e92ba6eda7328cb508462956c94c64 ] 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. This buffer is not freed

[PATCH 5.10 585/663] 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 009/775] w1: w1_therm: Fix conversion result for negative temperatures

2021-03-01 Thread Greg Kroah-Hartman
From: Ivan Zaentsev commit 2f6055c26f1913763eabc66c7c27d0693561e966 upstream. DS18B20 device driver returns an incorrect value for negative temperatures due to a missing sign-extension in w1_DS18B20_convert_temp(). Fix by using s16 temperature value when converting to int. Fixes: 9ace0b4dab1c

[PATCH 5.10 408/663] drm/msm: Fix MSM_INFO_GET_IOVA with carveout

2021-03-01 Thread Greg Kroah-Hartman
From: Iskren Chernev [ Upstream commit 6cefa31e810404dafdfcdb94874146cea11626c2 ] The msm_gem_get_iova should be guarded with gpu != NULL and not aspace != NULL, because aspace is NULL when using vram carveout. Fixes: 933415e24bd0d ("drm/msm: Add support for private address space instances")

[PATCH 5.11 269/775] btrfs: fix double accounting of ordered extent for subpage case in btrfs_invalidapge

2021-03-01 Thread Greg Kroah-Hartman
From: Qu Wenruo [ Upstream commit 951c80f83d61bd4b21794c8aba829c3c1a45c2d0 ] Commit dbfdb6d1b369 ("Btrfs: Search for all ordered extents that could span across a page") make btrfs_invalidapage() to search all ordered extents. The offending code looks like this: again: start =

[PATCH 5.10 366/663] selftests/ftrace: Update synthetic event syntax errors

2021-03-01 Thread Greg Kroah-Hartman
From: Tom Zanussi [ Upstream commit b5734e997e1117afb479ffda500e36fa91aea3e8 ] Some of the synthetic event errors and positions have changed in the code - update those and add several more tests. Also add a runtime check to ensure that the kernel supports dynamic strings in synthetic events,

[PATCH 4.19 067/247] ibmvnic: skip send_request_unmap for timeout reset

2021-03-01 Thread Greg Kroah-Hartman
From: Lijun Pan [ Upstream commit 7d3a7b9ea59ddb223aec59b45fa1713c633aaed4 ] Timeout reset will trigger the VIOS to unmap it automatically, similarly as FAILVOER and MOBILITY events. If we unmap it in the linux side, we will see errors like "3003: Error 4 in REQUEST_UNMAP_RSP". So, don't

[PATCH 5.10 340/663] IB/cm: Avoid a loop when device has 255 ports

2021-03-01 Thread Greg Kroah-Hartman
From: Parav Pandit [ Upstream commit 131be26750379592f0dd6244b2a90bbb504a10bb ] When RDMA device has 255 ports, loop iterator i overflows. Due to which cm_add_one() port iterator loops infinitely. Use core provided port iterator to avoid the infinite loop. Fixes: a977049dacde ("[PATCH] IB:

[PATCH 5.10 335/663] i2c: i2c-qcom-geni: Add shutdown callback for i2c

2021-03-01 Thread Greg Kroah-Hartman
From: Roja Rani Yarubandi [ Upstream commit e0371298ddc51761be257698554ea507ac8bf831 ] If the hardware is still accessing memory after SMMU translation is disabled (as part of smmu shutdown callback), then the IOVAs (I/O virtual address) which it was using will go on the bus as the physical

[PATCH 5.11 306/775] HSI: Fix PM usage counter unbalance in ssi_hw_init

2021-03-01 Thread Greg Kroah-Hartman
From: Zhang Qilong [ Upstream commit aa57e77b3d28f0df07149d88c47bc0f3aa77330b ] pm_runtime_get_sync will increment pm usage counter even it failed. Forgetting to putting operation will result in reference leak here. We fix it by replacing it with pm_runtime_resume_and_get to keep usage counter

[PATCH 5.10 595/663] x86: fix seq_file iteration for pat/memtype.c

2021-03-01 Thread Greg Kroah-Hartman
From: NeilBrown commit 3d2fc4c082448e9c05792f9b2a11c1d5db408b85 upstream. The memtype seq_file iterator allocates a buffer in the ->start and ->next functions and frees it in the ->show function. The preferred handling for such resources is to free them in the subsequent ->next or ->stop

[PATCH 5.10 284/663] fdt: Properly handle "no-map" field in the memory region

2021-03-01 Thread Greg Kroah-Hartman
From: KarimAllah Ahmed [ Upstream commit 86588296acbfb1591e92ba60221e95677ecadb43 ] Mark the memory region with NOMAP flag instead of completely removing it from the memory blocks. That makes the FDT handling consistent with the EFI memory map handling. Cc: Rob Herring Cc: Frank Rowand Cc:

[PATCH 5.10 651/663] dm era: Fix bitset memory leaks

2021-03-01 Thread Greg Kroah-Hartman
From: Nikos Tsironis commit 904e6b266619c2da5c58b5dce14ae30629e39645 upstream. Deallocate the memory allocated for the in-core bitsets when destroying the target and in error paths. Fixes: eec40579d84873 ("dm: add era target") Cc: sta...@vger.kernel.org # v3.15+ Signed-off-by: Nikos Tsironis

[PATCH 5.4 332/340] gtp: use icmp_ndo_send helper

2021-03-01 Thread Greg Kroah-Hartman
From: Jason A. Donenfeld commit e0fce6f945a26d4e953a147fe7ca11410322c9fe upstream. Because gtp is calling icmp from network device context, it should use the ndo helper so that the rate limiting applies correctly. Signed-off-by: Jason A. Donenfeld Cc: Harald Welte Signed-off-by: David S.

[PATCH 5.10 239/663] io_uring: fix possible deadlock in io_uring_poll

2021-03-01 Thread Greg Kroah-Hartman
From: Hao Xu [ Upstream commit ed670c3f90a67d9e16ab6d8893be6f072d79cd4c ] Abaci reported follow issue: [ 30.615891] == [ 30.616648] WARNING: possible circular locking dependency detected [ 30.617423] 5.11.0-rc3-next-20210115 #1 Not

[PATCH 5.10 532/663] btrfs: do not warn if we cant find the reloc root when looking up backref

2021-03-01 Thread Greg Kroah-Hartman
From: Josef Bacik commit f78743fbdae1bb31bc9c9233c3590a5048782381 upstream. The backref code is looking for a reloc_root that corresponds to the given fs root. However any number of things could have gone wrong while initializing that reloc_root, like ENOMEM while trying to allocate the root

[PATCH 5.10 107/663] net/mlx5e: kTLS, Use refcounts to free kTLS RX priv context

2021-03-01 Thread Greg Kroah-Hartman
From: Maxim Mikityanskiy [ Upstream commit b850bbff965129c34f50962638c0a66c82563536 ] wait_for_resync is unreliable - if it timeouts, priv_rx will be freed anyway. However, mlx5e_ktls_handle_get_psv_completion will be called sooner or later, leading to use-after-free. For example, it can happen

[PATCH 5.10 463/663] NFSv4: Fixes for nfs4_bitmask_adjust()

2021-03-01 Thread Greg Kroah-Hartman
From: Trond Myklebust [ Upstream commit 45901a231723a5a513ff08477983f3a274a6a910 ] We don't want to ask for the ACL in a WRITE reply, since we don't have a preallocated buffer. Instead of checking NFS_INO_INVALID_ACCESS, which is really about managing the access cache, we should look at the

[PATCH 5.10 067/663] 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 034/775] ARM: dts: exynos: correct PMIC interrupt trigger level on Odroid XU3 family

2021-03-01 Thread Greg Kroah-Hartman
From: Krzysztof Kozlowski [ Upstream commit 3e7d9a583a24f7582c6bc29a0d4d624feedbc2f9 ] 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: aac4e0615341

[PATCH 5.10 592/663] mtd: spi-nor: hisi-sfc: Put child node np on error path

2021-03-01 Thread Greg Kroah-Hartman
From: Pan Bian commit fe6653460ee7a7dbe0cd5fd322992af862ce5ab0 upstream. Put the child node np when it fails to get or register device. Fixes: e523f11141bd ("mtd: spi-nor: add hisilicon spi-nor flash controller driver") Cc: sta...@vger.kernel.org Signed-off-by: Pan Bian [ta: Add Fixes tag

[PATCH 5.11 075/775] opp: Correct debug message in _opp_add_static_v2()

2021-03-01 Thread Greg Kroah-Hartman
From: Dmitry Osipenko [ Upstream commit d7b9d9b31a3e55dcc9b5c289abfafe31efa5b5c4 ] The debug message always prints rate=0 instead of a proper value, fix it. Fixes: 6c591eec67cb ("OPP: Add helpers for reading the binding properties") Tested-by: Peter Geis Tested-by: Nicolas Chauvet Tested-by:

[PATCH 5.10 254/663] irqchip/imx: IMX_INTMUX should not default to y, unconditionally

2021-03-01 Thread Greg Kroah-Hartman
From: Geert Uytterhoeven [ Upstream commit a890caeb2ba40ca183969230e204ab144f258357 ] Merely enabling CONFIG_COMPILE_TEST should not enable additional code. To fix this, restrict the automatic enabling of IMX_INTMUX to ARCH_MXC, and ask the user in case of compile-testing. Fixes:

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