[PATCH 5.11 710/775] mmc: sdhci-esdhc-imx: fix kernel panic when remove module

2021-03-01 Thread Greg Kroah-Hartman
From: Frank Li commit a56f44138a2c57047f1ea94ea121af31c595132b upstream. In sdhci_esdhc_imx_remove() the SDHCI_INT_STATUS in read. Under some circumstances, this may be done while the device is runtime suspended, triggering the below splat. Fix the problem by adding a pm_runtime_get_sync(),

[PATCH 5.11 709/775] module: Ignore _GLOBAL_OFFSET_TABLE_ when warning for undefined symbols

2021-03-01 Thread Greg Kroah-Hartman
From: Fangrui Song commit ebfac7b778fac8b0e8e92ec91d0b055f046b4604 upstream. clang-12 -fno-pic (since https://github.com/llvm/llvm-project/commit/a084c0388e2a59b9556f2de008232da3f1d6) can emit `call __stack_chk_fail@PLT` instead of `call __stack_chk_fail` on x86. The two forms should have

[PATCH 5.11 708/775] 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.11 705/775] 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.11 704/775] hugetlb: fix copy_huge_page_from_user contig page struct assumption

2021-03-01 Thread Greg Kroah-Hartman
From: Mike Kravetz commit 3272cfc2525b3a2810a59312d7a1e6f04a0ca3ef upstream. page structs are not guaranteed to be contiguous for gigantic pages. The routine copy_huge_page_from_user can encounter gigantic pages, yet it assumes page structs are contiguous when copying pages from user space.

[PATCH 5.11 693/775] mtd: spi-nor: sfdp: Fix last erase region marking

2021-03-01 Thread Greg Kroah-Hartman
From: Takahiro Kuwano commit 9166f4af32db74e1544a2149aef231ff24515ea3 upstream. The place of spi_nor_region_mark_end() must be moved, because 'i' is re-used for the index of erase[]. Fixes: b038e8e3be72 ("mtd: spi-nor: parse SFDP Sector Map Parameter Table") Cc: sta...@vger.kernel.org

[PATCH 5.11 706/775] mm, compaction: make fast_isolate_freepages() stay within zone

2021-03-01 Thread Greg Kroah-Hartman
From: Vlastimil Babka commit 6e2b7044c199229a3d20cefbd3184968238c4184 upstream. Compaction always operates on pages from a single given zone when isolating both pages to migrate and freepages. Pageblock boundaries are intersected with zone boundaries to be safe in case zone starts or ends in

[PATCH 5.11 707/775] KVM: nSVM: fix running nested guests when npt=0

2021-03-01 Thread Greg Kroah-Hartman
From: Paolo Bonzini commit a04aead144fd938c2d9869eb187e5b9ea0009bae upstream. In case of npt=0 on host, nSVM needs the same .inject_page_fault tweak as VMX has, to make sure that shadow mmu faults are injected as vmexits. It is not clear why this is needed at all, but for now keep the same

[PATCH 5.11 703/775] hugetlb: fix update_and_free_page contig page struct assumption

2021-03-01 Thread Greg Kroah-Hartman
From: Mike Kravetz commit dbfee5aee7e54f83d96ceb8e3e80717fac62ad63 upstream. page structs are not guaranteed to be contiguous for gigantic pages. The routine update_and_free_page can encounter a gigantic page, yet it assumes page structs are contiguous when setting page flags in subpages. If

[PATCH 5.11 666/775] media: v4l: ioctl: Fix memory leak in video_usercopy

2021-03-01 Thread Greg Kroah-Hartman
From: Sakari Ailus commit fb18802a338b36f675a388fc03d2aa504a0d0899 upstream. When an IOCTL with argument size larger than 128 that also used array arguments were handled, two memory allocations were made but alas, only the latter one of them was released. This happened because there was only a

[PATCH 5.11 664/775] 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.11 665/775] media: i2c: max9286: fix access to unallocated memory

2021-03-01 Thread Greg Kroah-Hartman
From: Tomi Valkeinen commit e88ccf09e79cf33cac40316ba69c820d9eebc82b upstream. The asd allocated with v4l2_async_notifier_add_fwnode_subdev() must be of size max9286_asd, otherwise access to max9286_asd->source will go to unallocated memory. Fixes: 86d37bf31af6 ("media: i2c: max9286: Allocate

[PATCH 5.11 701/775] mm: memcontrol: fix swap undercounting in cgroup2

2021-03-01 Thread Greg Kroah-Hartman
From: Muchun Song commit cae3af62b33aa931427a0f211e04347b22180b36 upstream. When pages are swapped in, the VM may retain the swap copy to avoid repeated writes in the future. It's also retained if shared pages are faulted back in some processes, but not in others. During that time we have an

[PATCH 5.11 702/775] mm: memcontrol: fix get_active_memcg return value

2021-03-01 Thread Greg Kroah-Hartman
From: Muchun Song commit 1685bde6b9af55923180a76152036c7fb7176db0 upstream. We use a global percpu int_active_memcg variable to store the remote memcg when we are in the interrupt context. But get_active_memcg always return the current->active_memcg or root_mem_cgroup. The remote memcg (set

[PATCH 5.11 687/775] arm64 module: set plt* section addresses to 0x0

2021-03-01 Thread Greg Kroah-Hartman
From: Shaoying Xu commit f5c6d0fcf90ce07ee0d686d465b19b247ebd5ed7 upstream. These plt* and .text.ftrace_trampoline sections specified for arm64 have non-zero addressses. Non-zero section addresses in a relocatable ELF would confuse GDB when it tries to compute the section offsets and it ends up

[PATCH 5.11 688/775] arm64: spectre: Prevent lockdep splat on v4 mitigation enable path

2021-03-01 Thread Greg Kroah-Hartman
From: Will Deacon commit a2c42bbabbe260b7626d8459093631a6e16ee0ee upstream. The Spectre-v4 workaround is re-configured when resuming from suspend, as the firmware may have re-enabled the mitigation despite the user previously asking for it to be disabled. Enabling or disabling the workaround

[PATCH 5.11 692/775] coresight: etm4x: Handle accesses to TRCSTALLCTLR

2021-03-01 Thread Greg Kroah-Hartman
From: Suzuki K Poulose commit f72896063396b0cb205cbf0fd76ec6ab3ca11c8a upstream. TRCSTALLCTLR register is only implemented if TRCIDR3.STALLCTL == 0b1 Make sure the driver touches the register only it is implemented. Link:

[PATCH 5.11 685/775] arm64: kexec_file: fix memory leakage in create_dtb() when fdt_open_into() fails

2021-03-01 Thread Greg Kroah-Hartman
From: qiuguorui1 commit 656d1d58d8e0958d372db86c24f0b2ea36f50888 upstream. in function create_dtb(), if fdt_open_into() fails, we need to vfree buf before return. Fixes: 52b2a8af7436 ("arm64: kexec_file: load initrd and device-tree") Cc: sta...@vger.kernel.org # v5.0 Signed-off-by: qiuguorui1

[PATCH 5.11 684/775] mailbox: arm_mhuv2: Skip calling kfree() with invalid pointer

2021-03-01 Thread Greg Kroah-Hartman
From: Viresh Kumar commit 6b50df2b8c208a04d44b8df5b7baaf668ceb8fc3 upstream. It is possible that 'data' passed to kfree() is set to a error value instead of allocated space. Make sure it doesn't get called with invalid pointer. Fixes: 5a6338cce9f4 ("mailbox: arm_mhuv2: Add driver") Cc: v5.11

[PATCH 5.11 658/775] pstore: Fix typo in compression option name

2021-03-01 Thread Greg Kroah-Hartman
From: Jiri Bohac commit 19d8e9149c27b689c6224f5c84b96a159342195a upstream. Both pstore_compress() and decompress_record() use a mistyped config option name ("PSTORE_COMPRESSION" instead of "PSTORE_COMPRESS"). As a result compression and decompression of pstore records was always disabled. Use

[PATCH 5.11 663/775] staging: rtl8188eu: Add Edimax EW-7811UN V2 to device table

2021-03-01 Thread Greg Kroah-Hartman
From: Martin Kaiser commit 7a8d2f1908a59003e55ef8691d09efb7fbc51625 upstream. The Edimax EW-7811UN V2 uses an RTL8188EU chipset and works with this driver. Signed-off-by: Martin Kaiser Cc: stable Link: https://lore.kernel.org/r/20210204085217.9743-1-mar...@kaiser.cx Signed-off-by: Greg

[PATCH 5.11 667/775] media: ir_toy: add another IR Droid device

2021-03-01 Thread Greg Kroah-Hartman
From: Sean Young commit 4487e0215560392bd11c9de08d60824d72c89cd9 upstream. This device is also supported. Cc: sta...@vger.kernel.org Tested-by: Georgi Bakalski Reported-by: Georgi Bakalski Signed-off-by: Sean Young Reviewed-by: Greg Kroah-Hartman Signed-off-by: Mauro Carvalho Chehab

[PATCH 5.11 662/775] 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.11 686/775] arm64: uprobe: Return EOPNOTSUPP for AARCH32 instruction probing

2021-03-01 Thread Greg Kroah-Hartman
From: He Zhe commit d47422d953e258ad587b5edf2274eb95d08bdc7d upstream. As stated in linux/errno.h, ENOTSUPP should never be seen by user programs. When we set up uprobe with 32-bit perf and arm64 kernel, we would see the following vague error without useful hint. The sys_perf_event_open()

[PATCH 5.11 661/775] staging/mt7621-dma: mtk-hsdma.c->hsdma-mt7621.c

2021-03-01 Thread Greg Kroah-Hartman
From: Ilya Lipnitskiy commit 1f92798cbe7fe923479cff754dd06dd23d352e36 upstream. Also use KBUILD_MODNAME for module name. This driver is only used by RALINK MIPS MT7621 SoCs. Tested by building against that target using OpenWrt with Linux 5.10.10. Fixes the following error: error: the

[PATCH 5.11 690/775] 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 689/775] riscv: Disable KSAN_SANITIZE for vDSO

2021-03-01 Thread Greg Kroah-Hartman
From: Tobias Klauser commit f3d60f2a25e4417e1676161fe42115de3e3f98a2 upstream. We use the generic C VDSO implementations of a handful of clock-related functions. When kasan is enabled this results in asan stub calls that are unlikely to be resolved by userspace, this just disables KASAN when

[PATCH 5.11 676/775] rcu: Pull deferred rcuog wake up to rcu_eqs_enter() callers

2021-03-01 Thread Greg Kroah-Hartman
From: Frederic Weisbecker commit 54b7429efffc99e845ba9381bee3244f012a06c2 upstream. Deferred wakeup of rcuog kthreads upon RCU idle mode entry is going to be handled differently whether initiated by idle, user or guest. Prepare with pulling that control up to rcu_eqs_enter() callers.

[PATCH 5.11 677/775] rcu/nocb: Perform deferred wake up before last idles need_resched() check

2021-03-01 Thread Greg Kroah-Hartman
From: Frederic Weisbecker commit 43789ef3f7d61aa7bed0cb2764e588fc990c30ef upstream. Entering RCU idle mode may cause a deferred wake up of an RCU NOCB_GP kthread (rcuog) to be serviced. Usually a local wake up happening while running the idle task is handled in one of the need_resched() checks

[PATCH 5.11 670/775] 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.11 648/775] crypto: sun4i-ss - checking sg length is not sufficient

2021-03-01 Thread Greg Kroah-Hartman
From: Corentin Labbe commit 7bdcd851fa7eb66e8922aa7f6cba9e2f2427a7cf upstream. The optimized cipher function need length multiple of 4 bytes. But it get sometimes odd length. This is due to SG data could be stored with an offset. So the fix is to check also if the offset is aligned with 4

[PATCH 5.11 683/775] iommu/arm-smmu-qcom: Fix mask extraction for bootloader programmed SMRs

2021-03-01 Thread Greg Kroah-Hartman
From: Isaac J. Manjarres commit dead723e6f049e9fb6b05e5b93456982798ea961 upstream. When extracting the mask for a SMR that was programmed by the bootloader, the SMR's valid bit is also extracted and is treated as part of the mask, which is not correct. Consider the scenario where an SMMU master

[PATCH 5.11 625/775] 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.11 678/775] rcu/nocb: Trigger self-IPI on late deferred wake up before user resume

2021-03-01 Thread Greg Kroah-Hartman
From: Frederic Weisbecker commit f8bb5cae9616224a39cbb399de382d36ac41df10 upstream. Entering RCU idle mode may cause a deferred wake up of an RCU NOCB_GP kthread (rcuog) to be serviced. Unfortunately the call to rcu_user_enter() is already past the last rescheduling opportunity before we

[PATCH 5.11 675/775] powerpc/prom: Fix "ibm,arch-vec-5-platform-support" scan

2021-03-01 Thread Greg Kroah-Hartman
From: Cédric Le Goater commit ed5b00a05c2ae95b59adc3442f45944ec632e794 upstream. The "ibm,arch-vec-5-platform-support" property is a list of pairs of bytes representing the options and values supported by the platform firmware. At boot time, Linux scans this list and activates the available

[PATCH 5.11 660/775] arm64: dts: agilex: fix phy interface bit shift for gmac1 and gmac2

2021-03-01 Thread Greg Kroah-Hartman
From: Dinh Nguyen commit b7ff3a447d100c999d9848353ef8a4046831d893 upstream. The shift for the phy_intf_sel bit in the system manager for gmac1 and gmac2 should be 0. Fixes: 2f804ba7aa9ee ("arm64: dts: agilex: Add SysMgr to Ethernet nodes") Cc: sta...@vger.kernel.org Signed-off-by: Dinh Nguyen

[PATCH 5.11 682/775] 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.11 679/775] entry: Explicitly flush pending rcuog wakeup before last rescheduling point

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

[PATCH 5.11 681/775] kprobes: Fix to delay the kprobes jump optimization

2021-03-01 Thread Greg Kroah-Hartman
From: Masami Hiramatsu commit c85c9a2c6e368dc94907e63babb18a9788e5c9b6 upstream. Commit 36dadef23fcc ("kprobes: Init kprobes in early_initcall") moved the kprobe setup in early_initcall(), which includes kprobe jump optimization. The kprobes jump optimizer involves synchronize_rcu_tasks() which

[PATCH 5.11 680/775] 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.11 674/775] x86/entry: Fix instrumentation annotation

2021-03-01 Thread Greg Kroah-Hartman
From: Thomas Gleixner commit 15f720aabe71a5662c4198b22532d95bbeec80ef upstream. Embracing a callout into instrumentation_begin() / instrumentation_begin() does not really make sense. Make the latter instrumentation_end(). Fixes: 2f6474e4636b ("x86/entry: Switch XEN/PV hypercall entry to

[PATCH 5.11 671/775] x86/virt: Eat faults on VMXOFF in reboot flows

2021-03-01 Thread Greg Kroah-Hartman
From: Sean Christopherson commit aec511ad153556640fb1de38bfe00c69464f997f upstream. Silently ignore all faults on VMXOFF in the reboot flows as such faults are all but guaranteed to be due to the CPU not being in VMX root. Because (a) VMXOFF may be executed in NMI context, e.g. after VMXOFF but

[PATCH 5.11 673/775] x86/fault: Fix AMD erratum #91 errata fixup for user code

2021-03-01 Thread Greg Kroah-Hartman
From: Andy Lutomirski commit 35f1c89b0cce247bf0213df243ed902989b1dcda upstream. The recent rework of probe_kernel_address() and its conversion to get_kernel_nofault() inadvertently broke is_prefetch(). Before this change, probe_kernel_address() was used as a sloppy "read user or kernel memory"

[PATCH 5.11 659/775] dts64: mt7622: fix slow sd card access

2021-03-01 Thread Greg Kroah-Hartman
From: Frank Wunderlich commit dc2e76175417e69c41d927dba75a966399f18354 upstream. Fix extreme slow speed (200MB takes ~20 min) on writing sdcard on bananapi-r64 by adding reset-control for mmc1 like it's done for mmc0/emmc. Fixes: 2c002a3049f7 ("arm64: dts: mt7622: add mmc related device

[PATCH 5.11 668/775] media: ipu3-cio2: Fix mbus_code processing in cio2_subdev_set_fmt()

2021-03-01 Thread Greg Kroah-Hartman
From: Pavel Machek commit 334de4b45892f7e67074e1b1b2ac36fd3e091118 upstream. Loop was useless as it would always exit on the first iteration. Fix it with right condition. Signed-off-by: Pavel Machek (CIP) Fixes: a86cf9b29e8b ("media: ipu3-cio2: Validate mbus format in setting subdev format")

[PATCH 5.11 634/775] 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.11 669/775] media: marvell-ccic: power up the device on mclk enable

2021-03-01 Thread Greg Kroah-Hartman
From: Lubomir Rintel commit 655ae29da72a693cf294bba3c3322e662ff75bd3 upstream. Writing to REG_CLKCTRL with the power off causes a hang. Enable the device first. Cc: sta...@vger.kernel.org # 5.10+ Signed-off-by: Lubomir Rintel Signed-off-by: Sakari Ailus Signed-off-by: Mauro Carvalho Chehab

[PATCH 5.11 672/775] x86/reboot: Force all cpus to exit VMX root if VMX is supported

2021-03-01 Thread Greg Kroah-Hartman
From: Sean Christopherson commit ed72736183c45a413a8d6974dd04be90f514cb6b upstream. Force all CPUs to do VMXOFF (via NMI shootdown) during an emergency reboot if VMX is _supported_, as VMX being off on the current CPU does not prevent other CPUs from being in VMX root (post-VMXON). This fixes

[PATCH 5.11 649/775] crypto: sun4i-ss - IV register does not work on A10 and A13

2021-03-01 Thread Greg Kroah-Hartman
From: Corentin Labbe commit b756f1c8fc9d84e3f546d7ffe056c5352f4aab05 upstream. Allwinner A10 and A13 SoC have a version of the SS which produce invalid IV in IVx register. Instead of adding a variant for those, let's convert SS to produce IV directly from data. Fixes: 6298e948215f2 ("crypto:

Re: [PATCH] drivers: scsi: qla4xxx: Fix a spello in the file qla4xxx/ql4_os.c

2021-03-01 Thread Bhaskar Chowdhury
On 08:56 Mon 01 Mar 2021, Randy Dunlap wrote: On 3/1/21 5:17 AM, Bhaskar Chowdhury wrote: s/circuting/circuiting/ Signed-off-by: Bhaskar Chowdhury Acked-by: Randy Dunlap However: In lots of your patches, the subject begins with drivers: and we don't need that. See the SCSI qla4xxx

[PATCH 5.11 629/775] tpm_tis: Fix check_locality for correct locality acquisition

2021-03-01 Thread Greg Kroah-Hartman
From: James Bottomley commit 3d9ae54af1d02a7c0edc55c77d7df2b921e58a87 upstream. The TPM TIS specification says the TPM signals the acquisition of locality when the TMP_ACCESS_REQUEST_USE bit goes to one *and* the TPM_ACCESS_REQUEST_USE bit goes to zero. Currently we only check the former not

[PATCH 5.11 647/775] crypto: michael_mic - fix broken misalignment handling

2021-03-01 Thread Greg Kroah-Hartman
From: Ard Biesheuvel commit e1b2d980f03b833442768c1987d5ad0b9a58cfe7 upstream. The Michael MIC driver uses the cra_alignmask to ensure that pointers presented to its update and finup/final methods are 32-bit aligned. However, due to the way the shash API works, this is no guarantee that the

[PATCH 5.11 650/775] crypto: sun4i-ss - handle BigEndian for cipher

2021-03-01 Thread Greg Kroah-Hartman
From: Corentin Labbe commit 5ab6177fa02df15cd8a02a1f1fb361d2d5d8b946 upstream. Ciphers produce invalid results on BE. Key and IV need to be written in LE. Fixes: 6298e948215f2 ("crypto: sunxi-ss - Add Allwinner Security System crypto accelerator") Cc: Signed-off-by: Corentin Labbe

[PATCH 5.11 651/775] crypto: sun4i-ss - initialize need_fallback

2021-03-01 Thread Greg Kroah-Hartman
From: Corentin Labbe commit 4ec8977b921fd9d512701e009ce8082cb94b5c1c upstream. The need_fallback is never initialized and seem to be always true at runtime. So all hardware operations are always bypassed. Fixes: 0ae1f46c55f87 ("crypto: sun4i-ss - fallback when length is not multiple of

[PATCH 5.11 630/775] 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.11 631/775] KEYS: trusted: Fix incorrect handling of tpm_get_random()

2021-03-01 Thread Greg Kroah-Hartman
From: Jarkko Sakkinen commit 5df16caada3fba3b21cb09b85cdedf99507f4ec1 upstream. When tpm_get_random() was introduced, it defined the following API for the return value: 1. A positive value tells how many bytes of random data was generated. 2. A negative value on error. However, in the call

[PATCH 5.11 633/775] KEYS: trusted: Reserve TPM for seal and unseal operations

2021-03-01 Thread Greg Kroah-Hartman
From: Jarkko Sakkinen commit 8c657a0590de585b1115847c17b34a58025f2f4b upstream. When TPM 2.0 trusted keys code was moved to the trusted keys subsystem, the operations were unwrapped from tpm_try_get_ops() and tpm_put_ops(), which are used to take temporarily the ownership of the TPM chip. The

[PATCH 5.11 646/775] crypto: aesni - prevent misaligned buffers on the stack

2021-03-01 Thread Greg Kroah-Hartman
From: Ard Biesheuvel commit a13ed1d15b07a04b1f74b2df61ff7a5e47f45dd8 upstream. The GCM mode driver uses 16 byte aligned buffers on the stack to pass the IV to the asm helpers, but unfortunately, the x86 port does not guarantee that the stack pointer is 16 byte aligned upon entry in the first

[PATCH 5.11 655/775] arm64: ptrace: Fix seccomp of traced syscall -1 (NO_SYSCALL)

2021-03-01 Thread Greg Kroah-Hartman
From: Timothy E Baldwin commit df84fe94708985cdfb78a83148322bcd0a699472 upstream. Since commit f086f67485c5 ("arm64: ptrace: add support for syscall emulation"), if system call number -1 is called and the process is being traced with PTRACE_SYSCALL, for example by strace, the seccomp check is

[PATCH 5.11 654/775] seccomp: Add missing return in non-void function

2021-03-01 Thread Greg Kroah-Hartman
From: Paul Cercueil commit 04b38d012556199ba4c31195940160e0c44c64f0 upstream. We don't actually care about the value, since the kernel will panic before that; but a value should nonetheless be returned, otherwise the compiler will complain. Fixes: 8112c4f140fa ("seccomp: remove 2-phase API")

[PATCH 5.11 632/775] KEYS: trusted: Fix migratable=1 failing

2021-03-01 Thread Greg Kroah-Hartman
From: Jarkko Sakkinen commit 8da7520c80468c48f981f0b81fc1be6599e3b0ad upstream. Consider the following transcript: $ keyctl add trusted kmk "new 32 blobauth=helloworld keyhandle=8000 migratable=1" @u add_key: Invalid argument The documentation has the following description:

[PATCH 5.11 628/775] erofs: initialized fields can only be observed after bit is set

2021-03-01 Thread Greg Kroah-Hartman
From: Gao Xiang commit ce063129181312f8781a047a50be439c5859747b upstream. Currently, although set_bit() & test_bit() pairs are used as a fast- path for initialized configurations. However, these atomic ops are actually relaxed forms. Instead, load-acquire & store-release form is needed to make

[PATCH 5.11 645/775] crypto: arm64/sha - add missing module aliases

2021-03-01 Thread Greg Kroah-Hartman
From: Ard Biesheuvel commit 0df07d8117c3576f1603b05b84089742a118d10a upstream. The accelerated, instruction based implementations of SHA1, SHA2 and SHA3 are autoloaded based on CPU capabilities, given that the code is modest in size, and widely used, which means that resolving the algo name,

[PATCH 5.11 644/775] drm/i915/gt: Correct surface base address for renderclear

2021-03-01 Thread Greg Kroah-Hartman
From: Chris Wilson commit 81ce8f04aa96f7f6cae05770f68b5d15be91f5a2 upstream. The surface_state_base is an offset into the batch, so we need to pass the correct batch address for STATE_BASE_ADDRESS. Fixes: 47f8253d2b89 ("drm/i915/gen7: Clear all EU/L3 residual contexts") Signed-off-by: Chris

[PATCH 5.11 657/775] drivers/misc/vmw_vmci: restrict too big queue size in qp_host_alloc_queue

2021-03-01 Thread Greg Kroah-Hartman
From: Sabyrzhan Tasbolatov commit 2fd10bcf0310b9525b2af9e1f7aa9ddd87c3772e upstream. syzbot found WARNING in qp_broker_alloc[1] in qp_host_alloc_queue() when num_pages is 0x11, giving queue_size + queue_page_size bigger than KMALLOC_MAX_SIZE for kzalloc(), resulting order >= MAX_ORDER

[PATCH 5.11 653/775] soc: samsung: exynos-asv: handle reading revision register error

2021-03-01 Thread Greg Kroah-Hartman
From: Krzysztof Kozlowski commit 4561560dfb4f847a0b327d48bdd1f45bf1b6261f upstream. If regmap_read() fails, the product_id local variable will contain random value from the stack. Do not try to parse such value and fail the ASV driver probe. Fixes: 5ea428595cc5 ("soc: samsung: Add Exynos

[PATCH 5.11 652/775] 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.11 656/775] misc: rtsx: init of rts522a add OCP power off when no card is present

2021-03-01 Thread Greg Kroah-Hartman
From: Ricky Wu commit 920fd8a70619074eac7687352c8f1c6f3c2a64a5 upstream. Power down OCP for power consumption when no SD/MMC card is present Cc: sta...@vger.kernel.org Signed-off-by: Ricky Wu Link: https://lore.kernel.org/r/20210204083115.9471-1-ricky...@realtek.com Signed-off-by: Greg

[PATCH 5.11 640/775] btrfs: handle space_info::total_bytes_pinned inside the delayed ref itself

2021-03-01 Thread Greg Kroah-Hartman
From: Josef Bacik commit 2187374f35fe9cadbddaa9fcf0c4121365d914e8 upstream. Currently we pass things around to figure out if we maybe freeing data based on the state of the delayed refs head. This makes the accounting sort of confusing and hard to follow, as it's distinctly separate from the

Re: [PATCH v2 3/3] mm: use PF_ONLY_HEAD for PG_active and PG_unevictable

2021-03-01 Thread Hugh Dickins
On Mon, 1 Mar 2021, Yu Zhao wrote: > On Mon, Mar 01, 2021 at 02:50:07PM +0300, Kirill A. Shutemov wrote: > > On Fri, Feb 26, 2021 at 12:13:14PM +, Matthew Wilcox wrote: > > > On Fri, Feb 26, 2021 at 02:17:18AM -0700, Yu Zhao wrote: > > > > All places but one test, set or clear PG_active and

[PATCH 5.11 637/775] btrfs: abort the transaction if we fail to inc ref in btrfs_copy_root

2021-03-01 Thread Greg Kroah-Hartman
From: Josef Bacik commit 867ed321f90d06aaba84e2c91de51cd3038825ef upstream. While testing my error handling patches, I added a error injection site at btrfs_inc_extent_ref, to validate the error handling I added was doing the correct thing. However I hit a pretty ugly corruption while doing

[PATCH 5.11 638/775] btrfs: fix reloc root leak with 0 ref reloc roots on recovery

2021-03-01 Thread Greg Kroah-Hartman
From: Josef Bacik commit c78a10aebb275c38d0cfccae129a803fe622e305 upstream. When recovering a relocation, if we run into a reloc root that has 0 refs we simply add it to the reloc_control->reloc_roots list, and then clean it up later. The problem with this is __del_reloc_root() doesn't do

[PATCH 5.11 643/775] drm/i915/gt: Flush before changing register state

2021-03-01 Thread Greg Kroah-Hartman
From: Chris Wilson commit d5109f739c9f14a3bda249cb48b16de1065932f0 upstream. Flush; invalidate; change registers; invalidate; flush. Will this finally work on every device? Or will Baytrail complain again? On the positive side, we immediately see the benefit of having hsw-gt1 in CI. Fixes:

[PATCH 5.11 592/775] phy: lantiq: rcu-usb2: wait after clock enable

2021-03-01 Thread Greg Kroah-Hartman
From: Mathias Kresin commit 36acd5e24e3000691fb8d1ee31cf959cb1582d35 upstream. Commit 65dc2e725286 ("usb: dwc2: Update Core Reset programming flow.") revealed that the phy isn't ready immediately after enabling it's clocks. The dwc2_check_core_version() fails and the dwc2 usb driver errors out.

[PATCH 5.11 639/775] btrfs: splice remaining dirty_bgs onto the transaction dirty bg list

2021-03-01 Thread Greg Kroah-Hartman
From: Josef Bacik commit 938fcbfb0cbcf532a1869efab58e6009446b1ced upstream. While doing error injection testing with my relocation patches I hit the following assert: assertion failed: list_empty(_group->dirty_list), in fs/btrfs/block-group.c:3356 [ cut here ]

[PATCH 5.11 626/775] ASoC: siu: Fix build error by a wrong const prefix

2021-03-01 Thread Greg Kroah-Hartman
From: Takashi Iwai commit ae07f5c7c5e9ebca5b9d6471bb4b99a9da5c6d88 upstream. A const prefix was put wrongly in the middle at the code refactoring commit 932eaf7c7904 ("ASoC: sh: siu_pcm: remove snd_pcm_ops"), which leads to a build error as: sound/soc/sh/siu_pcm.c:546:8: error: expected '{'

[PATCH 5.11 635/775] 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.11 599/775] ALSA: hda: Add another CometLake-H PCI ID

2021-03-01 Thread Greg Kroah-Hartman
From: Kai Vehmanen commit 0d3070f5e6551d8a759619e85736e49a3bf40398 upstream. Add one more HD Audio PCI ID for CometLake-H PCH. Signed-off-by: Kai Vehmanen Reviewed-by: Pierre-Louis Bossart Cc: Link: https://lore.kernel.org/r/20210212151022.2568567-1-kai.vehma...@linux.intel.com

[PATCH 5.11 597/775] ALSA: usb-audio: Add implicit fb quirk for BOSS GP-10

2021-03-01 Thread Greg Kroah-Hartman
From: Takashi Iwai commit 15447b64789d9ade71eb374d5ae1f37d0bbce0bd upstream. BOSS GP-10 with 0582:0185 requires the similar quirk to make the implicit feedback working like other BOSS devices. Reported-by: Keith Milner Cc: Link: https://lore.kernel.org/r/20210214154251.10750-1-ti...@suse.de

[PATCH 5.11 601/775] ALSA: hda/realtek: modify EAPD in the ALC886

2021-03-01 Thread Greg Kroah-Hartman
From: PeiSen Hou commit 4841b8e6318a7f0ae57c4e5ec09032ea057c97a8 upstream. Modify 0x20 index 7 bit 5 to 1, make the 0x15 EAPD the same as 0x14. Signed-off-by: PeiSen Hou Cc: Link: https://lore.kernel.org/r/e62c5058957f48d8b8953e97135ff...@realtek.com Signed-off-by: Takashi Iwai

[PATCH 5.11 642/775] btrfs: fix extent buffer leak on failure to copy root

2021-03-01 Thread Greg Kroah-Hartman
From: Filipe Manana commit 72c9925f87c8b74f36f8e75a4cd93d964538d3ca upstream. At btrfs_copy_root(), if the call to btrfs_inc_ref() fails we end up returning without unlocking and releasing our reference on the extent buffer named "cow" we previously allocated with btrfs_alloc_tree_block(). So

[PATCH 5.11 641/775] btrfs: account for new extents being deleted in total_bytes_pinned

2021-03-01 Thread Greg Kroah-Hartman
From: Josef Bacik commit 81e75ac74ecba929d1e922bf93f9fc467232e39f upstream. My recent patch set "A variety of lock contention fixes", found here https://lore.kernel.org/linux-btrfs/cover.1608319304.git.jo...@toxicpanda.com/ (Tracked in https://github.com/btrfs/linux/issues/86) that reduce

[PATCH 5.11 636/775] btrfs: add asserts for deleting backref cache nodes

2021-03-01 Thread Greg Kroah-Hartman
From: Josef Bacik commit eddda68d97732ce05ca145f8e85e8a447f65cdad upstream. A weird KASAN problem that Zygo reported could have been easily caught if we checked for basic things in our backref freeing code. We have two methods of freeing a backref node - btrfs_backref_free_node: this just is

[PATCH 5.11 624/775] 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

[PATCH 5.11 596/775] ALSA: usb-audio: Dont avoid stopping the stream at disconnection

2021-03-01 Thread Greg Kroah-Hartman
From: Takashi Iwai commit 257d2d7e9e798305d65825cb82b0a7d1c0511e89 upstream. In the later patch, we're going to issue the PCM sync_stop calls at disconnection. But currently the USB-audio driver can't handle it because it has a check of shutdown flag for stopping the URBs. This is basically

[PATCH 5.11 598/775] ALSA: fireface: fix to parse sync status register of latter protocol

2021-03-01 Thread Greg Kroah-Hartman
From: Takashi Sakamoto commit c50bfc8a6866775be39d7e747e83e8a5a9051e2e upstream. Fireface UCX, UFX, and FF802 are categorized for latter protocol of the series. Current support for FF802 (and UFX) includes failure to parse sync status register and results in EIO. Further investigation figures

[PATCH 5.11 600/775] ALSA: hda/hdmi: Drop bogus check at closing a stream

2021-03-01 Thread Greg Kroah-Hartman
From: Takashi Iwai commit 056a3da5d07fc5d3ceacfa2cdf013c9d8df630bd upstream. Some users reported the kernel WARNING with stack traces from hdmi_pcm_close(), and it's the line checking the per_cvt->assigned flag. This used to be a valid check in the past because the flag was turned on/off only

[PATCH 5.11 623/775] drm/sched: Cancel and flush all outstanding jobs before finish.

2021-03-01 Thread Greg Kroah-Hartman
From: Andrey Grodzovsky commit e582951baabba3e278c97169d0acc1e09b24a72e upstream. To avoid any possible use after free. Signed-off-by: Andrey Grodzovsky Reviewed-by: Christian König Link: https://patchwork.freedesktop.org/patch/414814/ CC: sta...@vger.kernel.org Signed-off-by: Christian

[PATCH 5.11 622/775] 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.11 615/775] Revert "drm/amd/display: reuse current context instead of recreating one"

2021-03-01 Thread Greg Kroah-Hartman
From: Anson Jacob commit efc8278eecfd5e6fa36c5d41e71d038f534fe107 upstream. This reverts commit 8866a67ab86cc0812e65c04f1ef02bcc41e24d68. Reason for revert: This breaks hotplug of HDMI on some systems, resulting in a blank screen. Caused general hangs on boot/hotplugs. Bug:

[PATCH 5.11 617/775] drm/amdgpu: fix CGTS_TCC_DISABLE register offset on gfx10.3

2021-03-01 Thread Greg Kroah-Hartman
From: Marek Olšák commit 4112c00354004cbb1bf56f0114fa9951bf6b13ed upstream. This fixes incorrect TCC harvesting info reported to userspace. The impact was a very very tiny performance degradation (unnecessary GL2 cache flushes). Signed-off-by: Marek Olšák Reviewed-by: Hawking Zhang

[PATCH 5.11 619/775] drm/amdgpu: fix shutdown and poweroff process failed with s0ix

2021-03-01 Thread Greg Kroah-Hartman
From: Prike Liang commit b092b19602cfd47de1eeeb3a1b03822afd86b136 upstream. In the shutdown and poweroff opt on the s0i3 system we still need un-gate the gfx clock gating and power gating before destory amdgpu device. Fixes: 628c36d7b238e2 ("drm/amdgpu: update amdgpu device suspend/resume

[PATCH 5.11 605/775] MIPS: VDSO: Use CLANG_FLAGS instead of filtering out --target=

2021-03-01 Thread Greg Kroah-Hartman
From: Nathan Chancellor commit 76d7fff22be3e4185ee5f9da2eecbd8188e76b2c upstream. Commit ee67855ecd9d ("MIPS: vdso: Allow clang's --target flag in VDSO cflags") allowed the '--target=' flag from the main Makefile to filter through to the vDSO. However, it did not bring any of the other clang

[PATCH 5.11 618/775] drm/amdgpu: Set reference clock to 100Mhz on Renoir (v2)

2021-03-01 Thread Greg Kroah-Hartman
From: Alex Deucher commit 6e80fb8ab04f6c4f377e2fd422bdd1855beb7371 upstream. Fixes the rlc reference clock used for GPU timestamps. Value is 100Mhz. Confirmed with hardware team. v2: reword commit message. Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1480 Acked-by: Christian König

[PATCH 5.11 595/775] ALSA: usb-audio: More strict state change in EP

2021-03-01 Thread Greg Kroah-Hartman
From: Takashi Iwai commit 5c2b301476ec493be15546f05e23414e2aa9d472 upstream. The endpoint management has bit flags to indicate the current state, and we're dealing two things: the running bit and the stopping bit. There is a thin window in transition from the running to the stopping in

[PATCH 5.11 610/775] 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.11 620/775] drm/ttm: Fix a memory leak

2021-03-01 Thread Greg Kroah-Hartman
From: xinhui pan commit 7a8a4b0729a8807e37196e44629b31ee03f88872 upstream. Free the memory on failure. Also no need to re-alloc memory on retry. Signed-off-by: xinhui pan Link: https://patchwork.freedesktop.org/patch/msgid/20210219042547.44855-1-xinhui@amd.com Reviewed-by: Christian

[PATCH 5.11 621/775] drm/nouveau/kms: handle mDP connectors

2021-03-01 Thread Greg Kroah-Hartman
From: Karol Herbst commit d1f5a3fc85566e9ddce9361ef180f070367e6eab upstream. In some cases we have the handle those explicitly as the fallback connector type detection fails and marks those as eDP connectors. Attempting to use such a connector with mutter leads to a crash of mutter as it ends

[PATCH 5.11 594/775] ALSA: usb-audio: Handle invalid running state at releasing EP

2021-03-01 Thread Greg Kroah-Hartman
From: Takashi Iwai commit d6cda4655e2a7612a1e48c49795a5330abc01c5a upstream. When we stop an endpoint in release_urbs(), it ignores the inconsistent endpoint state and tries to release the resources. This shouldn't happen in theory, but it's still safer to abort the release and let the caller

[PATCH V2] docs: sphinx: Fix couple of spellings in the file rstFlatTable.py

2021-03-01 Thread Bhaskar Chowdhury
s/automaticly/automatically/ s/buidler/builder/ ..and a sentence construction fix. Signed-off-by: Bhaskar Chowdhury --- Changes from V1: Incorporating Randy's observations ...i.e sentence construction Documentation/sphinx/rstFlatTable.py | 4 ++-- 1 file changed, 2 insertions(+), 2

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