[PATCH 5.8 094/232] watchdog: f71808e_wdt: clear watchdog timeout occurred flag

2020-08-20 Thread Greg Kroah-Hartman
From: Ahmad Fatoum commit 4f39d575844148fbf3081571a1f3b4ae04150958 upstream. The flag indicating a watchdog timeout having occurred normally persists till Power-On Reset of the Fintek Super I/O chip. The user can clear it by writing a `1' to the bit. The driver doesn't offer a restart method, s

[PATCH 5.8 110/232] remoteproc: qcom_q6v5_mss: Validate modem blob firmware size before load

2020-08-20 Thread Greg Kroah-Hartman
From: Sibi Sankar commit 135b9e8d1cd8ba5ac9ad9bcf24b464b7b052e5b8 upstream. The following mem abort is observed when one of the modem blob firmware size exceeds the allocated mpss region. Fix this by restricting the copy size to segment size using request_firmware_into_buf before load. Err Logs

[PATCH 5.8 106/232] gfs2: Fix refcount leak in gfs2_glock_poke

2020-08-20 Thread Greg Kroah-Hartman
From: Andreas Gruenbacher commit c07bfb4d8fa1ee11c6d18b093d0bb6c8832d3626 upstream. In gfs2_glock_poke, make sure gfs2_holder_uninit is called on the local glock holder. Without that, we're leaking a glock and a pid reference. Fixes: 9e8990dea926 ("gfs2: Smarter iopen glock waiting") Cc: sta..

[PATCH 5.8 108/232] remoteproc: qcom: q6v5: Update running state before requesting stop

2020-08-20 Thread Greg Kroah-Hartman
From: Sibi Sankar commit 5b7be880074c73540948f8fc597e0407b98fabfa upstream. Sometimes the stop triggers a watchdog rather than a stop-ack. Update the running state to false on requesting stop to skip the watchdog instead. Error Logs: $ echo stop > /sys/class/remoteproc/remoteproc0/state ipa 1e4

[PATCH 5.8 138/232] crypto: af_alg - Fix regression on empty requests

2020-08-20 Thread Greg Kroah-Hartman
From: Herbert Xu [ Upstream commit 662bb52f50bca16a74fe92b487a14d7dccb85e1a ] Some user-space programs rely on crypto requests that have no control metadata. This broke when a check was added to require the presence of control metadata with the ctx->init flag. This patch fixes the regression b

[PATCH 5.8 134/232] selftests/bpf: test_progs avoid minus shell exit codes

2020-08-20 Thread Greg Kroah-Hartman
From: Jesper Dangaard Brouer [ Upstream commit b8c50df0cb3eb9008f8372e4ff0317eee993b8d1 ] There are a number of places in test_progs that use minus-1 as the argument to exit(). This is confusing as a process exit status is masked to be a number between 0 and 255 as defined in man exit(3). Thus,

[PATCH 5.8 125/232] media: staging: rkisp1: rename macros RKISP1_DIR_* to RKISP1_ISP_SD_*

2020-08-20 Thread Greg Kroah-Hartman
From: Dafna Hirschfeld [ Upstream commit c247818a873adcb8488021eed38c330ea8b288a3 ] The macros 'RKISP1_DIR_*' are flags that indicate on which pads of the isp subdevice the media bus code is supported. So the prefix RKISP1_ISP_SD_ is better. Signed-off-by: Dafna Hirschfeld Acked-by: Helen Koik

[PATCH 5.8 148/232] dm rq: dont call blk_mq_queue_stopped() in dm_stop_queue()

2020-08-20 Thread Greg Kroah-Hartman
From: Ming Lei [ Upstream commit e78c6cd49d741cfb49eaeb38998ba34d27bc ] dm_stop_queue() only uses blk_mq_quiesce_queue() so it doesn't formally stop the blk-mq queue; therefore there is no point making the blk_mq_queue_stopped() check -- it will never be stopped. In addition, even though dm

[PATCH 5.8 168/232] sched/uclamp: Fix a deadlock when enabling uclamp static key

2020-08-20 Thread Greg Kroah-Hartman
From: Qais Yousef [ Upstream commit e65855a52b479f98674998cb23b21ef5a8144b04 ] The following splat was caught when setting uclamp value of a task: BUG: sleeping function called from invalid context at ./include/linux/percpu-rwsem.h:49 cpus_read_lock+0x68/0x130 static_key_enable+0x1c/0

[PATCH 5.8 150/232] f2fs: compress: fix to avoid memory leak on cc->cpages

2020-08-20 Thread Greg Kroah-Hartman
From: Chao Yu [ Upstream commit 02772fbfcba8597eef9d5c5f7f94087132d0c1d4 ] Memory allocated for storing compressed pages' poitner should be released after f2fs_write_compressed_pages(), otherwise it will cause memory leak issue. Signed-off-by: Chao Yu Fixes: 4c8ff7095bef ("f2fs: support data c

[PATCH 5.8 147/232] gpu: ipu-v3: image-convert: Wait for all EOFs before completing a tile

2020-08-20 Thread Greg Kroah-Hartman
From: Steve Longerbeam [ Upstream commit dd81d821d0b3f77d949d0cac5c05c1f05b921d46 ] Use a bit-mask of EOF irqs to determine when all required idmac channel EOFs have been received for a tile conversion, and only do tile completion processing after all EOFs have been received. Otherwise it was fo

Re: [RESEND PATCH 1/5] ARM: dts: prima: Align L2 cache-controller nodename with dtschema

2020-08-20 Thread Krzysztof Kozlowski
On Wed, Aug 19, 2020 at 07:58:49PM +0200, Krzysztof Kozlowski wrote: > Fix dtschema validator warnings like: > l2-cache-controller@8004: $nodename:0: > 'l2-cache-controller@8004' does not match > '^(cache-controller|cpu)(@[0-9a-f,]+)*$' > > Signed-off-by: Krzysztof Kozlowski

[PATCH 5.8 129/232] IB/uverbs: Set IOVA on IB MR in uverbs layer

2020-08-20 Thread Greg Kroah-Hartman
From: Yishai Hadas [ Upstream commit 04c0a5fcfcf65aade2fb238b6336445f1a99b646 ] Set IOVA on IB MR in uverbs layer to let all drivers have it, this includes both reg/rereg MR flows. As part of this change cleaned-up this setting from the drivers that already did it by themselves in their user flo

[PATCH 5.8 175/232] ubi: fastmap: Free fastmap next anchor peb during detach

2020-08-20 Thread Greg Kroah-Hartman
From: Zhihao Cheng [ Upstream commit c3fc1a3919e35a9d8157ed3ae6fd0a478293ba2c ] ubi_wl_entry related with the fm_next_anchor PEB is not freed during detach, which causes a memory leak. Don't forget to release fm_next_anchor PEB while detaching ubi from mtd when CONFIG_MTD_UBI_FASTMAP is enabled.

Re: [RESEND PATCH 4/5] ARM: dts: tango: Align L2 cache-controller nodename with dtschema

2020-08-20 Thread Krzysztof Kozlowski
On Wed, Aug 19, 2020 at 07:58:52PM +0200, Krzysztof Kozlowski wrote: > Fix dtschema validator warnings like: > l2-cache-controller@2010: $nodename:0: > 'l2-cache-controller@2010' does not match > '^(cache-controller|cpu)(@[0-9a-f,]+)*$' > > Signed-off-by: Krzysztof Kozlowski

[PATCH 5.8 167/232] nvme: fix deadlock in disconnect during scan_work and/or ana_work

2020-08-20 Thread Greg Kroah-Hartman
From: Sagi Grimberg [ Upstream commit ecca390e80561debbfdb4dc96bf94595136889fa ] A deadlock happens in the following scenario with multipath: 1) scan_work(nvme0) detects a new nsid while nvme0 is an optimized path to it, path nvme1 happens to be inaccessible. 2) Before scan_work is comp

[PATCH 5.8 177/232] clk: hsdk: Fix bad dependency on IOMEM

2020-08-20 Thread Greg Kroah-Hartman
From: Geert Uytterhoeven [ Upstream commit bd8548d0dcdab514e08e35a3451667486d879dae ] CONFIG_IOMEM does not exist. The correct symbol to depend on is CONFIG_HAS_IOMEM. Fixes: 1e7468bd9d30a21e ("clk: Specify IOMEM dependency for HSDK pll driver") Signed-off-by: Geert Uytterhoeven Link: https:/

[PATCH 5.8 180/232] libnvdimm/security: ensure sysfs poll thread woke up and fetch updated attr

2020-08-20 Thread Greg Kroah-Hartman
From: Jane Chu [ Upstream commit 7f674025d9f7321dea11b802cc0ab3f09cbe51c5 ] commit 7d988097c546 ("acpi/nfit, libnvdimm/security: Add security DSM overwrite support") adds a sysfs_notify_dirent() to wake up userspace poll thread when the "overwrite" operation has completed. But the notification

[PATCH 5.8 182/232] perf evsel: Dont set sample_regs_intr/sample_regs_user for dummy event

2020-08-20 Thread Greg Kroah-Hartman
From: Jin Yao [ Upstream commit c4735d990268399da9133b0ad445e488ece009ad ] Since commit 0a892c1c9472 ("perf record: Add dummy event during system wide synthesis"), a dummy event is added to capture mmaps. But if we run perf-record as, # perf record -e cycles:p -IXMM0 -a -- sleep 1 Error: d

[PATCH 5.8 176/232] ubifs: Fix wrong orphan node deletion in ubifs_jnl_update|rename

2020-08-20 Thread Greg Kroah-Hartman
From: Zhihao Cheng [ Upstream commit 094b6d1295474f338201b846a1f15e72eb0b12cf ] There a wrong orphan node deleting in error handling path in ubifs_jnl_update() and ubifs_jnl_rename(), which may cause following error msg: UBIFS error (ubi0:0 pid 1522): ubifs_delete_orphan [ubifs]: missing or

[PATCH 5.8 157/232] clk: qcom: clk-alpha-pll: remove unused/incorrect PLL_CAL_VAL

2020-08-20 Thread Greg Kroah-Hartman
From: Jonathan Marek [ Upstream commit c8b9002f44e4a1d2771b2f59f6de900864b1f9d7 ] 0x44 isn't a register offset, it is the value that goes into CAL_L_VAL. Fixes: 548a909597d5 ("clk: qcom: clk-alpha-pll: Add support for Trion PLLs") Signed-off-by: Jonathan Marek Tested-by: Dmitry Baryshkov Link

[PATCH 5.8 170/232] perf tools: Fix term parsing for raw syntax

2020-08-20 Thread Greg Kroah-Hartman
From: Jiri Olsa [ Upstream commit 4929e95a1400e45b4b5a87fd3ce10273444187d4 ] Jin Yao reported issue with possible conflict between raw events and term values in pmu event syntax. Currently following syntax is resolved as raw event with 0xead value: uncore_imc_free_running/read/ instead of u

[PATCH 5.8 174/232] ubi: fastmap: Dont produce the initial next anchor PEB when fastmap is disabled

2020-08-20 Thread Greg Kroah-Hartman
From: Zhihao Cheng [ Upstream commit 3b185255bb2f34fa6927619b9ef27f192a3d9f5a ] Following process triggers a memleak caused by forgetting to release the initial next anchor PEB (CONFIG_MTD_UBI_FASTMAP is disabled): 1. attach -> __erase_worker -> produce the initial next anchor PEB 2. detach -> u

[PATCH 5.8 183/232] scsi: lpfc: nvmet: Avoid hang / use-after-free again when destroying targetport

2020-08-20 Thread Greg Kroah-Hartman
From: Ewan D. Milne [ Upstream commit af6de8c60fe9433afa73cea6fcccdccd98ad3e5e ] We cannot wait on a completion object in the lpfc_nvme_targetport structure in the _destroy_targetport() code path because the NVMe/fc transport will free that structure immediately after the .targetport_delete() ca

[PATCH 5.8 172/232] i2c: rcar: avoid race when unregistering slave

2020-08-20 Thread Greg Kroah-Hartman
From: Wolfram Sang [ Upstream commit c7c9e914f9a0478fba4dc6f227cfd69cf84a4063 ] Due to the lockless design of the driver, it is theoretically possible to access a NULL pointer, if a slave interrupt was running while we were unregistering the slave. To make this rock solid, disable the interrupt

[PATCH 5.8 184/232] nfs: nfs_file_write() should check for writeback errors

2020-08-20 Thread Greg Kroah-Hartman
From: Scott Mayhew [ Upstream commit ce368536dd614452407dc31e2449eb84681a06af ] The NFS_CONTEXT_ERROR_WRITE flag (as well as the check of said flag) was removed by commit 6fbda89b257f. The absence of an error check allows writes to be continually queued up for a server that may no longer be abl

[PATCH 5.8 169/232] pwm: bcm-iproc: handle clk_get_rate() return

2020-08-20 Thread Greg Kroah-Hartman
From: Rayagonda Kokatanur [ Upstream commit 6ced5ff0be8e94871ba846dfbddf69d21363f3d7 ] Handle clk_get_rate() returning 0 to avoid possible division by zero. Fixes: daa5abc41c80 ("pwm: Add support for Broadcom iProc PWM controller") Signed-off-by: Rayagonda Kokatanur Signed-off-by: Scott Brande

[PATCH 5.8 171/232] tools build feature: Use CC and CXX from parent

2020-08-20 Thread Greg Kroah-Hartman
From: Thomas Hebb [ Upstream commit e3232c2f39acafd5a29128425bc30b9884642cfa ] commit c8c188679ccf ("tools build: Use the same CC for feature detection and actual build") changed these assignments from unconditional (:=) to conditional (?=) so that they wouldn't clobber values from the environme

[PATCH 5.7 012/204] btrfs: dont allocate anonymous block device for user invisible roots

2020-08-20 Thread Greg Kroah-Hartman
From: Qu Wenruo commit 851fd730a743e072badaf67caf39883e32439431 upstream. [BUG] When a lot of subvolumes are created, there is a user report about transaction aborted: BTRFS: Transaction aborted (error -24) WARNING: CPU: 17 PID: 17041 at fs/btrfs/transaction.c:1576 create_pending_snapshot+

[PATCH 5.7 018/204] btrfs: dont traverse into the seed devices in show_devname

2020-08-20 Thread Greg Kroah-Hartman
From: Anand Jain commit 4faf55b03823e96c44dc4e36452ed3b12fdb upstream. ->show_devname currently shows the lowest devid in the list. As the seed devices have the lowest devid in the sprouted filesystem, the userland tool such as findmnt end up seeing seed device instead of the device from the

[PATCH 5.7 003/204] genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq()

2020-08-20 Thread Greg Kroah-Hartman
From: Guenter Roeck commit e27b1636e9337d1a1d174b191e53d0f86421a822 upstream. rearm_wake_irq() does not unlock the irq descriptor if the interrupt is not suspended or if wakeup is not enabled on it. Restucture the exit conditions so the unlock is always ensured. Fixes: 3a79bc63d9075 ("PCI: irq

[PATCH 5.7 004/204] PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context()

2020-08-20 Thread Greg Kroah-Hartman
From: Rafael J. Wysocki commit dae68d7fd4930315389117e9da35b763f12238f9 upstream. If context is not NULL in acpiphp_grab_context(), but the is_going_away flag is set for the device's parent, the reference counter of the context needs to be decremented before returning NULL or the context will ne

[PATCH 5.7 022/204] btrfs: relocation: review the call sites which can be interrupted by signal

2020-08-20 Thread Greg Kroah-Hartman
From: Qu Wenruo commit 44d354abf33e92a5e73b965c84caf5a5d5e58a0b upstream. Since most metadata reservation calls can return -EINTR when get interrupted by fatal signal, we need to review the all the metadata reservation call sites. In relocation code, the metadata reservation happens in the foll

[PATCH 5.8 207/232] fs/minix: fix block limit check for V1 filesystems

2020-08-20 Thread Greg Kroah-Hartman
From: Eric Biggers [ Upstream commit 0a12c4a8069607247cb8edc3b035a664e636fd9a ] The minix filesystem reads its maximum file size from its on-disk superblock. This value isn't necessarily a multiple of the block size. When it's not, the V1 block mapping code doesn't allow mapping the last possib

[PATCH 5.8 158/232] iommu/vt-d: Handle non-page aligned address

2020-08-20 Thread Greg Kroah-Hartman
From: Liu Yi L [ Upstream commit 288d08e78008828416ffaa85ef274b4e29ef3dae ] Address information for device TLB invalidation comes from userspace when device is directly assigned to a guest with vIOMMU support. VT-d requires page aligned address. This patch checks and enforce address to be page a

[PATCH 5.7 005/204] PCI/ATS: Add pci_pri_supported() to check device or associated PF

2020-08-20 Thread Greg Kroah-Hartman
From: Ashok Raj commit 3f9a7a13fe4cb6e119e4e4745fbf975d30bfac9b upstream. For SR-IOV, the PF PRI is shared between the PF and any associated VFs, and the PRI Capability is allowed for PFs but not for VFs. Searching for the PRI Capability on a VF always fails, even if its associated PF supports

[PATCH 5.8 208/232] fs/minix: remove expected error message in block_to_path()

2020-08-20 Thread Greg Kroah-Hartman
From: Eric Biggers [ Upstream commit f666f9fb9a36f1c833b9d18923572f0e4d304754 ] When truncating a file to a size within the last allowed logical block, block_to_path() is called with the *next* block. This exceeds the limit, causing the "block %ld too big" error message to be printed. This cas

[PATCH 5.8 166/232] clk: clk-atlas6: fix return value check in atlas6_clk_init()

2020-08-20 Thread Greg Kroah-Hartman
From: Xu Wang [ Upstream commit 12b90b40854a8461a02ef19f6f4474cc88d64b66 ] In case of error, the function clk_register() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Signed-off-by: Xu Wang Link: https://lore.kernel.org/r/20

[PATCH 5.7 027/204] btrfs: dont WARN if we abort a transaction with EROFS

2020-08-20 Thread Greg Kroah-Hartman
From: Josef Bacik commit f95ebdbed46a4d8b9fdb7bff109fdbb6fc9a6dc8 upstream. If we got some sort of corruption via a read and call btrfs_handle_fs_error() we'll set BTRFS_FS_STATE_ERROR on the fs and complain. If a subsequent trans handle trips over this it'll get EROFS and then abort. However

[PATCH 5.7 008/204] PCI: qcom: Define some PARF params needed for ipq8064 SoC

2020-08-20 Thread Greg Kroah-Hartman
From: Ansuel Smith commit 5149901e9e6deca487c01cc434a3ac4125c7b00b upstream. Set some specific value for Tx De-Emphasis, Tx Swing and Rx equalization needed on some ipq8064 based device (Netgear R7800 for example). Without this the system locks on kernel load. Link: https://lore.kernel.org/r/20

[PATCH 5.7 038/204] dt-bindings: iio: io-channel-mux: Fix compatible string in example code

2020-08-20 Thread Greg Kroah-Hartman
From: Christian Eggers commit add48ba425192c6e04ce70549129cacd01e2a09e upstream. The correct compatible string is "gpio-mux" (see bindings/mux/gpio-mux.txt). Cc: sta...@vger.kernel.org # v4.13+ Reviewed-by: Peter Rosin Signed-off-by: Christian Eggers Link: https://lore.kernel.org/r/2020072710

[PATCH 5.7 037/204] arm64: perf: Correct the event index in sysfs

2020-08-20 Thread Greg Kroah-Hartman
From: Shaokun Zhang commit 539707caa1a89ee4efc57b4e4231c20c46575ccc upstream. When PMU event ID is equal or greater than 0x4000, it will be reduced by 0x4000 and it is not the raw number in the sysfs. Let's correct it and obtain the raw event ID. Before this patch: cat /sys/bus/event_source/dev

[PATCH 5.7 007/204] PCI: Add device even if driver attach failed

2020-08-20 Thread Greg Kroah-Hartman
From: Rajat Jain commit 2194bc7c39610be7cabe7456c5f63a570604f015 upstream. device_attach() returning failure indicates a driver error while trying to probe the device. In such a scenario, the PCI device should still be added in the system and be visible to the user. When device_attach() fails,

[PATCH 5.7 040/204] iio: imu: st_lsm6dsx: reset hw ts after resume

2020-08-20 Thread Greg Kroah-Hartman
From: Lorenzo Bianconi commit a1bab9396c2d98c601ce81c27567159dfbc10c19 upstream. Reset hw time samples generator after system resume in order to avoid disalignment between system and device time reference since FIFO batching and time samples generator are disabled during suspend. Fixes: 2134510

[PATCH 5.7 054/204] irqchip/gic-v4.1: Ensure accessing the correct RD when writing INVALLR

2020-08-20 Thread Greg Kroah-Hartman
From: Zenghui Yu commit 3af9571cd585efafc2facbd8dbd407317ff898cf upstream. The GICv4.1 spec tells us that it's CONSTRAINED UNPREDICTABLE to issue a register-based invalidation operation for a vPEID not mapped to that RD, or another RD within the same CommonLPIAff group. To follow this rule, com

[PATCH 5.7 070/204] hugetlbfs: remove call to huge_pte_alloc without i_mmap_rwsem

2020-08-20 Thread Greg Kroah-Hartman
From: Mike Kravetz commit 34ae204f18519f0920bd50a644abd6fefc8dbfcf upstream. Commit c0d0381ade79 ("hugetlbfs: use i_mmap_rwsem for more pmd sharing synchronization") requires callers of huge_pte_alloc to hold i_mmap_rwsem in at least read mode. This is because the explicit locking in huge_pmd_s

[PATCH 5.7 056/204] net/compat: Add missing sock updates for SCM_RIGHTS

2020-08-20 Thread Greg Kroah-Hartman
From: Kees Cook commit d9539752d23283db4692384a634034f451261e29 upstream. Add missed sock updates to compat path via a new helper, which will be used more in coming patches. (The net/core/scm.c code is left as-is here to assist with -stable backports for the compat path.) Cc: Christoph Hellwig

[PATCH 5.7 055/204] pidfd: Add missing sock updates for pidfd_getfd()

2020-08-20 Thread Greg Kroah-Hartman
From: Kees Cook commit 4969f8a073977123504609d7310b42a588297aa4 upstream. The sock counting (sock_update_netprioidx() and sock_update_classid()) was missing from pidfd's implementation of received fd installation. Add a call to the new __receive_sock() helper. Cc: Christian Brauner Cc: Christo

[PATCH 5.7 047/204] pinctrl: ingenic: Enhance support for IRQ_TYPE_EDGE_BOTH

2020-08-20 Thread Greg Kroah-Hartman
From: Paul Cercueil commit 1c95348ba327fe8621d3680890c2341523d3524a upstream. Ingenic SoCs don't natively support registering an interrupt for both rising and falling edges. This has to be emulated in software. Until now, this was emulated by switching back and forth between IRQ_TYPE_EDGE_RISIN

[PATCH 5.7 052/204] net: stmmac: dwmac1000: provide multicast filter fallback

2020-08-20 Thread Greg Kroah-Hartman
From: Jonathan McDowell commit 592d751c1e174df5ff219946908b005eb48934b3 upstream. If we don't have a hardware multicast filter available then instead of silently failing to listen for the requested ethernet broadcast addresses fall back to receiving all multicast packets, in a similar fashion to

[PATCH 5.7 051/204] net: ethernet: stmmac: Disable hardware multicast filter

2020-08-20 Thread Greg Kroah-Hartman
From: Jonathan McDowell commit df43dd526e6609769ae513a81443c7aa727c8ca3 upstream. The IPQ806x does not appear to have a functional multicast ethernet address filter. This was observed as a failure to correctly receive IPv6 packets on a LAN to the all stations address. Checking the vendor driver

[PATCH 5.7 053/204] irqchip/loongson-liointc: Fix misuse of gc->mask_cache

2020-08-20 Thread Greg Kroah-Hartman
From: Huacai Chen commit c9c73a05413ea4a465cae1cb3593b01b190a233f upstream. In gc->mask_cache bits, 1 means enabled and 0 means disabled, but in the loongson-liointc driver mask_cache is misused by reverting its meaning. This patch fix the bug and update the comments as well. Fixes: dbb15226790

[PATCH 5.7 078/204] tracing/hwlat: Honor the tracing_cpumask

2020-08-20 Thread Greg Kroah-Hartman
From: Kevin Hao commit 96b4833b6827a62c295b149213c68b559514c929 upstream. In calculation of the cpu mask for the hwlat kernel thread, the wrong cpu mask is used instead of the tracing_cpumask, this causes the tracing/tracing_cpumask useless for hwlat tracer. Fixes it. Link: https://lkml.kernel.

[PATCH 5.7 079/204] tracing: Use trace_sched_process_free() instead of exit() for pid tracing

2020-08-20 Thread Greg Kroah-Hartman
From: Steven Rostedt (VMware) commit afcab636657421f7ebfa0783a91f90256bba0091 upstream. On exit, if a process is preempted after the trace_sched_process_exit() tracepoint but before the process is done exiting, then when it gets scheduled in, the function tracers will not filter it properly agai

[PATCH 5.7 076/204] ftrace: Setup correct FTRACE_FL_REGS flags for module

2020-08-20 Thread Greg Kroah-Hartman
From: Chengming Zhou commit 8a224ffb3f52b0027f6b7279854c71a31c48fc97 upstream. When module loaded and enabled, we will use __ftrace_replace_code for module if any ftrace_ops referenced it found. But we will get wrong ftrace_addr for module rec in ftrace_get_addr_new, because rec->flags has not b

[PATCH 5.7 071/204] mm/shuffle: dont move pages between zones and dont read garbage memmaps

2020-08-20 Thread Greg Kroah-Hartman
From: David Hildenbrand commit 4a93025cbe4a0b19d1a25a2d763a3d2018bad0d9 upstream. Especially with memory hotplug, we can have offline sections (with a garbage memmap) and overlapping zones. We have to make sure to only touch initialized memmaps (online sections managed by the buddy) and that th

[PATCH 5.7 077/204] kprobes: Fix NULL pointer dereference at kprobe_ftrace_handler

2020-08-20 Thread Greg Kroah-Hartman
From: Muchun Song commit 0cb2f1372baa60af8456388a574af6133edd7d80 upstream. We found a case of kernel panic on our server. The stack trace is as follows(omit some irrelevant information): BUG: kernel NULL pointer dereference, address: 0080 RIP: 0010:kprobe_ftrace_handler+0x5e/0x

[PATCH 5.7 081/204] watchdog: f71808e_wdt: remove use of wrong watchdog_info option

2020-08-20 Thread Greg Kroah-Hartman
From: Ahmad Fatoum commit 802141462d844f2e6a4d63a12260d79b7afc4c34 upstream. The flags that should be or-ed into the watchdog_info.options by drivers all start with WDIOF_, e.g. WDIOF_SETTIMEOUT, which indicates that the driver's watchdog_ops has a usable set_timeout. WDIOC_SETTIMEOUT was used

[PATCH 5.7 086/204] dm: dont call report zones for more than the user requested

2020-08-20 Thread Greg Kroah-Hartman
From: Johannes Thumshirn commit a9cb9f4148ef6bb8fabbdaa85c42b2171fbd5a0d upstream. Don't call report zones for more zones than the user actually requested, otherwise this can lead to out-of-bounds accesses in the callback functions. Such a situation can happen if the target's ->report_zones() c

[PATCH 5.7 061/204] mac80211: fix misplaced while instead of if

2020-08-20 Thread Greg Kroah-Hartman
From: Johannes Berg commit 5981fe5b0529ba25d95f37d7faa434183ad618c5 upstream. This never was intended to be a 'while' loop, it should've just been an 'if' instead of 'while'. Fix this. I noticed this while applying another patch from Ben that intended to fix a busy loop at this spot. Cc: sta..

[PATCH 5.7 082/204] watchdog: f71808e_wdt: clear watchdog timeout occurred flag

2020-08-20 Thread Greg Kroah-Hartman
From: Ahmad Fatoum commit 4f39d575844148fbf3081571a1f3b4ae04150958 upstream. The flag indicating a watchdog timeout having occurred normally persists till Power-On Reset of the Fintek Super I/O chip. The user can clear it by writing a `1' to the bit. The driver doesn't offer a restart method, s

[PATCH 5.7 087/204] module: Correctly truncate sysfs sections output

2020-08-20 Thread Greg Kroah-Hartman
From: Kees Cook commit 11990a5bd7e558e9203c1070fc52fb6f0488e75b upstream. The only-root-readable /sys/module/$module/sections/$section files did not truncate their output to the available buffer size. While most paths into the kernfs read handlers end up using PAGE_SIZE buffers, it's possible to

[PATCH 5.7 106/204] RDMA/ipoib: Fix ABBA deadlock with ipoib_reap_ah()

2020-08-20 Thread Greg Kroah-Hartman
From: Jason Gunthorpe [ Upstream commit 65936bf25f90fe440bb2d11624c7d10fab266639 ] ipoib_mcast_carrier_on_task() insanely open codes a rtnl_lock() such that the only time flush_workqueue() can be called is if it also clears IPOIB_FLAG_OPER_UP. Thus the flush inside ipoib_flush_ah() will deadloc

[PATCH 5.7 100/204] mfd: arizona: Ensure 32k clock is put on driver unbind and error

2020-08-20 Thread Greg Kroah-Hartman
From: Charles Keepax [ Upstream commit ddff6c45b21d0437ce0c85f8ac35d7b5480513d7 ] Whilst it doesn't matter if the internal 32k clock register settings are cleaned up on exit, as the part will be turned off losing any settings, hence the driver hasn't historially bothered. The external clock shou

[PATCH 5.7 104/204] platform/chrome: cros_ec_ishtp: Fix a double-unlock issue

2020-08-20 Thread Greg Kroah-Hartman
From: Qiushi Wu [ Upstream commit aaa3cbbac326c95308e315f1ab964a3369c4d07d ] In function cros_ec_ishtp_probe(), "up_write" is already called before function "cros_ec_dev_init". But "up_write" will be called again after the calling of the function "cros_ec_dev_init" failed. Thus add a call of the

[PATCH 5.7 103/204] mtd: rawnand: brcmnand: ECC error handling on EDU transfers

2020-08-20 Thread Greg Kroah-Hartman
From: Kamal Dasu [ Upstream commit 4551e78ad98add1f16b70cf286d5aad3ce7bcd4c ] Implement ECC correctable and uncorrectable error handling for EDU reads. If ECC correctable bitflips are encountered on EDU transfer, read page again using PIO. This is needed due to a NAND controller limitation where

[PATCH 5.7 108/204] media: staging: rkisp1: remove macro RKISP1_DIR_SINK_SRC

2020-08-20 Thread Greg Kroah-Hartman
From: Dafna Hirschfeld [ Upstream commit b861d139a36a4593498932bfec957bdcc7d98eb3 ] The macro RKISP1_DIR_SINK_SRC is a mask of two flags. The macro hides the fact that it's a mask and the code is actually more clear if we replace it the with bitwise-or explicitly. Signed-off-by: Dafna Hirschfel

[PATCH 5.7 064/204] MIPS: qi_lb60: Fix routing to audio amplifier

2020-08-20 Thread Greg Kroah-Hartman
From: Paul Cercueil commit 0889a67a9e7a56ba39af223d536630b20b877fda upstream. The ROUT (right channel output of audio codec) was connected to INL (left channel of audio amplifier) instead of INR (right channel of audio amplifier). Fixes: 8ddebad15e9b ("MIPS: qi_lb60: Migrate to devicetree") Cc:

[PATCH 5.7 095/204] remoteproc: qcom_q6v5_mss: Validate MBA firmware size before load

2020-08-20 Thread Greg Kroah-Hartman
From: Sibi Sankar commit e013f455d95add874f310dc47c608e8c70692ae5 upstream. The following mem abort is observed when the mba firmware size exceeds the allocated mba region. MBA firmware size is restricted to a maximum size of 1M and remaining memory region is used by modem debug policy firmware

[PATCH 5.7 121/204] devres: keep both device name and resource name in pretty name

2020-08-20 Thread Greg Kroah-Hartman
From: Vladimir Oltean [ Upstream commit 35bd8c07db2ce8fd2834ef866240613a4ef982e7 ] Sometimes debugging a device is easiest using devmem on its register map, and that can be seen with /proc/iomem. But some device drivers have many memory regions. Take for example a networking switch. Its memory m

[PATCH 5.7 093/204] gfs2: Never call gfs2_block_zero_range with an open transaction

2020-08-20 Thread Greg Kroah-Hartman
From: Bob Peterson commit 70499cdfeb3625c87eebe4f7a7ea06fa7447e5df upstream. Before this patch, some functions started transactions then they called gfs2_block_zero_range. However, gfs2_block_zero_range, like writes, can start transactions, which results in a recursive transaction error. For exa

[PATCH 5.7 097/204] drm/imx: imx-ldb: Disable both channels for split mode in enc->disable()

2020-08-20 Thread Greg Kroah-Hartman
From: Liu Ying commit 3b2a999582c467d1883716b37ffcc00178a13713 upstream. Both of the two LVDS channels should be disabled for split mode in the encoder's ->disable() callback, because they are enabled in the encoder's ->enable() callback. Fixes: 6556f7f82b9c ("drm: imx: Move imx-drm driver out

[PATCH 5.7 094/204] remoteproc: qcom: q6v5: Update running state before requesting stop

2020-08-20 Thread Greg Kroah-Hartman
From: Sibi Sankar commit 5b7be880074c73540948f8fc597e0407b98fabfa upstream. Sometimes the stop triggers a watchdog rather than a stop-ack. Update the running state to false on requesting stop to skip the watchdog instead. Error Logs: $ echo stop > /sys/class/remoteproc/remoteproc0/state ipa 1e4

[PATCH 5.7 120/204] crypto: af_alg - Fix regression on empty requests

2020-08-20 Thread Greg Kroah-Hartman
From: Herbert Xu [ Upstream commit 662bb52f50bca16a74fe92b487a14d7dccb85e1a ] Some user-space programs rely on crypto requests that have no control metadata. This broke when a check was added to require the presence of control metadata with the ctx->init flag. This patch fixes the regression b

[PATCH 5.7 118/204] USB: serial: ftdi_sio: clean up receive processing

2020-08-20 Thread Greg Kroah-Hartman
From: Johan Hovold [ Upstream commit ce054039ba5e47b75a3be02a00274e52b06a6456 ] Clean up receive processing by dropping the character pointer and keeping the length argument unchanged throughout the function. Also make it more apparent that sysrq processing can consume a characters by adding an

[PATCH 5.7 112/204] sched/uclamp: Protect uclamp fast path code with static key

2020-08-20 Thread Greg Kroah-Hartman
From: Qais Yousef [ Upstream commit 46609ce227039fd192e0ecc7d940bed587fd2c78 ] There is a report that when uclamp is enabled, a netperf UDP test regresses compared to a kernel compiled without uclamp. https://lore.kernel.org/lkml/20200529100806.ga3...@suse.de/ While investigating the root caus

[PATCH 5.7 150/204] nfs: ensure correct writeback errors are returned on close()

2020-08-20 Thread Greg Kroah-Hartman
From: Scott Mayhew [ Upstream commit 67dd23f9e6fbaf163431912ef5599c5e0693476c ] nfs_wb_all() calls filemap_write_and_wait(), which uses filemap_check_errors() to determine the error to return. filemap_check_errors() only looks at the mapping->flags and will therefore only return either -ENOSPC o

[PATCH 5.7 143/204] clk: qcom: gcc-sdm660: Fix up gcc_mss_mnoc_bimc_axi_clk

2020-08-20 Thread Greg Kroah-Hartman
From: Konrad Dybcio [ Upstream commit 3386af51d3bcebcba3f7becdb1ef2e384abe90cf ] Add missing halt_check, hwcg_reg and hwcg_bit properties. These were likely omitted when porting the driver upstream. Signed-off-by: Konrad Dybcio Link: https://lore.kernel.org/r/20200726111215.22361-9-konradyb...

[PATCH 5.7 146/204] sched/uclamp: Fix a deadlock when enabling uclamp static key

2020-08-20 Thread Greg Kroah-Hartman
From: Qais Yousef [ Upstream commit e65855a52b479f98674998cb23b21ef5a8144b04 ] The following splat was caught when setting uclamp value of a task: BUG: sleeping function called from invalid context at ./include/linux/percpu-rwsem.h:49 cpus_read_lock+0x68/0x130 static_key_enable+0x1c/0

[PATCH 5.7 151/204] ubifs: Fix wrong orphan node deletion in ubifs_jnl_update|rename

2020-08-20 Thread Greg Kroah-Hartman
From: Zhihao Cheng [ Upstream commit 094b6d1295474f338201b846a1f15e72eb0b12cf ] There a wrong orphan node deleting in error handling path in ubifs_jnl_update() and ubifs_jnl_rename(), which may cause following error msg: UBIFS error (ubi0:0 pid 1522): ubifs_delete_orphan [ubifs]: missing or

[PATCH 5.7 147/204] pwm: bcm-iproc: handle clk_get_rate() return

2020-08-20 Thread Greg Kroah-Hartman
From: Rayagonda Kokatanur [ Upstream commit 6ced5ff0be8e94871ba846dfbddf69d21363f3d7 ] Handle clk_get_rate() returning 0 to avoid possible division by zero. Fixes: daa5abc41c80 ("pwm: Add support for Broadcom iProc PWM controller") Signed-off-by: Rayagonda Kokatanur Signed-off-by: Scott Brande

[PATCH 5.7 136/204] selftests/powerpc: ptrace-pkey: Dont update expected UAMOR value

2020-08-20 Thread Greg Kroah-Hartman
From: Aneesh Kumar K.V [ Upstream commit 3563b9bea0ca7f53e4218b5e268550341a49f333 ] With commit 4a4a5e5d2aad ("powerpc/pkeys: key allocation/deallocation must not change pkey registers") we are not updating UAMOR on key allocation. So don't update the expected uamor value in the test. Fixes: 4a

[PATCH 5.7 141/204] i2c: rcar: slave: only send STOP event when we have been addressed

2020-08-20 Thread Greg Kroah-Hartman
From: Wolfram Sang [ Upstream commit 314139f9f0abdba61ed9a8463bbcb0bf900ac5a2 ] When the SSR interrupt is activated, it will detect every STOP condition on the bus, not only the ones after we have been addressed. So, enable this interrupt only after we have been addressed, and disable it otherwi

[PATCH 5.7 133/204] clk: actions: Fix h_clk for Actions S500 SoC

2020-08-20 Thread Greg Kroah-Hartman
From: Cristian Ciocaltea [ Upstream commit f47ee279d25fb0e010cae5d6e758e39b40eb6378 ] The h_clk clock in the Actions Semi S500 SoC clock driver has an invalid parent. Replace with the correct one. Fixes: ed6b4795ece4 ("clk: actions: Add clock driver for S500 SoC") Signed-off-by: Cristian Ciocal

[PATCH 5.7 140/204] iommu/vt-d: Enforce PASID devTLB field mask

2020-08-20 Thread Greg Kroah-Hartman
From: Liu Yi L [ Upstream commit 5f77d6ca5ca74e4b4a5e2e010f7ff50c45dea326 ] Set proper masks to avoid invalid input spillover to reserved bits. Signed-off-by: Liu Yi L Signed-off-by: Jacob Pan Signed-off-by: Lu Baolu Reviewed-by: Eric Auger Link: https://lore.kernel.org/r/20200724014925.155

[PATCH 5.7 125/204] rtw88: pci: disable aspm for platform inter-op with module parameter

2020-08-20 Thread Greg Kroah-Hartman
From: Yan-Hsuan Chuang [ Upstream commit 68aa716b7dd36f55e080da9e27bc594346334c41 ] Some platforms cannot read the DBI register successfully for the ASPM settings. After the read failed, the bus could be unstable, and the device just became unavailable [1]. For those platforms, the ASPM should b

[PATCH 5.7 152/204] clk: bcm2835: Do not use prediv with bcm2711s PLLs

2020-08-20 Thread Greg Kroah-Hartman
From: Nicolas Saenz Julienne [ Upstream commit f34e4651ce66a754f41203284acf09b28b9dd955 ] Contrary to previous SoCs, bcm2711 doesn't have a prescaler in the PLL feedback loop. Bypass it by zeroing fb_prediv_mask when running on bcm2711. Note that, since the prediv configuration bits were re-pur

[PATCH 5.7 155/204] openrisc: Fix oops caused when dumping stack

2020-08-20 Thread Greg Kroah-Hartman
From: Stafford Horne [ Upstream commit 57b8e277c33620e115633cdf700a260b55095460 ] When dumping a stack with 'cat /proc/#/stack' the kernel would oops. For example: # cat /proc/690/stack Unable to handle kernel access at virtual address 0x7fc60f58 Oops#: CPU #: 0

[PATCH 5.7 126/204] rtc: pl031: fix set_alarm by adding back call to alarm_irq_enable

2020-08-20 Thread Greg Kroah-Hartman
From: Sudeep Holla [ Upstream commit 4df2ef85f0efe44505f511ca5e4455585f53a2da ] Commit c8ff5841a90b ("rtc: pl031: switch to rtc_time64_to_tm/rtc_tm_to_time64") seemed to have accidentally removed the call to pl031_alarm_irq_enable from pl031_set_alarm while switching to 64-bit apis. Let us add

[PATCH 5.7 122/204] RDMA/counter: Only bind user QPs in auto mode

2020-08-20 Thread Greg Kroah-Hartman
From: Mark Zhang [ Upstream commit c9f557421e505f75da4234a6af8eff46bc08614b ] In auto mode only bind user QPs to a dynamic counter, since this feature is mainly used for system statistic and diagnostic purpose, while there's no need to counter kernel QPs so far. Fixes: 99fa331dc862 ("RDMA/count

[PATCH 5.7 131/204] ima: Fail rule parsing when appraise_flag=blacklist is unsupportable

2020-08-20 Thread Greg Kroah-Hartman
From: Tyler Hicks [ Upstream commit 5f3e92657bbfb63ad3109433d843c89996114b03 ] Verifying that a file hash is not blacklisted is currently only supported for files with appended signatures (modsig). In the future, this might change. For now, the "appraise_flag" option is only appropriate for ap

[PATCH 5.7 165/204] vdpa_sim: init iommu lock

2020-08-20 Thread Greg Kroah-Hartman
From: Michael S. Tsirkin [ Upstream commit 1e3e792650d2c0df8dd796906275b7c79e278664 ] The patch adding the iommu lock did not initialize it. The struct is zero-initialized so this is mostly a problem when using lockdep. Reported-by: kernel test robot Cc: Max Gurtovoy Fixes: 0ea9ee430e74 ("vdp

[PATCH 5.7 130/204] dm rq: dont call blk_mq_queue_stopped() in dm_stop_queue()

2020-08-20 Thread Greg Kroah-Hartman
From: Ming Lei [ Upstream commit e78c6cd49d741cfb49eaeb38998ba34d27bc ] dm_stop_queue() only uses blk_mq_quiesce_queue() so it doesn't formally stop the blk-mq queue; therefore there is no point making the blk_mq_queue_stopped() check -- it will never be stopped. In addition, even though dm

[PATCH 5.7 166/204] recordmcount: Fix build failure on non arm64

2020-08-20 Thread Greg Kroah-Hartman
From: Christophe Leroy [ Upstream commit 3df14264ad9930733a8166e5bd0eccc1727564bb ] Commit ea0eada45632 leads to the following build failure on powerpc: HOSTCC scripts/recordmcount scripts/recordmcount.c: In function 'arm64_is_fake_mcount': scripts/recordmcount.c:440: error: 'R_AARCH64_CALL2

[PATCH 5.7 172/204] net: qcom/emac: add missed clk_disable_unprepare in error path of emac_clks_phase1_init

2020-08-20 Thread Greg Kroah-Hartman
From: Wang Hai [ Upstream commit 50caa777a3a24d7027748e96265728ce748b41ef ] Fix the missing clk_disable_unprepare() before return from emac_clks_phase1_init() in the error handling case. Fixes: b9b17debc69d ("net: emac: emac gigabit ethernet controller driver") Reported-by: Hulk Robot Signed-o

[PATCH 5.7 156/204] scsi: lpfc: nvmet: Avoid hang / use-after-free again when destroying targetport

2020-08-20 Thread Greg Kroah-Hartman
From: Ewan D. Milne [ Upstream commit af6de8c60fe9433afa73cea6fcccdccd98ad3e5e ] We cannot wait on a completion object in the lpfc_nvme_targetport structure in the _destroy_targetport() code path because the NVMe/fc transport will free that structure immediately after the .targetport_delete() ca

[PATCH 5.7 173/204] nfs: Fix getxattr kernel panic and memory overflow

2020-08-20 Thread Greg Kroah-Hartman
From: Jeffrey Mitchell [ Upstream commit b4487b93545214a9db8cbf32e86411677b0cca21 ] Move the buffer size check to decode_attr_security_label() before memcpy() Only call memcpy() if the buffer is large enough Fixes: aa9c2669626c ("NFS: Client implementation of Labeled-NFS") Signed-off-by: Jeffre

[PATCH 5.7 170/204] s390/test_unwind: fix possible memleak in test_unwind()

2020-08-20 Thread Greg Kroah-Hartman
From: Wang Hai [ Upstream commit 75d3e7f4769d276a056efa1cc7f08de571fc9b4b ] test_unwind() misses to call kfree(bt) in an error path. Add the missed function call to fix it. Fixes: 0610154650f1 ("s390/test_unwind: print verbose unwinding results") Reported-by: Hulk Robot Signed-off-by: Wang Hai

[PATCH 5.7 167/204] vdpa: Fix pointer math bug in vdpasim_get_config()

2020-08-20 Thread Greg Kroah-Hartman
From: Dan Carpenter [ Upstream commit cf16fe9243bfa2863491026fc727618c7c593c84 ] If "offset" is non-zero then we end up copying from beyond the end of the config because of pointer math. We can fix this by casting the struct to a u8 pointer. Fixes: 2c53d0f64c06 ("vdpasim: vDPA device simulator

[PATCH 5.7 168/204] drm/vmwgfx: Use correct vmw_legacy_display_unit pointer

2020-08-20 Thread Greg Kroah-Hartman
From: Dan Carpenter [ Upstream commit 1d2c0c565bc0da25f5e899a862fb58e612b222df ] The "entry" pointer is an offset from the list head and it doesn't point to a valid vmw_legacy_display_unit struct. Presumably the intent was to point to the last entry. Also the "i++" wasn't used so I have remove

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