[PATCH RT 00/24] Linux 4.14.63-rt41-rc2

Dear RT Folks, This is the RT stable review cycle of patch 4.14.63-rt41-rc2. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release

[PATCH RT 07/24] seqlock: provide the same ordering semantics as mainline

4.14.63-rt41-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Julia Cartwright [ Upstream commit afa4c06b89a3c0fb7784ff900ccd707bef519cb7 ] The mainline implementation of read_seqbegin() orders prior loads w.r.t. the read-side critical

[PATCH RT 12/24] irqchip/gic-v3-its: Move ITS ->pend_page allocation into an early CPU up hook

4.14.63-rt41-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior [ Upstream commit e083f14dc2e98ced872bf077b4d1cccf95b7e4f8 ] The AP-GIC-starting hook allocates memory for the ->pend_page while the CPU is started during

[PATCH RT 05/24] PM / wakeup: Make events_lock a RAW_SPINLOCK

4.14.63-rt41-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior [ Upstream commit 1debb85a1d7d5c7655b4574f5b0ddf5f7c84873e ] The `events_lock' is acquired during suspend while interrupts are disabled even on RT. The

[PATCH RT 03/24] squashfs: make use of local lock in multi_cpu decompressor

4.14.63-rt41-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Julia Cartwright [ Upstream commit c160736542d7b3d67da32848d2f028b8e35730e5 ] Currently, the squashfs multi_cpu decompressor makes use of get_cpu_ptr()/put_cpu_ptr(), which

[PATCH 4.18 079/145] uprobes: Use synchronize_rcu() not synchronize_sched()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit 016f8ffc48cb01d1e7701649c728c5d2e737d295 upstream. While debugging another bug, I was looking at all the synchronize*() functions being used in kernel/trace,

[PATCH 4.18 081/145] ovl: fix wrong use of impure dir cache in ovl_iterate()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Amir Goldstein commit 67810693077afc1ebf9e1646af300436cb8103c2 upstream. Only upper dir can be impure, but if we are in the middle of iterating a lower real dir, dir could be copied up and

[PATCH 4.18 087/145] cpufreq: governor: Avoid accessing invalid governor_data

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Henry Willard commit 2a3eb51e30b9ac66fe1b75877627a7e4aaeca24a upstream. If cppc_cpufreq.ko is deleted at the same time that tuned-adm is changing profiles, there is a small chance that a race

[PATCH 4.18 083/145] ACPICA: Clear status of all events when entering sleep states

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit f317c7dc12b73eb9d67fdae404563deb907dcfb7 upstream. Commit fa85015c0d95 (ACPICA: Clear status of all events when entering S5) made the sleep state entry code in ACPICA

[PATCH 4.18 085/145] sched: idle: Avoid retaining the tick when it has been stopped

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 7059b36636beab57c3c43c62104483e5449bee95 upstream. If the tick has been stopped already, but the governor has not asked to stop it (which it can do sometimes), the

[PATCH 4.18 084/145] drivers/block/zram/zram_drv.c: fix bug storing backing_dev

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Peter Kalauskas commit c8bd134a4bddafe5917d163eea73873932c15e83 upstream. The call to strlcpy in backing_dev_store is incorrect. It should take the size of the destination buffer instead of

[PATCH 4.18 078/145] livepatch: Validate module/old func name length

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kamalesh Babulal commit 6e9df95b76cad18f7b217bdad7bb8a26d63b8c47 upstream. livepatch module author can pass module name/old function name with more than the defined character limit. With

[PATCH 4.18 077/145] printk/tracing: Do not trace printk_nmi_enter()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit d1c392c9e2a301f38998a353f467f76414e38725 upstream. I hit the following splat in my tests: [ cut here ] IRQs not enabled as expected

[PATCH 4.18 071/145] vmw_balloon: VMCI_DOORBELL_SET does not check status

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Nadav Amit commit ce664331b2487a5d244a51cbdd8cb54f866fbe5d upstream. When vmballoon_vmci_init() sets a doorbell using VMCI_DOORBELL_SET, for some reason it does not consider the status and

[PATCH 4.18 073/145] rtc: omap: fix resource leak in registration error path

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 551757eb052986ec81cebcc6301cc1c4f8dca938 upstream. Make sure to deregister the pin controller in case rtc registration fails. Fixes: 57072758623f ("rtc: omap: switch to

[PATCH 4.18 029/145] powerpc/pkeys: Give all threads control of their key permissions

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ram Pai commit a57a04c76e06822e4377831611364c846b7202ca upstream. Currently in a multithreaded application, a key allocated by one thread is not usable by other threads. By "not usable" we

[PATCH 4.18 060/145] dm writecache: fix a crash due to reading past end of dirty_bitmap

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 1e1132ea21da6d7be92a72195204379c819cb70b upstream. wc->dirty_bitmap_size is in bytes so must multiply it by 8, not by BITS_PER_LONG, to get number of bitmap_bits.

[PATCH 4.18 075/145] tracing: Do not call start/stop() functions when tracing_on does not change

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit f143641bfef9a4a60c57af30de26c63057e7e695 upstream. Currently, when one echo's in 1 into tracing_on, the current tracer's "start()" function is executed, even if

[PATCH 4.18 037/145] powerpc/powernv/pci: Work around races in PCI bridge enabling

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Herrenschmidt commit db2173198b9513f7add8009f225afa1f1c79bcc6 upstream. The generic code is racy when multiple children of a PCI bridge try to enable it simultaneously. This leads

[PATCH 4.18 038/145] cxl: Fix wrong comparison in cxl_adapter_context_get()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vaibhav Jain commit ef6cb5f1a048fdf91ccee6d63d2bfa293338502d upstream. Function atomic_inc_unless_negative() returns a bool to indicate success/failure. However cxl_adapter_context_get()

[PATCH 4.18 036/145] powerpc64/ftrace: Include ftrace.h needed for enable/disable calls

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Luke Dashjr commit d6ee76d3d37d156c479348821574b6f99d6472a1 upstream. this_cpu_disable_ftrace and this_cpu_enable_ftrace are inlines in ftrace.h Without it included, the build fails. Fixes:

[PATCH 4.18 033/145] powerpc/pkeys: Fix calculation of total pkeys.

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ram Pai commit fe6a2804e65969a574377bdb3605afb79e6091a9 upstream. Total number of pkeys calculation is off by 1. Fix it. Fixes: 4fb158f65ac5 ("powerpc: track allocation status of all pkeys")

[PATCH 4.18 058/145] dm cache metadata: set dirty on all cache blocks after a crash

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 5b1fe7bec8a8d0cc547a22e7ddc2bd59acd67de4 upstream. Quoting Documentation/device-mapper/cache.txt: The 'dirty' state for a cache block changes far too frequently for us

[PATCH 4.18 057/145] dm cache metadata: save in-core policy_hint_size to on-disk superblock

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit fd2fa95416188a767a63979296fa3e169a9ef5ec upstream. policy_hint_size starts as 0 during __write_initial_superblock(). It isn't until the policy is loaded that

[PATCH 4.18 074/145] rtc: omap: fix potential crash on power off

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 5c8b84f410b3819d14cb1ebf32e4b3714b5a6e0b upstream. Do not set the system power-off callback and omap power-off rtc pointer until we're done setting up our device to avoid

[PATCH 4.18 063/145] Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dexuan Cui commit d3b26dd7cb0e3433bfd3c1d4dcf74c6039bb49fb upstream. Before setting channel->rescind in vmbus_rescind_cleanup(), we should make sure the channel callback won't run any more,

[PATCH 4.18 080/145] mfd: hi655x: Fix regmap area declared size for hi655x

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rafael David Tinoco commit 6afebb70ee7a4bde106dc1a875e7ac7997248f84 upstream. Fixes https://bugs.linaro.org/show_bug.cgi?id=3903 LTP Functional tests have caused a bad paging request when

[PATCH 4.18 086/145] cpuidle: menu: Handle stopped tick more aggressively

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 5ef499cd571c293b74a30d77e7ef512edb6ded6b upstream. Commit 87c9fe6ee495 (cpuidle: menu: Avoid selecting shallow states with stopped tick) missed the case when the

[PATCH 4.18 089/145] ALSA: ac97: fix device initialization in the compat layer

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Lihua Yao commit c7b8170790c19293acd835dc50b8247ec207d4a3 upstream. ac97->dev is an object of 'struct device' type. It should be initialized via device_initialize() or device_register().

[PATCH 4.18 090/145] ALSA: ac97: fix check of pm_runtime_get_sync failure

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Lihua Yao commit d15ec0b482ff502e4e19e43d15aa5072e4290199 upstream. pm_runtime_get_sync returns negative on failure. Fixes: 74426fbff66e ("ALSA: ac97: add an ac97 bus") Signed-off-by: Lihua

[PATCH 4.18 064/145] iio: sca3000: Fix missing return in switch

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit c5b974bee9d2ceae4c441ae5a01e498c2674e100 upstream. The IIO_CHAN_INFO_LOW_PASS_FILTER_3DB_FREQUENCY case is missing a return and will fall through to the default

[PATCH 4.18 088/145] PM / sleep: wakeup: Fix build error caused by missing SRCU support

4.18-stable review patch. If anyone has any objections, please let me know. -- From: zhangyi (F) commit 3df6f61fff49632492490fb6e42646b803a9958a upstream. Commit ea0212f40c6 (power: auto select CONFIG_SRCU) made the code in drivers/base/power/wakeup.c use SRCU instead of RCU,

[PATCH 4.18 082/145] ACPICA: AML Parser: skip opcodes that open a scope upon parse failure

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Erik Schmauss commit 4a7c94c721074eafb27298d93dbcc339aa28e745 upstream. This change skips the entire length of opcodes that open a scope (Device, Scope, Processor, etc) if the creation of the

[PATCH 4.18 072/145] vmw_balloon: fix VMCI use when balloon built into kernel

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Nadav Amit commit c3cc1b0fc27508da53fe955a3b23d03964410682 upstream. Currently, when all modules, including VMCI and VMware balloon are built into the kernel, the initialization of the

[PATCH 4.18 110/145] sys: dont hold uts_sem while accessing userspace memory

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit 42a0cc3478584d4d63f68f2f5af021ddbea771fa upstream. Holding uts_sem as a writer while accessing userspace memory allows a namespace admin to stall all processes that attempt

[PATCH 4.18 095/145] xtensa: limit offsets in __loop_cache_{all,page}

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit be75de25251f7cf3e399ca1f584716a95510d24a upstream. When building kernel for xtensa cores with big cache lines (e.g. 128 bytes or more) __loop_cache_all and

[PATCH 4.18 107/145] iommu/ipmmu-vmsa: Dont register as BUS IOMMU if machine doesnt have IPMMU-VMSA

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Osipenko commit 5c5c87411488af3cd082221e567498d813d0fe83 upstream. This fixes kernel crashing on NVIDIA Tegra if kernel is compiled in a multiplatform configuration and IPMMU-VMSA

[PATCH 4.18 112/145] ubifs: Fix memory leak in lprobs self-check

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit eef19816ada3abd56d9f20c88794cc2fea83ebb2 upstream. Allocate the buffer after we return early. Otherwise memory is being leaked. Cc: Fixes: 1e51764a3c2a ("UBIFS:

[PATCH 4.18 111/145] userns: move user access out of the mutex

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit 5820f140edef111a9ea2ef414ab2428b8cb805b1 upstream. The old code would hold the userns_state_mutex indefinitely if memdup_user_nul stalled due to e.g. a userfault region.

[PATCH 4.18 115/145] ubifs: xattr: Dont operate on deleted inodes

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit 11a6fc3dc743e22fb50f2196ec55bee5140d3c52 upstream. xattr operations can race with unlink and the following assert triggers: UBIFS assert failed in

[PATCH 4.18 109/145] iommu/vt-d: Fix dev iotlb pfsid use

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jacob Pan commit 1c48db44924298ad0cb5a6386b88017539be8822 upstream. PFSID should be used in the invalidation descriptor for flushing device IOTLBs on SRIOV VFs. Signed-off-by: Jacob Pan Cc:

[PATCH 4.18 108/145] iommu/vt-d: Add definitions for PFSID

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jacob Pan commit 0f725561e168485eff7277d683405c05b192f537 upstream. When SRIOV VF device IOTLB is invalidated, we need to provide the PF source ID such that IOMMU hardware can gauge the depth

[PATCH 4.18 106/145] mm/tlb: Remove tlb_remove_table() non-concurrent condition

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit a6f572084fbee8b30f91465f4a085d7a90901c57 upstream. Will noted that only checking mm_users is incorrect; we should also check mm_count in order to cover CPUs that have a

[PATCH 4.18 104/145] ARM: dts: am57xx-idk: Enable dual role for USB2 port

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Roger Quadros commit 5f3cc16483d40bbc609a828511ff851296fc62b6 upstream. Dual-role support was added in v4.12. We should be using it for USB2 port on the am57xx-idk. Cc: [4.16+]

[PATCH 4.18 105/145] pwm: omap-dmtimer: Return -EPROBE_DEFER if no dmtimer platform data

4.18-stable review patch. If anyone has any objections, please let me know. -- From: David Rivshin commit 43725feb593127b16318b871e3a9bf89a96d66cb upstream. If a pwm-omap-dmtimer is probed before the dmtimer it uses, the platform data won't be set yet. Fixes: ac30751df953

[PATCH 4.18 143/145] udf: Fix mounting of Win7 created UDF filesystems

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit ee4af50ca94f58afc3532662779b9cf80bbe27c8 upstream. Win7 is creating UDF filesystems with single partition with number 8192. Current partition descriptor scanning code does not

[PATCH 4.18 130/145] libnvdimm: fix ars_status output length calculation

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vishal Verma commit 286e87718103acdf85f4ed323a37e4839a8a7c05 upstream. Commit efda1b5d87cb ("acpi, nfit, libnvdimm: fix / harden ars_status output length handling") Introduced additional

[PATCH 4.18 144/145] cpuidle: menu: Retain tick when shallow state is selected

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 757ab15c3f4968b5a29caf3fe8b67660ce84c3cd upstream. The case addressed by commit 5ef499cd571c (cpuidle: menu: Handle stopped tick more aggressively) in the stopped

[PATCH 4.18 145/145] arm64: mm: always enable CONFIG_HOLES_IN_ZONE

4.18-stable review patch. If anyone has any objections, please let me know. -- From: James Morse commit f52bb98f5aded4c43e52f5ce19fb83f7261e9e73 upstream. Commit 6d526ee26ccd ("arm64: mm: enable CONFIG_HOLES_IN_ZONE for NUMA") only enabled HOLES_IN_ZONE for NUMA systems

[PATCH 4.18 137/145] crypto: aesni - Use unaligned loads from gcm_context_data

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dave Watson commit e5b954e8d11fdde55eed35017370a3a0d8837754 upstream. A regression was reported bisecting to 1476db2d12 "Move HashKey computation from stack to gcm_context". That diff moved

[PATCH 4.18 138/145] crypto: arm64/sm4-ce - check for the right CPU feature bit

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 7fa885e2a22fd0f91a2c23d9275f5021f618ff5a upstream. ARMv8.2 specifies special instructions for the SM3 cryptographic hash and the SM4 symmetric cipher. While it is

[PATCH 4.18 128/145] getxattr: use correct xattr length

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christian Brauner commit 82c9a927bc5df6e06b72d206d24a9d10cced4eb5 upstream. When running in a container with a user namespace, if you call getxattr with name = "system.posix_acl_access" and

[PATCH 4.18 129/145] libnvdimm: Use max contiguous area for namespace size

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Keith Busch commit 12e3129e29b406c41bc89231092a20d79dbf802c upstream. This patch will find the max contiguous area to determine the largest pmem namespace size that can be created. If the

[PATCH 4.18 133/145] cap_inode_getsecurity: use d_find_any_alias() instead of d_find_alias()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Eddie.Horng commit 355139a8dba446cc11a424cddbf7afebc3041ba1 upstream. The code in cap_inode_getsecurity(), introduced by commit 8db6c34f1dbc ("Introduce v3 namespaced file capabilities"),

[PATCH 4.18 126/145] udlfb: handle allocation failure

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 080fb5240bdcabed7387b814139c3ea172d59fc5 upstream. Allocations larger than PAGE_ALLOC_COSTLY_ORDER are unreliable and they may fail anytime. This patch fixes the udlfb

[PATCH 4.18 132/145] kconfig: fix "Cant open ..." in parallel build

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Masahiro Yamada commit 98a4afbfafd226636cd6bb6a1208b3693daff2b1 upstream. If you run "make menuconfig" or "make nconfig" with -j option in a fresh source tree, you will see several "Can't

[PATCH 4.14 01/89] net: 6lowpan: fix reserved space for single frames

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Aring commit ac74f87c789af40936a80131c4759f3e72579c3a upstream. This patch fixes patch add handling to take care tail and headroom for single 6lowpan frames. We need to be sure we

[PATCH 4.14 10/89] block: blk_init_allocated_queue() set q->fq as NULL in the fail case

4.14-stable review patch. If anyone has any objections, please let me know. -- From: xiao jin commit 54648cf1ec2d7f4b6a71767799c45676a138ca24 upstream. We find the memory use-after-free issue in __blk_drain_queue() on the kernel 4.14. After read the latest kernel 4.18-rc6 we

[PATCH 4.18 142/145] fs/quota: Fix spectre gadget in do_quotactl

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Cline commit 7b6924d94a60c6b8c1279ca003e8744e6cd9e8b1 upstream. 'type' is user-controlled, so sanitize it after the bounds check to avoid using it in speculative execution. This covers

[PATCH 4.18 131/145] bcache: release dc->writeback_lock properly in bch_writeback_thread()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Shan Hai commit 3943b040f11ed0cc6d4585fd286a623ca8634547 upstream. The writeback thread would exit with a lock held when the cache device is detached via sysfs interface, fix it by releasing

[PATCH 4.18 136/145] crypto: vmx - Fix sleep-in-atomic bugs

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ondrej Mosnacek commit 0522236d4f9c5ab2e79889cb020d1acbe5da416e upstream. This patch fixes sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations. The problem is that the blkcipher_*

[PATCH 4.14 25/89] fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr failed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: piaojun commit 3111784bee81591ea2815011688d28b65df03627 upstream. In my testing, v9fs_fid_xattr_set will return successfully even if the backend ext4 filesystem has no space to store xattr

[PATCH 4.14 56/89] KVM: PPC: Book3S: Fix guest DMA when guest partially backed by THP pages

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 8cfbdbdc24815417a3ab35101ccf706b9a23ff17 upstream. Commit 76fa4975f3ed ("KVM: PPC: Check if IOMMU page is contained in the pinned physical page", 2018-07-17) added some

[PATCH 4.14 57/89] xtensa: limit offsets in __loop_cache_{all,page}

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit be75de25251f7cf3e399ca1f584716a95510d24a upstream. When building kernel for xtensa cores with big cache lines (e.g. 128 bytes or more) __loop_cache_all and

[PATCH 4.14 24/89] 9p: fix multiple NULL-pointer-dereferences

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tomas Bortoli commit 10aa14527f458e9867cf3d2cc6b8cb0f6704448b upstream. Added checks to prevent GPFs from raising. Link: http://lkml.kernel.org/r/20180727110558.5479-1-tomasbort...@gmail.com

[PATCH 4.14 38/89] iio: ad9523: Fix return value for ad952x_store()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen commit 9a5094ca29ea9b1da301b31fd377c0c0c4c23034 upstream. A sysfs write callback function needs to either return the number of consumed characters or an error. The

[PATCH 4.14 23/89] RDMA/rxe: Set wqe->status correctly if an unexpected response is received

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 61b717d041b1976530f68f8b539b2e3a7dd8e39c upstream. Every function that returns COMPST_ERROR must set wqe->status to another value than IB_WC_SUCCESS before returning

Re: [PATCH v4 2/2] x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation

On Fri, 7 Sep 2018, Thomas Gleixner wrote: > > + * The read-modify-write of the MSR doesn't need any race protection here, > > + * as we're running in atomic context. > > + */ > > +static void enable_stibp(void *info) > > +{ > > + u64 mask; > > + rdmsrl(MSR_IA32_SPEC_CTRL, mask); > > + mask

[PATCH] f2fs: submit bio after shutdown

Sometimes, some merged IOs could get a chance to be submitted, resulting in system hang in shutdown test. This issues IOs all the time after shutdown. Signed-off-by: Jaegeuk Kim --- fs/f2fs/data.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c index

[PATCH 4.14 53/89] cpufreq: governor: Avoid accessing invalid governor_data

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Henry Willard commit 2a3eb51e30b9ac66fe1b75877627a7e4aaeca24a upstream. If cppc_cpufreq.ko is deleted at the same time that tuned-adm is changing profiles, there is a small chance that a race

[PATCH 4.14 47/89] printk/tracing: Do not trace printk_nmi_enter()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit d1c392c9e2a301f38998a353f467f76414e38725 upstream. I hit the following splat in my tests: [ cut here ] IRQs not enabled as expected

[PATCH 4.14 51/89] ovl: fix wrong use of impure dir cache in ovl_iterate()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Amir Goldstein commit 67810693077afc1ebf9e1646af300436cb8103c2 upstream. Only upper dir can be impure, but if we are in the middle of iterating a lower real dir, dir could be copied up and

[PATCH 4.14 52/89] drivers/block/zram/zram_drv.c: fix bug storing backing_dev

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Kalauskas commit c8bd134a4bddafe5917d163eea73873932c15e83 upstream. The call to strlcpy in backing_dev_store is incorrect. It should take the size of the destination buffer instead of

[PATCH 4.14 29/89] dm integrity: change suspending variable from bool to int

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit c21b16392701543d61e366dca84e15fe7f0cf0cf upstream. Early alpha processors can't write a byte or short atomically - they read 8 bytes, modify the byte or two bytes in

[PATCH 4.14 54/89] PM / sleep: wakeup: Fix build error caused by missing SRCU support

4.14-stable review patch. If anyone has any objections, please let me know. -- From: zhangyi (F) commit 3df6f61fff49632492490fb6e42646b803a9958a upstream. Commit ea0212f40c6 (power: auto select CONFIG_SRCU) made the code in drivers/base/power/wakeup.c use SRCU instead of RCU,

[PATCH 4.14 50/89] mfd: hi655x: Fix regmap area declared size for hi655x

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rafael David Tinoco commit 6afebb70ee7a4bde106dc1a875e7ac7997248f84 upstream. Fixes https://bugs.linaro.org/show_bug.cgi?id=3903 LTP Functional tests have caused a bad paging request when

[PATCH 4.14 26/89] 9p/virtio: fix off-by-one error in sg list bounds check

4.14-stable review patch. If anyone has any objections, please let me know. -- From: jiangyiwen commit 23cba9cbde0bba05d772b335fe5f66aa82b9ad19 upstream. Because the value of limit is VIRTQUEUE_NUM, if index is equal to limit, it will cause sg array out of bounds, so correct

[PATCH 4.14 55/89] KVM: VMX: fixes for vmentry_l1d_flush module parameter

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 0027ff2a75f9dcf0537ac0a65c5840b0e21a4950 upstream. Two bug fixes: 1) missing entries in the l1d_param array; this can cause a host crash if an access attempts to reach

[PATCH 4.14 28/89] net/9p/trans_fd.c: fix race-condition by flushing workqueue before the kfree()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tomas Bortoli commit 430ac66eb4c5b5c4eb846b78ebf65747510b30f1 upstream. The patch adds the flush in p9_mux_poll_stop() as it the function used by p9_conn_destroy(), in turn called by

[PATCH 4.14 27/89] net/9p/client.c: version pointer uninitialized

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tomas Bortoli commit 7913690dcc5e18e235769fd87c34143072f5dbea upstream. The p9_client_version() does not initialize the version pointer. If the call to p9pdu_readf() returns an error and

[PATCH 4.14 88/89] fs/quota: Fix spectre gadget in do_quotactl

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Cline commit 7b6924d94a60c6b8c1279ca003e8744e6cd9e8b1 upstream. 'type' is user-controlled, so sanitize it after the bounds check to avoid using it in speculative execution. This covers

[PATCH 4.14 89/89] arm64: mm: always enable CONFIG_HOLES_IN_ZONE

4.14-stable review patch. If anyone has any objections, please let me know. -- From: James Morse commit f52bb98f5aded4c43e52f5ce19fb83f7261e9e73 upstream. Commit 6d526ee26ccd ("arm64: mm: enable CONFIG_HOLES_IN_ZONE for NUMA") only enabled HOLES_IN_ZONE for NUMA systems

[PATCH 4.14 61/89] NFSv4 client live hangs after live data migration recovery

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bill Baker commit 0f90be132cbf1537d87a6a8b9e80867adac892f6 upstream. After a live data migration event at the NFS server, the client may send I/O requests to the wrong server, causing a live

Re: Redoing eXclusive Page Frame Ownership (XPFO) with isolated CPUs in mind (for KVM to isolate its guests per CPU)

On 08/30/2018 10:00 AM, Julian Stecklina wrote: Hey everyone, On Mon, 20 Aug 2018 15:27 Linus Torvalds wrote: On Mon, Aug 20, 2018 at 3:02 PM Woodhouse, David wrote: It's the *kernel* we don't want being able to access those pages, because of the multitude of unfixable cache load gadgets.

[PATCH 4.14 82/89] cap_inode_getsecurity: use d_find_any_alias() instead of d_find_alias()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eddie.Horng commit 355139a8dba446cc11a424cddbf7afebc3041ba1 upstream. The code in cap_inode_getsecurity(), introduced by commit 8db6c34f1dbc ("Introduce v3 namespaced file capabilities"),

[PATCH 4.14 84/89] crypto: vmx - Fix sleep-in-atomic bugs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ondrej Mosnacek commit 0522236d4f9c5ab2e79889cb020d1acbe5da416e upstream. This patch fixes sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations. The problem is that the blkcipher_*

[PATCH 4.14 83/89] perf auxtrace: Fix queue resize

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 99cbbe56eb8bede625f410ab62ba34673ffa7d21 upstream. When the number of queues grows beyond 32, the array of queues is resized but not all members were being copied. Fix by

[PATCH 4.14 81/89] bcache: release dc->writeback_lock properly in bch_writeback_thread()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Shan Hai commit 3943b040f11ed0cc6d4585fd286a623ca8634547 upstream. The writeback thread would exit with a lock held when the cache device is detached via sysfs interface, fix it by releasing

[PATCH 4.9 46/63] osf_getdomainname(): use copy_to_user()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 9ba3eb5103cf56f0daaf07de4507df76e7813ed7 upstream. Signed-off-by: Al Viro Signed-off-by: Greg Kroah-Hartman --- arch/alpha/kernel/osf_sys.c | 23 +-- 1

[PATCH 4.9 47/63] sys: dont hold uts_sem while accessing userspace memory

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit 42a0cc3478584d4d63f68f2f5af021ddbea771fa upstream. Holding uts_sem as a writer while accessing userspace memory allows a namespace admin to stall all processes that attempt to

[PATCH 4.9 44/63] iommu/vt-d: Add definitions for PFSID

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jacob Pan commit 0f725561e168485eff7277d683405c05b192f537 upstream. When SRIOV VF device IOTLB is invalidated, we need to provide the PF source ID such that IOMMU hardware can gauge the depth

[PATCH 4.9 45/63] iommu/vt-d: Fix dev iotlb pfsid use

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jacob Pan commit 1c48db44924298ad0cb5a6386b88017539be8822 upstream. PFSID should be used in the invalidation descriptor for flushing device IOTLBs on SRIOV VFs. Signed-off-by: Jacob Pan Cc:

[PATCH 4.9 41/63] Replace magic for trusting the secondary keyring with #define

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Yannik Sembritzki commit 817aef260037f33ee0f44c17fe341323d3aebd6d upstream. Replace the use of a magic number that indicates that verify_*_signature() should use the secondary keyring with a

[PATCH 4.9 32/63] mfd: hi655x: Fix regmap area declared size for hi655x

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Rafael David Tinoco commit 6afebb70ee7a4bde106dc1a875e7ac7997248f84 upstream. Fixes https://bugs.linaro.org/show_bug.cgi?id=3903 LTP Functional tests have caused a bad paging request when

[PATCH 4.9 48/63] userns: move user access out of the mutex

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit 5820f140edef111a9ea2ef414ab2428b8cb805b1 upstream. The old code would hold the userns_state_mutex indefinitely if memdup_user_nul stalled due to e.g. a userfault region.

[PATCH 4.9 49/63] ubifs: Fix memory leak in lprobs self-check

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit eef19816ada3abd56d9f20c88794cc2fea83ebb2 upstream. Allocate the buffer after we return early. Otherwise memory is being leaked. Cc: Fixes: 1e51764a3c2a ("UBIFS: add

kselftests for memory.oom.group

Here is the third version of the patchset. Changes since the last patchset: - Updated commit message of first patch to clarify fixes - Add ack from Roman There should be no code changes since the last patchset. Let me know if any improvements can be made, and thanks for your time! -Jay

[PATCH 4.4 03/47] 9p/net: Fix zero-copy path in the 9p virtio transport

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chirantan Ekbote commit d28c756caee6e414d9ba367d0b92da24145af2a8 upstream. The zero-copy optimization when reading or writing large chunks of data is quite useful. However, the 9p messages

[PATCH 4.4 29/47] mm/tlb: Remove tlb_remove_table() non-concurrent condition

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit a6f572084fbee8b30f91465f4a085d7a90901c57 upstream. Will noted that only checking mm_users is incorrect; we should also check mm_count in order to cover CPUs that have a

[PATCH 4.4 28/47] ARM: tegra: Fix Tegra30 Cardhu PCA954x reset

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jon Hunter commit 6e1811900b6fe6f2b4665dba6bd6ed32c6b98575 upstream. On all versions of Tegra30 Cardhu, the reset signal to the NXP PCA9546 I2C mux is connected to the Tegra GPIO BB0.

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