From: Sasha Levin Date: Sun, 23 Aug 2020 21:41:33 +0000 (-0400) Subject: Fixes for 4.19 X-Git-Tag: v4.4.234~42 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=50beba1ab806f97b2bdcfec84034700dbe775298;p=thirdparty%2Fkernel%2Fstable-queue.git Fixes for 4.19 Signed-off-by: Sasha Levin --- diff --git a/queue-4.19/alpha-fix-annotation-of-io-read-write-16-32-be.patch b/queue-4.19/alpha-fix-annotation-of-io-read-write-16-32-be.patch new file mode 100644 index 00000000000..69e9f049b75 --- /dev/null +++ b/queue-4.19/alpha-fix-annotation-of-io-read-write-16-32-be.patch @@ -0,0 +1,57 @@ +From 2648fb0267c34b16ecbafc23fcd1c92bb5a28bee Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 11 Aug 2020 18:33:54 -0700 +Subject: alpha: fix annotation of io{read,write}{16,32}be() + +From: Luc Van Oostenryck + +[ Upstream commit bd72866b8da499e60633ff28f8a4f6e09ca78efe ] + +These accessors must be used to read/write a big-endian bus. The value +returned or written is native-endian. + +However, these accessors are defined using be{16,32}_to_cpu() or +cpu_to_be{16,32}() to make the endian conversion but these expect a +__be{16,32} when none is present. Keeping them would need a force cast +that would solve nothing at all. + +So, do the conversion using swab{16,32}, like done in asm-generic for +similar situations. + +Reported-by: kernel test robot +Signed-off-by: Luc Van Oostenryck +Signed-off-by: Andrew Morton +Cc: Richard Henderson +Cc: Ivan Kokshaysky +Cc: Matt Turner +Cc: Stephen Boyd +Cc: Arnd Bergmann +Link: http://lkml.kernel.org/r/20200622114232.80039-1-luc.vanoostenryck@gmail.com +Signed-off-by: Linus Torvalds +Signed-off-by: Sasha Levin +--- + arch/alpha/include/asm/io.h | 8 ++++---- + 1 file changed, 4 insertions(+), 4 deletions(-) + +diff --git a/arch/alpha/include/asm/io.h b/arch/alpha/include/asm/io.h +index eb09d5aee9106..0bba9e991189d 100644 +--- a/arch/alpha/include/asm/io.h ++++ b/arch/alpha/include/asm/io.h +@@ -507,10 +507,10 @@ extern inline void writeq(u64 b, volatile void __iomem *addr) + } + #endif + +-#define ioread16be(p) be16_to_cpu(ioread16(p)) +-#define ioread32be(p) be32_to_cpu(ioread32(p)) +-#define iowrite16be(v,p) iowrite16(cpu_to_be16(v), (p)) +-#define iowrite32be(v,p) iowrite32(cpu_to_be32(v), (p)) ++#define ioread16be(p) swab16(ioread16(p)) ++#define ioread32be(p) swab32(ioread32(p)) ++#define iowrite16be(v,p) iowrite16(swab16(v), (p)) ++#define iowrite32be(v,p) iowrite32(swab32(v), (p)) + + #define inb_p inb + #define inw_p inw +-- +2.25.1 + diff --git a/queue-4.19/ceph-fix-use-after-free-for-fsc-mdsc.patch b/queue-4.19/ceph-fix-use-after-free-for-fsc-mdsc.patch new file mode 100644 index 00000000000..ed00d6e32de --- /dev/null +++ b/queue-4.19/ceph-fix-use-after-free-for-fsc-mdsc.patch @@ -0,0 +1,44 @@ +From a48462dc02875eef2159e2bda0812300cbdaac7d Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 23 Jul 2020 15:32:25 +0800 +Subject: ceph: fix use-after-free for fsc->mdsc + +From: Xiubo Li + +[ Upstream commit a7caa88f8b72c136f9a401f498471b8a8e35370d ] + +If the ceph_mdsc_init() fails, it will free the mdsc already. + +Reported-by: syzbot+b57f46d8d6ea51960b8c@syzkaller.appspotmail.com +Signed-off-by: Xiubo Li +Reviewed-by: Jeff Layton +Signed-off-by: Ilya Dryomov +Signed-off-by: Sasha Levin +--- + fs/ceph/mds_client.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/fs/ceph/mds_client.c b/fs/ceph/mds_client.c +index a2e903203bf9f..0fa14d8b9c64c 100644 +--- a/fs/ceph/mds_client.c ++++ b/fs/ceph/mds_client.c +@@ -3682,7 +3682,6 @@ int ceph_mdsc_init(struct ceph_fs_client *fsc) + return -ENOMEM; + } + +- fsc->mdsc = mdsc; + init_completion(&mdsc->safe_umount_waiters); + init_waitqueue_head(&mdsc->session_close_wq); + INIT_LIST_HEAD(&mdsc->waiting_for_map); +@@ -3723,6 +3722,8 @@ int ceph_mdsc_init(struct ceph_fs_client *fsc) + + strscpy(mdsc->nodename, utsname()->nodename, + sizeof(mdsc->nodename)); ++ ++ fsc->mdsc = mdsc; + return 0; + } + +-- +2.25.1 + diff --git a/queue-4.19/cpufreq-intel_pstate-fix-cpuinfo_max_freq-when-msr_t.patch b/queue-4.19/cpufreq-intel_pstate-fix-cpuinfo_max_freq-when-msr_t.patch new file mode 100644 index 00000000000..2241dd5b197 --- /dev/null +++ b/queue-4.19/cpufreq-intel_pstate-fix-cpuinfo_max_freq-when-msr_t.patch @@ -0,0 +1,48 @@ +From 08d3c004175b8243bd270c57c0ba81ee23d8b448 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 3 Aug 2020 11:37:20 -0700 +Subject: cpufreq: intel_pstate: Fix cpuinfo_max_freq when + MSR_TURBO_RATIO_LIMIT is 0 + +From: Srinivas Pandruvada + +[ Upstream commit 4daca379c703ff55edc065e8e5173dcfeecf0148 ] + +The MSR_TURBO_RATIO_LIMIT can be 0. This is not an error. User can update +this MSR via BIOS settings on some systems or can use msr tools to update. +Also some systems boot with value = 0. + +This results in display of cpufreq/cpuinfo_max_freq wrong. This value +will be equal to cpufreq/base_frequency, even though turbo is enabled. + +But platform will still function normally in HWP mode as we get max +1-core frequency from the MSR_HWP_CAPABILITIES. This MSR is already used +to calculate cpu->pstate.turbo_freq, which is used for to set +policy->cpuinfo.max_freq. But some other places cpu->pstate.turbo_pstate +is used. For example to set policy->max. + +To fix this, also update cpu->pstate.turbo_pstate when updating +cpu->pstate.turbo_freq. + +Signed-off-by: Srinivas Pandruvada +Signed-off-by: Rafael J. Wysocki +Signed-off-by: Sasha Levin +--- + drivers/cpufreq/intel_pstate.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c +index e7b3d4ed8eff4..99166000ffb77 100644 +--- a/drivers/cpufreq/intel_pstate.c ++++ b/drivers/cpufreq/intel_pstate.c +@@ -1431,6 +1431,7 @@ static void intel_pstate_get_cpu_pstates(struct cpudata *cpu) + + intel_pstate_get_hwp_max(cpu->cpu, &phy_max, ¤t_max); + cpu->pstate.turbo_freq = phy_max * cpu->pstate.scaling; ++ cpu->pstate.turbo_pstate = phy_max; + } else { + cpu->pstate.turbo_freq = cpu->pstate.turbo_pstate * cpu->pstate.scaling; + } +-- +2.25.1 + diff --git a/queue-4.19/fs-signalfd.c-fix-inconsistent-return-codes-for-sign.patch b/queue-4.19/fs-signalfd.c-fix-inconsistent-return-codes-for-sign.patch new file mode 100644 index 00000000000..5cc0d4bc0da --- /dev/null +++ b/queue-4.19/fs-signalfd.c-fix-inconsistent-return-codes-for-sign.patch @@ -0,0 +1,60 @@ +From c6ed876951566b64de49ba16236064a83d8235d4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 11 Aug 2020 18:36:04 -0700 +Subject: fs/signalfd.c: fix inconsistent return codes for signalfd4 + +From: Helge Deller + +[ Upstream commit a089e3fd5a82aea20f3d9ec4caa5f4c65cc2cfcc ] + +The kernel signalfd4() syscall returns different error codes when called +either in compat or native mode. This behaviour makes correct emulation +in qemu and testing programs like LTP more complicated. + +Fix the code to always return -in both modes- EFAULT for unaccessible user +memory, and EINVAL when called with an invalid signal mask. + +Signed-off-by: Helge Deller +Signed-off-by: Andrew Morton +Cc: Alexander Viro +Cc: Laurent Vivier +Link: http://lkml.kernel.org/r/20200530100707.GA10159@ls3530.fritz.box +Signed-off-by: Linus Torvalds +Signed-off-by: Sasha Levin +--- + fs/signalfd.c | 10 ++++++---- + 1 file changed, 6 insertions(+), 4 deletions(-) + +diff --git a/fs/signalfd.c b/fs/signalfd.c +index 4fcd1498acf52..3c40a3bf772ce 100644 +--- a/fs/signalfd.c ++++ b/fs/signalfd.c +@@ -313,9 +313,10 @@ SYSCALL_DEFINE4(signalfd4, int, ufd, sigset_t __user *, user_mask, + { + sigset_t mask; + +- if (sizemask != sizeof(sigset_t) || +- copy_from_user(&mask, user_mask, sizeof(mask))) ++ if (sizemask != sizeof(sigset_t)) + return -EINVAL; ++ if (copy_from_user(&mask, user_mask, sizeof(mask))) ++ return -EFAULT; + return do_signalfd4(ufd, &mask, flags); + } + +@@ -324,9 +325,10 @@ SYSCALL_DEFINE3(signalfd, int, ufd, sigset_t __user *, user_mask, + { + sigset_t mask; + +- if (sizemask != sizeof(sigset_t) || +- copy_from_user(&mask, user_mask, sizeof(mask))) ++ if (sizemask != sizeof(sigset_t)) + return -EINVAL; ++ if (copy_from_user(&mask, user_mask, sizeof(mask))) ++ return -EFAULT; + return do_signalfd4(ufd, &mask, 0); + } + +-- +2.25.1 + diff --git a/queue-4.19/input-psmouse-add-a-newline-when-printing-proto-by-s.patch b/queue-4.19/input-psmouse-add-a-newline-when-printing-proto-by-s.patch new file mode 100644 index 00000000000..dc8b401c8c3 --- /dev/null +++ b/queue-4.19/input-psmouse-add-a-newline-when-printing-proto-by-s.patch @@ -0,0 +1,39 @@ +From 5a2e5d71e8609cff5b1c44f4f1cd50a7f8682129 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 21 Jul 2020 22:24:07 -0700 +Subject: Input: psmouse - add a newline when printing 'proto' by sysfs + +From: Xiongfeng Wang + +[ Upstream commit 4aec14de3a15cf9789a0e19c847f164776f49473 ] + +When I cat parameter 'proto' by sysfs, it displays as follows. It's +better to add a newline for easy reading. + +root@syzkaller:~# cat /sys/module/psmouse/parameters/proto +autoroot@syzkaller:~# + +Signed-off-by: Xiongfeng Wang +Link: https://lore.kernel.org/r/20200720073846.120724-1-wangxiongfeng2@huawei.com +Signed-off-by: Dmitry Torokhov +Signed-off-by: Sasha Levin +--- + drivers/input/mouse/psmouse-base.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/input/mouse/psmouse-base.c b/drivers/input/mouse/psmouse-base.c +index d3ff1fc09af71..a9040c0fb4c3f 100644 +--- a/drivers/input/mouse/psmouse-base.c ++++ b/drivers/input/mouse/psmouse-base.c +@@ -2044,7 +2044,7 @@ static int psmouse_get_maxproto(char *buffer, const struct kernel_param *kp) + { + int type = *((unsigned int *)kp->arg); + +- return sprintf(buffer, "%s", psmouse_protocol_by_type(type)->name); ++ return sprintf(buffer, "%s\n", psmouse_protocol_by_type(type)->name); + } + + static int __init psmouse_init(void) +-- +2.25.1 + diff --git a/queue-4.19/jffs2-fix-uaf-problem.patch b/queue-4.19/jffs2-fix-uaf-problem.patch new file mode 100644 index 00000000000..990598a9cf9 --- /dev/null +++ b/queue-4.19/jffs2-fix-uaf-problem.patch @@ -0,0 +1,80 @@ +From 14fa681e4621f2a6e0545fff4e07a218d5f55c5f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 19 Jun 2020 17:06:35 +0800 +Subject: jffs2: fix UAF problem + +From: Zhe Li + +[ Upstream commit 798b7347e4f29553db4b996393caf12f5b233daf ] + +The log of UAF problem is listed below. +BUG: KASAN: use-after-free in jffs2_rmdir+0xa4/0x1cc [jffs2] at addr c1f165fc +Read of size 4 by task rm/8283 +============================================================================= +BUG kmalloc-32 (Tainted: P B O ): kasan: bad access detected +----------------------------------------------------------------------------- + +INFO: Allocated in 0xbbbbbbbb age=3054364 cpu=0 pid=0 + 0xb0bba6ef + jffs2_write_dirent+0x11c/0x9c8 [jffs2] + __slab_alloc.isra.21.constprop.25+0x2c/0x44 + __kmalloc+0x1dc/0x370 + jffs2_write_dirent+0x11c/0x9c8 [jffs2] + jffs2_do_unlink+0x328/0x5fc [jffs2] + jffs2_rmdir+0x110/0x1cc [jffs2] + vfs_rmdir+0x180/0x268 + do_rmdir+0x2cc/0x300 + ret_from_syscall+0x0/0x3c +INFO: Freed in 0x205b age=3054364 cpu=0 pid=0 + 0x2e9173 + jffs2_add_fd_to_list+0x138/0x1dc [jffs2] + jffs2_add_fd_to_list+0x138/0x1dc [jffs2] + jffs2_garbage_collect_dirent.isra.3+0x21c/0x288 [jffs2] + jffs2_garbage_collect_live+0x16bc/0x1800 [jffs2] + jffs2_garbage_collect_pass+0x678/0x11d4 [jffs2] + jffs2_garbage_collect_thread+0x1e8/0x3b0 [jffs2] + kthread+0x1a8/0x1b0 + ret_from_kernel_thread+0x5c/0x64 +Call Trace: +[c17ddd20] [c02452d4] kasan_report.part.0+0x298/0x72c (unreliable) +[c17ddda0] [d2509680] jffs2_rmdir+0xa4/0x1cc [jffs2] +[c17dddd0] [c026da04] vfs_rmdir+0x180/0x268 +[c17dde00] [c026f4e4] do_rmdir+0x2cc/0x300 +[c17ddf40] [c001a658] ret_from_syscall+0x0/0x3c + +The root cause is that we don't get "jffs2_inode_info.sem" before +we scan list "jffs2_inode_info.dents" in function jffs2_rmdir. +This patch add codes to get "jffs2_inode_info.sem" before we scan +"jffs2_inode_info.dents" to slove the UAF problem. + +Signed-off-by: Zhe Li +Reviewed-by: Hou Tao +Signed-off-by: Richard Weinberger +Signed-off-by: Sasha Levin +--- + fs/jffs2/dir.c | 6 +++++- + 1 file changed, 5 insertions(+), 1 deletion(-) + +diff --git a/fs/jffs2/dir.c b/fs/jffs2/dir.c +index f20cff1194bb6..776493713153f 100644 +--- a/fs/jffs2/dir.c ++++ b/fs/jffs2/dir.c +@@ -590,10 +590,14 @@ static int jffs2_rmdir (struct inode *dir_i, struct dentry *dentry) + int ret; + uint32_t now = JFFS2_NOW(); + ++ mutex_lock(&f->sem); + for (fd = f->dents ; fd; fd = fd->next) { +- if (fd->ino) ++ if (fd->ino) { ++ mutex_unlock(&f->sem); + return -ENOTEMPTY; ++ } + } ++ mutex_unlock(&f->sem); + + ret = jffs2_do_unlink(c, dir_f, dentry->d_name.name, + dentry->d_name.len, f, now); +-- +2.25.1 + diff --git a/queue-4.19/kvm-arm64-only-reschedule-if-mmu_notifier_range_bloc.patch b/queue-4.19/kvm-arm64-only-reschedule-if-mmu_notifier_range_bloc.patch new file mode 100644 index 00000000000..6ab3ced4372 --- /dev/null +++ b/queue-4.19/kvm-arm64-only-reschedule-if-mmu_notifier_range_bloc.patch @@ -0,0 +1,110 @@ +From 265d91ebe51c31f68e576ded3e4dfe23171e6382 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 11 Aug 2020 11:27:25 +0100 +Subject: KVM: arm64: Only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is not + set + +From: Will Deacon + +[ Upstream commit b5331379bc62611d1026173a09c73573384201d9 ] + +When an MMU notifier call results in unmapping a range that spans multiple +PGDs, we end up calling into cond_resched_lock() when crossing a PGD boundary, +since this avoids running into RCU stalls during VM teardown. Unfortunately, +if the VM is destroyed as a result of OOM, then blocking is not permitted +and the call to the scheduler triggers the following BUG(): + + | BUG: sleeping function called from invalid context at arch/arm64/kvm/mmu.c:394 + | in_atomic(): 1, irqs_disabled(): 0, non_block: 1, pid: 36, name: oom_reaper + | INFO: lockdep is turned off. + | CPU: 3 PID: 36 Comm: oom_reaper Not tainted 5.8.0 #1 + | Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 + | Call trace: + | dump_backtrace+0x0/0x284 + | show_stack+0x1c/0x28 + | dump_stack+0xf0/0x1a4 + | ___might_sleep+0x2bc/0x2cc + | unmap_stage2_range+0x160/0x1ac + | kvm_unmap_hva_range+0x1a0/0x1c8 + | kvm_mmu_notifier_invalidate_range_start+0x8c/0xf8 + | __mmu_notifier_invalidate_range_start+0x218/0x31c + | mmu_notifier_invalidate_range_start_nonblock+0x78/0xb0 + | __oom_reap_task_mm+0x128/0x268 + | oom_reap_task+0xac/0x298 + | oom_reaper+0x178/0x17c + | kthread+0x1e4/0x1fc + | ret_from_fork+0x10/0x30 + +Use the new 'flags' argument to kvm_unmap_hva_range() to ensure that we +only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is set in the notifier +flags. + +Cc: +Fixes: 8b3405e345b5 ("kvm: arm/arm64: Fix locking for kvm_free_stage2_pgd") +Cc: Marc Zyngier +Cc: Suzuki K Poulose +Cc: James Morse +Signed-off-by: Will Deacon +Message-Id: <20200811102725.7121-3-will@kernel.org> +Signed-off-by: Paolo Bonzini +Signed-off-by: Sasha Levin +--- + virt/kvm/arm/mmu.c | 17 +++++++++++++---- + 1 file changed, 13 insertions(+), 4 deletions(-) + +diff --git a/virt/kvm/arm/mmu.c b/virt/kvm/arm/mmu.c +index a5bc10d30618f..84c0b5005f0f4 100644 +--- a/virt/kvm/arm/mmu.c ++++ b/virt/kvm/arm/mmu.c +@@ -323,7 +323,8 @@ static void unmap_stage2_puds(struct kvm *kvm, pgd_t *pgd, + * destroying the VM), otherwise another faulting VCPU may come in and mess + * with things behind our backs. + */ +-static void unmap_stage2_range(struct kvm *kvm, phys_addr_t start, u64 size) ++static void __unmap_stage2_range(struct kvm *kvm, phys_addr_t start, u64 size, ++ bool may_block) + { + pgd_t *pgd; + phys_addr_t addr = start, end = start + size; +@@ -348,11 +349,16 @@ static void unmap_stage2_range(struct kvm *kvm, phys_addr_t start, u64 size) + * If the range is too large, release the kvm->mmu_lock + * to prevent starvation and lockup detector warnings. + */ +- if (next != end) ++ if (may_block && next != end) + cond_resched_lock(&kvm->mmu_lock); + } while (pgd++, addr = next, addr != end); + } + ++static void unmap_stage2_range(struct kvm_s2_mmu *mmu, phys_addr_t start, u64 size) ++{ ++ __unmap_stage2_range(mmu, start, size, true); ++} ++ + static void stage2_flush_ptes(struct kvm *kvm, pmd_t *pmd, + phys_addr_t addr, phys_addr_t end) + { +@@ -1820,7 +1826,10 @@ static int handle_hva_to_gpa(struct kvm *kvm, + + static int kvm_unmap_hva_handler(struct kvm *kvm, gpa_t gpa, u64 size, void *data) + { +- unmap_stage2_range(kvm, gpa, size); ++ unsigned flags = *(unsigned *)data; ++ bool may_block = flags & MMU_NOTIFIER_RANGE_BLOCKABLE; ++ ++ __unmap_stage2_range(kvm, gpa, size, may_block); + return 0; + } + +@@ -1831,7 +1840,7 @@ int kvm_unmap_hva_range(struct kvm *kvm, + return 0; + + trace_kvm_unmap_hva_range(start, end); +- handle_hva_to_gpa(kvm, start, end, &kvm_unmap_hva_handler, NULL); ++ handle_hva_to_gpa(kvm, start, end, &kvm_unmap_hva_handler, &flags); + return 0; + } + +-- +2.25.1 + diff --git a/queue-4.19/m68knommu-fix-overwriting-of-bits-in-coldfire-v3-cac.patch b/queue-4.19/m68knommu-fix-overwriting-of-bits-in-coldfire-v3-cac.patch new file mode 100644 index 00000000000..77354f3e4c9 --- /dev/null +++ b/queue-4.19/m68knommu-fix-overwriting-of-bits-in-coldfire-v3-cac.patch @@ -0,0 +1,52 @@ +From ad4cd079411b38d39fd0db7554dcd31e96cf1dee Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 13 Jun 2020 17:17:52 +1000 +Subject: m68knommu: fix overwriting of bits in ColdFire V3 cache control + +From: Greg Ungerer + +[ Upstream commit bdee0e793cea10c516ff48bf3ebb4ef1820a116b ] + +The Cache Control Register (CACR) of the ColdFire V3 has bits that +control high level caching functions, and also enable/disable the use +of the alternate stack pointer register (the EUSP bit) to provide +separate supervisor and user stack pointer registers. The code as +it is today will blindly clear the EUSP bit on cache actions like +invalidation. So it is broken for this case - and that will result +in failed booting (interrupt entry and exit processing will be +completely hosed). + +This only affects ColdFire V3 parts that support the alternate stack +register (like the 5329 for example) - generally speaking new parts do, +older parts don't. It has no impact on ColdFire V3 parts with the single +stack pointer, like the 5307 for example. + +Fix the cache bit defines used, so they maintain the EUSP bit when +carrying out cache actions through the CACR register. + +Signed-off-by: Greg Ungerer +Signed-off-by: Sasha Levin +--- + arch/m68k/include/asm/m53xxacr.h | 6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/arch/m68k/include/asm/m53xxacr.h b/arch/m68k/include/asm/m53xxacr.h +index 9138a624c5c81..692f90e7fecc1 100644 +--- a/arch/m68k/include/asm/m53xxacr.h ++++ b/arch/m68k/include/asm/m53xxacr.h +@@ -89,9 +89,9 @@ + * coherency though in all cases. And for copyback caches we will need + * to push cached data as well. + */ +-#define CACHE_INIT CACR_CINVA +-#define CACHE_INVALIDATE CACR_CINVA +-#define CACHE_INVALIDATED CACR_CINVA ++#define CACHE_INIT (CACHE_MODE + CACR_CINVA - CACR_EC) ++#define CACHE_INVALIDATE (CACHE_MODE + CACR_CINVA) ++#define CACHE_INVALIDATED (CACHE_MODE + CACR_CINVA) + + #define ACR0_MODE ((CONFIG_RAMBASE & 0xff000000) + \ + (0x000f0000) + \ +-- +2.25.1 + diff --git a/queue-4.19/media-budget-core-improve-exception-handling-in-budg.patch b/queue-4.19/media-budget-core-improve-exception-handling-in-budg.patch new file mode 100644 index 00000000000..ddf346ef53e --- /dev/null +++ b/queue-4.19/media-budget-core-improve-exception-handling-in-budg.patch @@ -0,0 +1,56 @@ +From e628d0f2100f258e9bb16a789ef4603ef52d4da4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 5 Jun 2020 18:17:28 +0200 +Subject: media: budget-core: Improve exception handling in budget_register() + +From: Chuhong Yuan + +[ Upstream commit fc0456458df8b3421dba2a5508cd817fbc20ea71 ] + +budget_register() has no error handling after its failure. +Add the missed undo functions for error handling to fix it. + +Signed-off-by: Chuhong Yuan +Signed-off-by: Sean Young +Signed-off-by: Mauro Carvalho Chehab +Signed-off-by: Sasha Levin +--- + drivers/media/pci/ttpci/budget-core.c | 11 ++++++++--- + 1 file changed, 8 insertions(+), 3 deletions(-) + +diff --git a/drivers/media/pci/ttpci/budget-core.c b/drivers/media/pci/ttpci/budget-core.c +index b3dc45b91101d..9b545c7431685 100644 +--- a/drivers/media/pci/ttpci/budget-core.c ++++ b/drivers/media/pci/ttpci/budget-core.c +@@ -383,20 +383,25 @@ static int budget_register(struct budget *budget) + ret = dvbdemux->dmx.add_frontend(&dvbdemux->dmx, &budget->hw_frontend); + + if (ret < 0) +- return ret; ++ goto err_release_dmx; + + budget->mem_frontend.source = DMX_MEMORY_FE; + ret = dvbdemux->dmx.add_frontend(&dvbdemux->dmx, &budget->mem_frontend); + if (ret < 0) +- return ret; ++ goto err_release_dmx; + + ret = dvbdemux->dmx.connect_frontend(&dvbdemux->dmx, &budget->hw_frontend); + if (ret < 0) +- return ret; ++ goto err_release_dmx; + + dvb_net_init(&budget->dvb_adapter, &budget->dvb_net, &dvbdemux->dmx); + + return 0; ++ ++err_release_dmx: ++ dvb_dmxdev_release(&budget->dmxdev); ++ dvb_dmx_release(&budget->demux); ++ return ret; + } + + static void budget_unregister(struct budget *budget) +-- +2.25.1 + diff --git a/queue-4.19/media-vpss-clean-up-resources-in-init.patch b/queue-4.19/media-vpss-clean-up-resources-in-init.patch new file mode 100644 index 00000000000..697b6e9fce2 --- /dev/null +++ b/queue-4.19/media-vpss-clean-up-resources-in-init.patch @@ -0,0 +1,66 @@ +From a04d71fd3dd0b87773559de7bbc0460acce142cd Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 10 Jul 2020 11:02:23 +0200 +Subject: media: vpss: clean up resources in init + +From: Evgeny Novikov + +[ Upstream commit 9c487b0b0ea7ff22127fe99a7f67657d8730ff94 ] + +If platform_driver_register() fails within vpss_init() resources are not +cleaned up. The patch fixes this issue by introducing the corresponding +error handling. + +Found by Linux Driver Verification project (linuxtesting.org). + +Signed-off-by: Evgeny Novikov +Signed-off-by: Hans Verkuil +Signed-off-by: Mauro Carvalho Chehab +Signed-off-by: Sasha Levin +--- + drivers/media/platform/davinci/vpss.c | 20 ++++++++++++++++---- + 1 file changed, 16 insertions(+), 4 deletions(-) + +diff --git a/drivers/media/platform/davinci/vpss.c b/drivers/media/platform/davinci/vpss.c +index 89a86c19579b8..50fc71d0cb9f3 100644 +--- a/drivers/media/platform/davinci/vpss.c ++++ b/drivers/media/platform/davinci/vpss.c +@@ -514,19 +514,31 @@ static void vpss_exit(void) + + static int __init vpss_init(void) + { ++ int ret; ++ + if (!request_mem_region(VPSS_CLK_CTRL, 4, "vpss_clock_control")) + return -EBUSY; + + oper_cfg.vpss_regs_base2 = ioremap(VPSS_CLK_CTRL, 4); + if (unlikely(!oper_cfg.vpss_regs_base2)) { +- release_mem_region(VPSS_CLK_CTRL, 4); +- return -ENOMEM; ++ ret = -ENOMEM; ++ goto err_ioremap; + } + + writel(VPSS_CLK_CTRL_VENCCLKEN | +- VPSS_CLK_CTRL_DACCLKEN, oper_cfg.vpss_regs_base2); ++ VPSS_CLK_CTRL_DACCLKEN, oper_cfg.vpss_regs_base2); ++ ++ ret = platform_driver_register(&vpss_driver); ++ if (ret) ++ goto err_pd_register; ++ ++ return 0; + +- return platform_driver_register(&vpss_driver); ++err_pd_register: ++ iounmap(oper_cfg.vpss_regs_base2); ++err_ioremap: ++ release_mem_region(VPSS_CLK_CTRL, 4); ++ return ret; + } + subsys_initcall(vpss_init); + module_exit(vpss_exit); +-- +2.25.1 + diff --git a/queue-4.19/rtc-goldfish-enable-interrupt-in-set_alarm-when-nece.patch b/queue-4.19/rtc-goldfish-enable-interrupt-in-set_alarm-when-nece.patch new file mode 100644 index 00000000000..184842f1022 --- /dev/null +++ b/queue-4.19/rtc-goldfish-enable-interrupt-in-set_alarm-when-nece.patch @@ -0,0 +1,39 @@ +From d29d336be3e8007eae323818281a8844ba21329e Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 20 Jun 2020 20:04:43 +0800 +Subject: rtc: goldfish: Enable interrupt in set_alarm() when necessary + +From: Huacai Chen + +[ Upstream commit 22f8d5a1bf230cf8567a4121fc3789babb46336d ] + +When use goldfish rtc, the "hwclock" command fails with "select() to +/dev/rtc to wait for clock tick timed out". This is because "hwclock" +need the set_alarm() hook to enable interrupt when alrm->enabled is +true. This operation is missing in goldfish rtc (but other rtc drivers, +such as cmos rtc, enable interrupt here), so add it. + +Signed-off-by: Huacai Chen +Signed-off-by: Jiaxun Yang +Signed-off-by: Alexandre Belloni +Link: https://lore.kernel.org/r/1592654683-31314-1-git-send-email-chenhc@lemote.com +Signed-off-by: Sasha Levin +--- + drivers/rtc/rtc-goldfish.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/rtc/rtc-goldfish.c b/drivers/rtc/rtc-goldfish.c +index a1c44d0c85578..30cbe22c57a8e 100644 +--- a/drivers/rtc/rtc-goldfish.c ++++ b/drivers/rtc/rtc-goldfish.c +@@ -87,6 +87,7 @@ static int goldfish_rtc_set_alarm(struct device *dev, + rtc_alarm64 = rtc_alarm * NSEC_PER_SEC; + writel((rtc_alarm64 >> 32), base + TIMER_ALARM_HIGH); + writel(rtc_alarm64, base + TIMER_ALARM_LOW); ++ writel(1, base + TIMER_IRQ_ENABLED); + } else { + /* + * if this function was called with enabled=0 +-- +2.25.1 + diff --git a/queue-4.19/scsi-libfc-free-skb-in-fc_disc_gpn_id_resp-for-valid.patch b/queue-4.19/scsi-libfc-free-skb-in-fc_disc_gpn_id_resp-for-valid.patch new file mode 100644 index 00000000000..4e29bc4facc --- /dev/null +++ b/queue-4.19/scsi-libfc-free-skb-in-fc_disc_gpn_id_resp-for-valid.patch @@ -0,0 +1,66 @@ +From 839023813ac1a86b4ab3d39a0a404cd2aca556e3 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 29 Jul 2020 01:18:23 -0700 +Subject: scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases + +From: Javed Hasan + +[ Upstream commit ec007ef40abb6a164d148b0dc19789a7a2de2cc8 ] + +In fc_disc_gpn_id_resp(), skb is supposed to get freed in all cases except +for PTR_ERR. However, in some cases it didn't. + +This fix is to call fc_frame_free(fp) before function returns. + +Link: https://lore.kernel.org/r/20200729081824.30996-2-jhasan@marvell.com +Reviewed-by: Girish Basrur +Reviewed-by: Santosh Vernekar +Reviewed-by: Saurav Kashyap +Reviewed-by: Shyam Sundar +Signed-off-by: Javed Hasan +Signed-off-by: Martin K. Petersen +Signed-off-by: Sasha Levin +--- + drivers/scsi/libfc/fc_disc.c | 12 +++++++++--- + 1 file changed, 9 insertions(+), 3 deletions(-) + +diff --git a/drivers/scsi/libfc/fc_disc.c b/drivers/scsi/libfc/fc_disc.c +index 8839f509b19ab..78cf5b32bca67 100644 +--- a/drivers/scsi/libfc/fc_disc.c ++++ b/drivers/scsi/libfc/fc_disc.c +@@ -593,8 +593,12 @@ static void fc_disc_gpn_id_resp(struct fc_seq *sp, struct fc_frame *fp, + + if (PTR_ERR(fp) == -FC_EX_CLOSED) + goto out; +- if (IS_ERR(fp)) +- goto redisc; ++ if (IS_ERR(fp)) { ++ mutex_lock(&disc->disc_mutex); ++ fc_disc_restart(disc); ++ mutex_unlock(&disc->disc_mutex); ++ goto out; ++ } + + cp = fc_frame_payload_get(fp, sizeof(*cp)); + if (!cp) +@@ -621,7 +625,7 @@ static void fc_disc_gpn_id_resp(struct fc_seq *sp, struct fc_frame *fp, + new_rdata->disc_id = disc->disc_id; + fc_rport_login(new_rdata); + } +- goto out; ++ goto free_fp; + } + rdata->disc_id = disc->disc_id; + mutex_unlock(&rdata->rp_mutex); +@@ -638,6 +642,8 @@ redisc: + fc_disc_restart(disc); + mutex_unlock(&disc->disc_mutex); + } ++free_fp: ++ fc_frame_free(fp); + out: + kref_put(&rdata->kref, fc_rport_destroy); + if (!IS_ERR(fp)) +-- +2.25.1 + diff --git a/queue-4.19/scsi-target-tcmu-fix-crash-in-tcmu_flush_dcache_rang.patch b/queue-4.19/scsi-target-tcmu-fix-crash-in-tcmu_flush_dcache_rang.patch new file mode 100644 index 00000000000..1fec5d4b67e --- /dev/null +++ b/queue-4.19/scsi-target-tcmu-fix-crash-in-tcmu_flush_dcache_rang.patch @@ -0,0 +1,94 @@ +From 2a439184f1cfe515b0feb0688755f5793b9824fb Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 18 Jun 2020 15:16:32 +0200 +Subject: scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM + +From: Bodo Stroesser + +[ Upstream commit 3145550a7f8b08356c8ff29feaa6c56aca12901d ] + +This patch fixes the following crash (see +https://bugzilla.kernel.org/show_bug.cgi?id=208045) + + Process iscsi_trx (pid: 7496, stack limit = 0x0000000010dd111a) + CPU: 0 PID: 7496 Comm: iscsi_trx Not tainted 4.19.118-0419118-generic + #202004230533 + Hardware name: Greatwall QingTian DF720/F601, BIOS 601FBE20 Sep 26 2019 + pstate: 80400005 (Nzcv daif +PAN -UAO) + pc : flush_dcache_page+0x18/0x40 + lr : is_ring_space_avail+0x68/0x2f8 [target_core_user] + sp : ffff000015123a80 + x29: ffff000015123a80 x28: 0000000000000000 + x27: 0000000000001000 x26: ffff000023ea5000 + x25: ffffcfa25bbe08b8 x24: 0000000000000078 + x23: ffff7e0000000000 x22: ffff000023ea5001 + x21: ffffcfa24b79c000 x20: 0000000000000fff + x19: ffff7e00008fa940 x18: 0000000000000000 + x17: 0000000000000000 x16: ffff2d047e709138 + x15: 0000000000000000 x14: 0000000000000000 + x13: 0000000000000000 x12: ffff2d047fbd0a40 + x11: 0000000000000000 x10: 0000000000000030 + x9 : 0000000000000000 x8 : ffffc9a254820a00 + x7 : 00000000000013b0 x6 : 000000000000003f + x5 : 0000000000000040 x4 : ffffcfa25bbe08e8 + x3 : 0000000000001000 x2 : 0000000000000078 + x1 : ffffcfa25bbe08b8 x0 : ffff2d040bc88a18 + Call trace: + flush_dcache_page+0x18/0x40 + is_ring_space_avail+0x68/0x2f8 [target_core_user] + queue_cmd_ring+0x1f8/0x680 [target_core_user] + tcmu_queue_cmd+0xe4/0x158 [target_core_user] + __target_execute_cmd+0x30/0xf0 [target_core_mod] + target_execute_cmd+0x294/0x390 [target_core_mod] + transport_generic_new_cmd+0x1e8/0x358 [target_core_mod] + transport_handle_cdb_direct+0x50/0xb0 [target_core_mod] + iscsit_execute_cmd+0x2b4/0x350 [iscsi_target_mod] + iscsit_sequence_cmd+0xd8/0x1d8 [iscsi_target_mod] + iscsit_process_scsi_cmd+0xac/0xf8 [iscsi_target_mod] + iscsit_get_rx_pdu+0x404/0xd00 [iscsi_target_mod] + iscsi_target_rx_thread+0xb8/0x130 [iscsi_target_mod] + kthread+0x130/0x138 + ret_from_fork+0x10/0x18 + Code: f9000bf3 aa0003f3 aa1e03e0 d503201f (f9400260) + ---[ end trace 1e451c73f4266776 ]--- + +The solution is based on patch: + + "scsi: target: tcmu: Optimize use of flush_dcache_page" + +which restricts the use of tcmu_flush_dcache_range() to addresses from +vmalloc'ed areas only. + +This patch now replaces the virt_to_page() call in +tcmu_flush_dcache_range() - which is wrong for vmalloced addrs - by +vmalloc_to_page(). + +The patch was tested on ARM with kernel 4.19.118 and 5.7.2 + +Link: https://lore.kernel.org/r/20200618131632.32748-3-bstroesser@ts.fujitsu.com +Tested-by: JiangYu +Tested-by: Daniel Meyerholt +Acked-by: Mike Christie +Signed-off-by: Bodo Stroesser +Signed-off-by: Martin K. Petersen +Signed-off-by: Sasha Levin +--- + drivers/target/target_core_user.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/target/target_core_user.c b/drivers/target/target_core_user.c +index 8da89925a874d..9c05e820857aa 100644 +--- a/drivers/target/target_core_user.c ++++ b/drivers/target/target_core_user.c +@@ -612,7 +612,7 @@ static inline void tcmu_flush_dcache_range(void *vaddr, size_t size) + size = round_up(size+offset, PAGE_SIZE); + + while (size) { +- flush_dcache_page(virt_to_page(start)); ++ flush_dcache_page(vmalloc_to_page(start)); + start += PAGE_SIZE; + size -= PAGE_SIZE; + } +-- +2.25.1 + diff --git a/queue-4.19/scsi-ufs-add-delay_before_lpm-quirk-for-micron-devic.patch b/queue-4.19/scsi-ufs-add-delay_before_lpm-quirk-for-micron-devic.patch new file mode 100644 index 00000000000..138adc09c44 --- /dev/null +++ b/queue-4.19/scsi-ufs-add-delay_before_lpm-quirk-for-micron-devic.patch @@ -0,0 +1,52 @@ +From cf832e06c4ea50d3975b3e802483646159006111 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 12 Jun 2020 09:26:24 +0800 +Subject: scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices + +From: Stanley Chu + +[ Upstream commit c0a18ee0ce78d7957ec1a53be35b1b3beba80668 ] + +It is confirmed that Micron device needs DELAY_BEFORE_LPM quirk to have a +delay before VCC is powered off. Sdd Micron vendor ID and this quirk for +Micron devices. + +Link: https://lore.kernel.org/r/20200612012625.6615-2-stanley.chu@mediatek.com +Reviewed-by: Bean Huo +Reviewed-by: Alim Akhtar +Signed-off-by: Stanley Chu +Signed-off-by: Martin K. Petersen +Signed-off-by: Sasha Levin +--- + drivers/scsi/ufs/ufs_quirks.h | 1 + + drivers/scsi/ufs/ufshcd.c | 2 ++ + 2 files changed, 3 insertions(+) + +diff --git a/drivers/scsi/ufs/ufs_quirks.h b/drivers/scsi/ufs/ufs_quirks.h +index 5d2dfdb41a6ff..758d3a67047df 100644 +--- a/drivers/scsi/ufs/ufs_quirks.h ++++ b/drivers/scsi/ufs/ufs_quirks.h +@@ -21,6 +21,7 @@ + #define UFS_ANY_VENDOR 0xFFFF + #define UFS_ANY_MODEL "ANY_MODEL" + ++#define UFS_VENDOR_MICRON 0x12C + #define UFS_VENDOR_TOSHIBA 0x198 + #define UFS_VENDOR_SAMSUNG 0x1CE + #define UFS_VENDOR_SKHYNIX 0x1AD +diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c +index bd21c9cdf8183..ab628fd37e026 100644 +--- a/drivers/scsi/ufs/ufshcd.c ++++ b/drivers/scsi/ufs/ufshcd.c +@@ -218,6 +218,8 @@ ufs_get_desired_pm_lvl_for_dev_link_state(enum ufs_dev_pwr_mode dev_state, + + static struct ufs_dev_fix ufs_fixups[] = { + /* UFS cards deviations table */ ++ UFS_FIX(UFS_VENDOR_MICRON, UFS_ANY_MODEL, ++ UFS_DEVICE_QUIRK_DELAY_BEFORE_LPM), + UFS_FIX(UFS_VENDOR_SAMSUNG, UFS_ANY_MODEL, + UFS_DEVICE_QUIRK_DELAY_BEFORE_LPM), + UFS_FIX(UFS_VENDOR_SAMSUNG, UFS_ANY_MODEL, UFS_DEVICE_NO_VCCQ), +-- +2.25.1 + diff --git a/queue-4.19/series b/queue-4.19/series index fe4063d63be..0acd9ae8bcf 100644 --- a/queue-4.19/series +++ b/queue-4.19/series @@ -16,3 +16,23 @@ jbd2-add-the-missing-unlock_buffer-in-the-error-path-of-jbd2_write_superblock.pa scsi-zfcp-fix-use-after-free-in-request-timeout-handlers.patch mm-memory.c-skip-spurious-tlb-flush-for-retried-page-fault.patch drm-amd-display-fix-pow-crashing-when-given-base-0.patch +kvm-arm64-only-reschedule-if-mmu_notifier_range_bloc.patch +spi-prevent-adding-devices-below-an-unregistering-co.patch +scsi-ufs-add-delay_before_lpm-quirk-for-micron-devic.patch +scsi-target-tcmu-fix-crash-in-tcmu_flush_dcache_rang.patch +media-budget-core-improve-exception-handling-in-budg.patch +rtc-goldfish-enable-interrupt-in-set_alarm-when-nece.patch +media-vpss-clean-up-resources-in-init.patch +input-psmouse-add-a-newline-when-printing-proto-by-s.patch +m68knommu-fix-overwriting-of-bits-in-coldfire-v3-cac.patch +svcrdma-fix-another-receive-buffer-leak.patch +xfs-fix-inode-quota-reservation-checks.patch +jffs2-fix-uaf-problem.patch +ceph-fix-use-after-free-for-fsc-mdsc.patch +cpufreq-intel_pstate-fix-cpuinfo_max_freq-when-msr_t.patch +scsi-libfc-free-skb-in-fc_disc_gpn_id_resp-for-valid.patch +virtio_ring-avoid-loop-when-vq-is-broken-in-virtqueu.patch +tools-testing-selftests-cgroup-cgroup_util.c-cg_read.patch +xfs-fix-ubsan-null-ptr-deref-in-xfs_sysfs_init.patch +alpha-fix-annotation-of-io-read-write-16-32-be.patch +fs-signalfd.c-fix-inconsistent-return-codes-for-sign.patch diff --git a/queue-4.19/spi-prevent-adding-devices-below-an-unregistering-co.patch b/queue-4.19/spi-prevent-adding-devices-below-an-unregistering-co.patch new file mode 100644 index 00000000000..ea25932e022 --- /dev/null +++ b/queue-4.19/spi-prevent-adding-devices-below-an-unregistering-co.patch @@ -0,0 +1,115 @@ +From 033c1f9e3943ba3429cd31bdb50c4f2428fe5370 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 3 Aug 2020 13:09:01 +0200 +Subject: spi: Prevent adding devices below an unregistering controller + +From: Lukas Wunner + +[ Upstream commit ddf75be47ca748f8b12d28ac64d624354fddf189 ] + +CONFIG_OF_DYNAMIC and CONFIG_ACPI allow adding SPI devices at runtime +using a DeviceTree overlay or DSDT patch. CONFIG_SPI_SLAVE allows the +same via sysfs. + +But there are no precautions to prevent adding a device below a +controller that's being removed. Such a device is unusable and may not +even be able to unbind cleanly as it becomes inaccessible once the +controller has been torn down. E.g. it is then impossible to quiesce +the device's interrupt. + +of_spi_notify() and acpi_spi_notify() do hold a ref on the controller, +but otherwise run lockless against spi_unregister_controller(). + +Fix by holding the spi_add_lock in spi_unregister_controller() and +bailing out of spi_add_device() if the controller has been unregistered +concurrently. + +Fixes: ce79d54ae447 ("spi/of: Add OF notifier handler") +Signed-off-by: Lukas Wunner +Cc: stable@vger.kernel.org # v3.19+ +Cc: Geert Uytterhoeven +Cc: Octavian Purdila +Cc: Pantelis Antoniou +Link: https://lore.kernel.org/r/a8c3205088a969dc8410eec1eba9aface60f36af.1596451035.git.lukas@wunner.de +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + drivers/spi/Kconfig | 3 +++ + drivers/spi/spi.c | 21 ++++++++++++++++++++- + 2 files changed, 23 insertions(+), 1 deletion(-) + +diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig +index 671d078349cc6..0a7fd56c1ed9d 100644 +--- a/drivers/spi/Kconfig ++++ b/drivers/spi/Kconfig +@@ -817,4 +817,7 @@ config SPI_SLAVE_SYSTEM_CONTROL + + endif # SPI_SLAVE + ++config SPI_DYNAMIC ++ def_bool ACPI || OF_DYNAMIC || SPI_SLAVE ++ + endif # SPI +diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c +index f589d8100e957..92e6b6774d98e 100644 +--- a/drivers/spi/spi.c ++++ b/drivers/spi/spi.c +@@ -432,6 +432,12 @@ static LIST_HEAD(spi_controller_list); + */ + static DEFINE_MUTEX(board_lock); + ++/* ++ * Prevents addition of devices with same chip select and ++ * addition of devices below an unregistering controller. ++ */ ++static DEFINE_MUTEX(spi_add_lock); ++ + /** + * spi_alloc_device - Allocate a new SPI device + * @ctlr: Controller to which device is connected +@@ -510,7 +516,6 @@ static int spi_dev_check(struct device *dev, void *data) + */ + int spi_add_device(struct spi_device *spi) + { +- static DEFINE_MUTEX(spi_add_lock); + struct spi_controller *ctlr = spi->controller; + struct device *dev = ctlr->dev.parent; + int status; +@@ -538,6 +543,13 @@ int spi_add_device(struct spi_device *spi) + goto done; + } + ++ /* Controller may unregister concurrently */ ++ if (IS_ENABLED(CONFIG_SPI_DYNAMIC) && ++ !device_is_registered(&ctlr->dev)) { ++ status = -ENODEV; ++ goto done; ++ } ++ + if (ctlr->cs_gpios) + spi->cs_gpio = ctlr->cs_gpios[spi->chip_select]; + +@@ -2306,6 +2318,10 @@ void spi_unregister_controller(struct spi_controller *ctlr) + struct spi_controller *found; + int id = ctlr->bus_num; + ++ /* Prevent addition of new devices, unregister existing ones */ ++ if (IS_ENABLED(CONFIG_SPI_DYNAMIC)) ++ mutex_lock(&spi_add_lock); ++ + device_for_each_child(&ctlr->dev, NULL, __unregister); + + /* First make sure that this controller was ever added */ +@@ -2326,6 +2342,9 @@ void spi_unregister_controller(struct spi_controller *ctlr) + if (found == ctlr) + idr_remove(&spi_master_idr, id); + mutex_unlock(&board_lock); ++ ++ if (IS_ENABLED(CONFIG_SPI_DYNAMIC)) ++ mutex_unlock(&spi_add_lock); + } + EXPORT_SYMBOL_GPL(spi_unregister_controller); + +-- +2.25.1 + diff --git a/queue-4.19/svcrdma-fix-another-receive-buffer-leak.patch b/queue-4.19/svcrdma-fix-another-receive-buffer-leak.patch new file mode 100644 index 00000000000..0bc5abc9d5f --- /dev/null +++ b/queue-4.19/svcrdma-fix-another-receive-buffer-leak.patch @@ -0,0 +1,45 @@ +From 1bce5bafd166a3390ef71bc46533a53ccc7c6cfb Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 30 Jun 2020 15:55:45 -0400 +Subject: svcrdma: Fix another Receive buffer leak + +From: Chuck Lever + +[ Upstream commit 64d26422516b2e347b32e6d9b1d40b3c19a62aae ] + +During a connection tear down, the Receive queue is flushed before +the device resources are freed. Typically, all the Receives flush +with IB_WR_FLUSH_ERR. + +However, any pending successful Receives flush with IB_WR_SUCCESS, +and the server automatically posts a fresh Receive to replace the +completing one. This happens even after the connection has closed +and the RQ is drained. Receives that are posted after the RQ is +drained appear never to complete, causing a Receive resource leak. +The leaked Receive buffer is left DMA-mapped. + +To prevent these late-posted recv_ctxt's from leaking, block new +Receive posting after XPT_CLOSE is set. + +Signed-off-by: Chuck Lever +Signed-off-by: Sasha Levin +--- + net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c b/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c +index 16c8174658fd1..252495ff9010d 100644 +--- a/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c ++++ b/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c +@@ -268,6 +268,8 @@ static int svc_rdma_post_recv(struct svcxprt_rdma *rdma) + { + struct svc_rdma_recv_ctxt *ctxt; + ++ if (test_bit(XPT_CLOSE, &rdma->sc_xprt.xpt_flags)) ++ return 0; + ctxt = svc_rdma_recv_ctxt_get(rdma); + if (!ctxt) + return -ENOMEM; +-- +2.25.1 + diff --git a/queue-4.19/tools-testing-selftests-cgroup-cgroup_util.c-cg_read.patch b/queue-4.19/tools-testing-selftests-cgroup-cgroup_util.c-cg_read.patch new file mode 100644 index 00000000000..2a1f69fc7ad --- /dev/null +++ b/queue-4.19/tools-testing-selftests-cgroup-cgroup_util.c-cg_read.patch @@ -0,0 +1,44 @@ +From c0af9a1d25e3cd4109effdedb5046863c5751441 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 6 Aug 2020 23:17:25 -0700 +Subject: tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix + null pointer dereference + +From: Gaurav Singh + +[ Upstream commit d830020656c5b68ced962ed3cb51a90e0a89d4c4 ] + +Haven't reproduced this issue. This PR is does a minor code cleanup. + +Signed-off-by: Gaurav Singh +Signed-off-by: Andrew Morton +Reviewed-by: Andrew Morton +Cc: Shuah Khan +Cc: Tejun Heo +Cc: Michal Koutn +Cc: Roman Gushchin +Cc: Christian Brauner +Cc: Chris Down +Link: http://lkml.kernel.org/r/20200726013808.22242-1-gaurav1086@gmail.com +Signed-off-by: Linus Torvalds +Signed-off-by: Sasha Levin +--- + tools/testing/selftests/cgroup/cgroup_util.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/tools/testing/selftests/cgroup/cgroup_util.c b/tools/testing/selftests/cgroup/cgroup_util.c +index 075cb0c730149..90418d79ef676 100644 +--- a/tools/testing/selftests/cgroup/cgroup_util.c ++++ b/tools/testing/selftests/cgroup/cgroup_util.c +@@ -95,7 +95,7 @@ int cg_read_strcmp(const char *cgroup, const char *control, + + /* Handle the case of comparing against empty string */ + if (!expected) +- size = 32; ++ return -1; + else + size = strlen(expected) + 1; + +-- +2.25.1 + diff --git a/queue-4.19/virtio_ring-avoid-loop-when-vq-is-broken-in-virtqueu.patch b/queue-4.19/virtio_ring-avoid-loop-when-vq-is-broken-in-virtqueu.patch new file mode 100644 index 00000000000..d334a22f601 --- /dev/null +++ b/queue-4.19/virtio_ring-avoid-loop-when-vq-is-broken-in-virtqueu.patch @@ -0,0 +1,53 @@ +From e1733c718a80ea5b745c394f86bfa31367252d44 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 2 Aug 2020 15:44:09 +0800 +Subject: virtio_ring: Avoid loop when vq is broken in virtqueue_poll + +From: Mao Wenan + +[ Upstream commit 481a0d7422db26fb63e2d64f0652667a5c6d0f3e ] + +The loop may exist if vq->broken is true, +virtqueue_get_buf_ctx_packed or virtqueue_get_buf_ctx_split +will return NULL, so virtnet_poll will reschedule napi to +receive packet, it will lead cpu usage(si) to 100%. + +call trace as below: +virtnet_poll + virtnet_receive + virtqueue_get_buf_ctx + virtqueue_get_buf_ctx_packed + virtqueue_get_buf_ctx_split + virtqueue_napi_complete + virtqueue_poll //return true + virtqueue_napi_schedule //it will reschedule napi + +to fix this, return false if vq is broken in virtqueue_poll. + +Signed-off-by: Mao Wenan +Acked-by: Michael S. Tsirkin +Link: https://lore.kernel.org/r/1596354249-96204-1-git-send-email-wenan.mao@linux.alibaba.com +Signed-off-by: Michael S. Tsirkin +Acked-by: Jason Wang +Signed-off-by: Sasha Levin +--- + drivers/virtio/virtio_ring.c | 3 +++ + 1 file changed, 3 insertions(+) + +diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c +index 6228b48d1e127..df7980aef927a 100644 +--- a/drivers/virtio/virtio_ring.c ++++ b/drivers/virtio/virtio_ring.c +@@ -828,6 +828,9 @@ bool virtqueue_poll(struct virtqueue *_vq, unsigned last_used_idx) + { + struct vring_virtqueue *vq = to_vvq(_vq); + ++ if (unlikely(vq->broken)) ++ return false; ++ + virtio_mb(vq->weak_barriers); + return (u16)last_used_idx != virtio16_to_cpu(_vq->vdev, vq->vring.used->idx); + } +-- +2.25.1 + diff --git a/queue-4.19/xfs-fix-inode-quota-reservation-checks.patch b/queue-4.19/xfs-fix-inode-quota-reservation-checks.patch new file mode 100644 index 00000000000..ff63d3e1b76 --- /dev/null +++ b/queue-4.19/xfs-fix-inode-quota-reservation-checks.patch @@ -0,0 +1,56 @@ +From 0a1b01086a532e9ea578145beddf28bb17a84c00 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 14 Jul 2020 10:36:09 -0700 +Subject: xfs: fix inode quota reservation checks + +From: Darrick J. Wong + +[ Upstream commit f959b5d037e71a4d69b5bf71faffa065d9269b4a ] + +xfs_trans_dqresv is the function that we use to make reservations +against resource quotas. Each resource contains two counters: the +q_core counter, which tracks resources allocated on disk; and the dquot +reservation counter, which tracks how much of that resource has either +been allocated or reserved by threads that are working on metadata +updates. + +For disk blocks, we compare the proposed reservation counter against the +hard and soft limits to decide if we're going to fail the operation. +However, for inodes we inexplicably compare against the q_core counter, +not the incore reservation count. + +Since the q_core counter is always lower than the reservation count and +we unlock the dquot between reservation and transaction commit, this +means that multiple threads can reserve the last inode count before we +hit the hard limit, and when they commit, we'll be well over the hard +limit. + +Fix this by checking against the incore inode reservation counter, since +we would appear to maintain that correctly (and that's what we report in +GETQUOTA). + +Signed-off-by: Darrick J. Wong +Reviewed-by: Allison Collins +Reviewed-by: Chandan Babu R +Reviewed-by: Christoph Hellwig +Signed-off-by: Sasha Levin +--- + fs/xfs/xfs_trans_dquot.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/fs/xfs/xfs_trans_dquot.c b/fs/xfs/xfs_trans_dquot.c +index c23257a26c2b8..b8f05d5909b59 100644 +--- a/fs/xfs/xfs_trans_dquot.c ++++ b/fs/xfs/xfs_trans_dquot.c +@@ -657,7 +657,7 @@ xfs_trans_dqresv( + } + } + if (ninos > 0) { +- total_count = be64_to_cpu(dqp->q_core.d_icount) + ninos; ++ total_count = dqp->q_res_icount + ninos; + timer = be32_to_cpu(dqp->q_core.d_itimer); + warns = be16_to_cpu(dqp->q_core.d_iwarns); + warnlimit = dqp->q_mount->m_quotainfo->qi_iwarnlimit; +-- +2.25.1 + diff --git a/queue-4.19/xfs-fix-ubsan-null-ptr-deref-in-xfs_sysfs_init.patch b/queue-4.19/xfs-fix-ubsan-null-ptr-deref-in-xfs_sysfs_init.patch new file mode 100644 index 00000000000..11ead7f442c --- /dev/null +++ b/queue-4.19/xfs-fix-ubsan-null-ptr-deref-in-xfs_sysfs_init.patch @@ -0,0 +1,59 @@ +From 147b10b82eb8183d079606d2961f07d0a00031c6 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 6 Aug 2020 15:18:48 -0700 +Subject: xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init + +From: Eiichi Tsukata + +[ Upstream commit 96cf2a2c75567ff56195fe3126d497a2e7e4379f ] + +If xfs_sysfs_init is called with parent_kobj == NULL, UBSAN +shows the following warning: + + UBSAN: null-ptr-deref in ./fs/xfs/xfs_sysfs.h:37:23 + member access within null pointer of type 'struct xfs_kobj' + Call Trace: + dump_stack+0x10e/0x195 + ubsan_type_mismatch_common+0x241/0x280 + __ubsan_handle_type_mismatch_v1+0x32/0x40 + init_xfs_fs+0x12b/0x28f + do_one_initcall+0xdd/0x1d0 + do_initcall_level+0x151/0x1b6 + do_initcalls+0x50/0x8f + do_basic_setup+0x29/0x2b + kernel_init_freeable+0x19f/0x20b + kernel_init+0x11/0x1e0 + ret_from_fork+0x22/0x30 + +Fix it by checking parent_kobj before the code accesses its member. + +Signed-off-by: Eiichi Tsukata +Reviewed-by: Darrick J. Wong +[darrick: minor whitespace edits] +Signed-off-by: Darrick J. Wong +Signed-off-by: Sasha Levin +--- + fs/xfs/xfs_sysfs.h | 6 ++++-- + 1 file changed, 4 insertions(+), 2 deletions(-) + +diff --git a/fs/xfs/xfs_sysfs.h b/fs/xfs/xfs_sysfs.h +index e9f810fc67317..43585850f1546 100644 +--- a/fs/xfs/xfs_sysfs.h ++++ b/fs/xfs/xfs_sysfs.h +@@ -32,9 +32,11 @@ xfs_sysfs_init( + struct xfs_kobj *parent_kobj, + const char *name) + { ++ struct kobject *parent; ++ ++ parent = parent_kobj ? &parent_kobj->kobject : NULL; + init_completion(&kobj->complete); +- return kobject_init_and_add(&kobj->kobject, ktype, +- &parent_kobj->kobject, "%s", name); ++ return kobject_init_and_add(&kobj->kobject, ktype, parent, "%s", name); + } + + static inline void +-- +2.25.1 +