[PATCH 4.14 041/183] af_key: unconditionally clone on broadcast

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fc2d5cfdcfe2ab76b263d91429caa22451123085 ] Attempting to avoid cloning the skb when broadcasting by inflating the refcount with sock_hold/sock_put while under RCU lock is dangerous

Re: [PATCH] csky: remove redundant generic-y

Thx Masahiro, Approved and I'll add it into my tree. Best Regards Guo Ren On Fri, Mar 22, 2019 at 08:19:14PM +0900, Masahiro Yamada wrote: > Since commit 7c8bc297 ("kbuild: warn redundant generic-y"), > redundant generic-y is reported. I missed to delete this one. > >

[PATCH 4.14 070/183] libnvdimm/pmem: Honor force_raw for legacy pmem regions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit fa7d2e639cd90442d868dfc6ca1d4cc9d8bf206e upstream. For recovery, where non-dax access is needed to a given physical address range, and testing, allow the 'force_raw'

[PATCH 4.14 068/183] libnvdimm/label: Clear updating flag after label-set update

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 966d23a006ca7b44ac8cf4d0c96b19785e0c3da0 upstream. The UEFI 2.7 specification sets expectations that the 'updating' flag is eventually cleared. To date, the libnvdimm core

Re: [PATCH 0/4] Signal: Fix hard lockup problem in flush_sigqueue()

On 03/22, Matthew Wilcox wrote: > > On Thu, Mar 21, 2019 at 05:45:08PM -0400, Waiman Long wrote: > > It was found that if a process has accumulated sufficient number of > > pending signals, the exiting of that process may cause its parent to > > have hard lockup when running on a debug kernel with

[PATCH 4.14 067/183] stm class: Prevent division by zero

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit bf7cbaae0831252b416f375ca9b1027ecd4642dd upstream. Using STP_POLICY_ID_SET ioctl command with dummy_stm device, or any STM device that supplies zero mmio channel

[PATCH 4.14 055/183] ixgbe: fix older devices that do not support IXGBE_MRQC_L3L4TXSWEN

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 156a67a9065e3339be85f811d1b13b920e50d73b ] The enabling L3/L4 filtering for transmit switched packets for all devices caused unforeseen issue on older devices when trying to send

[PATCH 4.14 058/183] ARCv2: support manual regfile save on interrupts

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e494239a007e601448110ac304fe055951f9de3b ] There's a hardware bug which affects the HSDK platform, triggered by micro-ops for auto-saving regfile on taken interrupt. The workaround

[PATCH 4.14 062/183] nfp: bpf: fix code-gen bug on BPF_ALU | BPF_XOR | BPF_K

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 71c190249f0ced5b26377ea6bf829ab3af77a40c ] The intended optimization should be A ^ 0 = A, not A ^ -1 = A. Fixes: cd7df56ed3e6 ("nfp: add BPF to NFP code translator") Reviewed-by:

[PATCH 4.14 059/183] phonet: fix building with clang

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6321aa197547da397753757bd84c6ce64b3e3d89 ] clang warns about overflowing the data[] member in the struct pnpipehdr: net/phonet/pep.c:295:8: warning: array index 4 is past the end

[PATCH 4.14 053/183] net: marvell: mvneta: fix DMA debug warning

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a8fef9ba58c9966ddb1fec916d8d8137c9d8bc89 ] Booting 4.20 on SolidRun Clearfog issues this warning with DMA API debug enabled: WARNING: CPU: 0 PID: 555 at kernel/dma/debug.c:1230

[PATCH 4.14 090/183] regulator: s2mpa01: Fix step values for some LDOs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stuart Menefy commit 28c4f730d2a44f2591cb104091da29a38dac49fe upstream. The step values for some of the LDOs appears to be incorrect, resulting in incorrect voltages (or at least, ones which

[PATCH 4.14 076/183] crypto: testmgr - skip crc32c context test for ahash algorithms

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit eb5e6730db98fcc4b51148b4a819fa4bf864ae54 upstream. Instantiating "cryptd(crc32c)" causes a crypto self-test failure because the crypto_alloc_shash() in alg_test_crc32c()

[PATCH 4.14 080/183] CIFS: Fix read after write for files with read caching

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Shilovsky commit 6dfbd84684700cb58b34e8602c01c12f3d2595c8 upstream. When we have a READ lease for a file and have just issued a write operation to the server we need to purge the cache

Re: [possible PATCH] crypto: sahara - Use #ifdef DEBUG not IS_ENABLED(DEBUG)

Le 08/03/2019 à 01:15, Joe Perches a écrit : Normal use of IS_ENABLED is with a CONFIG_ and there is no -DDEBUG in the Makefile here. Replace the IS_ENABLED(DEBUG) with #ifdef DEBUG/#endif blocks. By doing this you hide a big part of the code which cannot be verified unless DEBUG is

[PATCH 4.14 085/183] mmc: sdhci-esdhc-imx: fix HS400 timing issue

4.14-stable review patch. If anyone has any objections, please let me know. -- From: BOUGH CHEN commit de0a0decf2edfc5b0c782915f4120cf990a9bd13 upstream. Now tuning reset will be done when the timing is MMC_TIMING_LEGACY/ MMC_TIMING_MMC_HS/MMC_TIMING_SD_HS. But for timing

[PATCH 4.14 086/183] spi: ti-qspi: Fix mmap read when more than one CS in use

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vignesh R commit 673c865efbdc5fec3cc525c46d71844d42c60072 upstream. Commit 4dea6c9b0b64 ("spi: spi-ti-qspi: add mmap mode read support") has has got order of parameter wrong when calling

[PATCH 4.14 092/183] clocksource/drivers/exynos_mct: Clear timer interrupt when shutdown

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stuart Menefy commit d2f276c8d3c224d5b493c42b6cf006ae4e64fb1c upstream. When shutting down the timer, ensure that after we have stopped the timer any pending interrupts are cleared. This

[PATCH 4.14 104/183] Btrfs: fix corruption reading shared and compressed extents after hole punching

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 8e928218780e2f1cf2f5891c7575e8f0b284fcce upstream. In the past we had data corruption when reading compressed extents that are shared within the same file and they are

[PATCH 4.14 099/183] fs/devpts: always delete dcache dentry-s in dput()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Varad Gautam commit 73052b0daee0b750b39af18460dfec683e4f5887 upstream. d_delete only unhashes an entry if it is reached with dentry->d_lockref.count != 1. Prior to commit 8ead9dd54716

[PATCH 4.14 106/183] libertas_tf: dont set URB_ZERO_PACKET on IN USB transfer

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lubomir Rintel commit 607076a904c435f2677fadaadd4af546279db68b upstream. It doesn't make sense and the USB core warns on each submit of such URB, easily flooding the message buffer with

[PATCH 4.14 108/183] x86/kprobes: Prohibit probing on optprobe template code

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 0192e6535ebe9af68614198ced4fd6d37b778ebf upstream. Prohibit probing on optprobe template code, since it is not a code but a template instruction sequence. If we modify

[PATCH 4.14 110/183] cpufreq: pxa2xx: remove incorrect __init annotation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 9505b98ccddc454008ca7efff90044e3e857c827 upstream. pxa_cpufreq_init_voltages() is marked __init but usually inlined into the non-__init pxa_cpufreq_init() function. When

[PATCH 4.14 102/183] Btrfs: setup a nofs context for memory allocation at __btrfs_set_acl

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit a0873490660246db587849a9e172f2b7b21fa88a upstream. We are holding a transaction handle when setting an acl, therefore we can not allocate the xattr value buffer using

[PATCH 4.14 094/183] s390/virtio: handle find on invalid queue gracefully

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Halil Pasic commit 3438b2c039b4bf26881786a1f3450f016d66ad11 upstream. A queue with a capacity of zero is clearly not a valid virtio queue. Some emulators report zero queue size if queried

[PATCH 4.14 119/183] clk: ingenic: Fix doc of ingenic_cgu_div_info

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paul Cercueil commit 7ca4c922aad2e3c46767a12f80d01c6b25337b59 upstream. The 'div' field does not represent a number of bits used to divide (understand: right-shift) the divider, but a number

[PATCH 4.14 117/183] clk: clk-twl6040: Fix imprecise external abort for pdmclk

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 5ae51d67aec95f6f9386aa8dd5db424964895575 upstream. I noticed that modprobe clk-twl6040 can fail after a cold boot with: abe_cm:clk:0010:0: failed to enable ... Unhandled

[PATCH 4.14 124/183] kernel/sysctl.c: add missing range check in do_proc_dointvec_minmax_conv

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Zev Weiss commit 8cf7630b29701d364f8df4a50e4f1f5e752b2778 upstream. This bug has apparently existed since the introduction of this function in the pre-git era (4500e91754d3 in Thomas

[PATCH 4.14 128/183] i2c: tegra: fix maximum transfer size

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sowjanya Komatineni commit f4e3f4ae1d9c9330de355f432b69952e8cef650c upstream. Tegra186 and prior supports maximum 4K bytes per packet transfer including 12 bytes of packet header. This patch

[PATCH 4.14 113/183] IB/hfi1: Close race condition on user context disable and close

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael J. Ruhl commit bc5add09764c123f58942a37c8335247e683d234 upstream. When disabling and removing a receive context, it is possible for an asynchronous event (i.e IRQ) to occur. Because

[PATCH 4.14 127/183] parport_pc: fix find_superio io compare code, should use equal test.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: QiaoChong commit 21698fd57984cd28207d841dbdaa026d6061bceb upstream. In the original code before 181bf1e815a2 the loop was continuing until it finds the first matching superios[i].io and

[PATCH 4.14 152/183] dm integrity: limit the rate of error messages

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 225557446856448039a9e495da37b72c20071ef2 upstream. When using dm-integrity underneath md-raid, some tests with raid auto-correction trigger large amounts of integrity

[PATCH 4.14 140/183] powerpc/powernv: Make opal log only readable by root

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Niethe commit 7b62f9bd2246b7d3d086e571397c14ba52645ef1 upstream. Currently the opal log is globally readable. It is kernel policy to limit the visibility of physical addresses / kernel

[PATCH 4.14 134/183] serial: 8250_pci: Have ACCES cards that use the four port Pericom PI7C9X7954 chip use the pci_pericom_setup()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jay Dolan commit 78d3820b9bd39028727c6aab7297b63c093db343 upstream. The four port Pericom chips have the fourth port at the wrong address. Make use of quirk to fix it. Fixes: c8d192428f52

[PATCH 4.14 112/183] ext4: fix crash during online resizing

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit f96c3ac8dfc24b4e38fc4c2eba5fea2107b929d1 upstream. When computing maximum size of filesystem possible with given number of group descriptor blocks, we forget to include

[PATCH 4.14 150/183] arm64: KVM: Fix architecturally invalid reset value for FPEXC32_EL2

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit c88b093693ccbe41991ef2e9b1d251945e6e54ed upstream. Due to what looks like a typo dating back to the original addition of FPEXC32_EL2 handling, KVM currently initialises

[PATCH 4.14 136/183] jbd2: fix compile warning when using JBUFFER_TRACE

4.14-stable review patch. If anyone has any objections, please let me know. -- From: zhangyi (F) commit 01215d3edb0f384ddeaa5e4a22c1ae5ff634149f upstream. The jh pointer may be used uninitialized in the two cases below and the compiler complain about it when enabling

[PATCH 4.14 137/183] security/selinux: fix SECURITY_LSM_NATIVE_LABELS on reused superblock

4.14-stable review patch. If anyone has any objections, please let me know. -- From: J. Bruce Fields commit 3815a245b50124f0865415dcb606a034e97494d4 upstream. In the case when we're reusing a superblock, selinux_sb_clone_mnt_opts() fails to set set_kern_flags, with the result

[PATCH 4.14 135/183] jbd2: clear dirty flag when revoking a buffer from an older transaction

4.14-stable review patch. If anyone has any objections, please let me know. -- From: zhangyi (F) commit 904cdbd41d749a476863a0ca41f6f396774f26e4 upstream. Now, we capture a data corruption problem on ext4 while we're truncating an extent index block. Imaging that if we are

[PATCH 4.14 172/183] media: uvcvideo: Avoid NULL pointer dereference at the end of streaming

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sakari Ailus commit 9dd0627d8d62a7ddb001a75f63942d92b5336561 upstream. The UVC video driver converts the timestamp from hardware specific unit to one known by the kernel at the time when the

[PATCH 4.14 154/183] NFS: Fix I/O request leakages

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit f57dcf4c72113c745d83f1c65f7291299f65c14f upstream. When we fail to add the request to the I/O queue, we currently leave it to the caller to free the failed request.

[PATCH 4.14 171/183] media: imx: prpencvf: Stop upstream before disabling IDMA channel

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steve Longerbeam commit a19c22677377b87e4354f7306f46ad99bc982a9f upstream. Upstream must be stopped immediately after receiving the last EOF and before disabling the IDMA channel. This can be

[PATCH 4.14 164/183] perf auxtrace: Define auxtrace record alignment

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit c3fcadf0bb765faf45d6d562246e1d08885466df upstream. Define auxtrace record alignment so that it can be referenced elsewhere. Note this is preparation for patch "perf

[PATCH 4.14 141/183] powerpc/83xx: Also save/restore SPRG4-7 during suspend

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 36da5ff0bea2dc67298150ead8d8471575c54c7d upstream. The 83xx has 8 SPRG registers and uses at least SPRG4 for DTLB handling LRU. Fixes: 2319f1239592 ("powerpc/mm:

[PATCH 4.14 142/183] powerpc: Fix 32-bit KVM-PR lockup and host crash with MacOS guest

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mark Cave-Ayland commit fe1ef6bcdb4fca33434256a802a3ed6aacf0bd2f upstream. Commit 8792468da5e1 "powerpc: Add the ability to save FPU without giving it up" unexpectedly removed the MSR_FE0 and

[PATCH 4.14 156/183] NFS: Dont recoalesce on error in nfs_pageio_complete_mirror()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 8127d82705998568b52ac724e28e00941538083d upstream. If the I/O completion failed with a fatal error, then we should just exit nfs_pageio_complete_mirror() rather than

[PATCH 4.14 175/183] media: imx: csi: Stop upstream before disabling IDMA channel

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steve Longerbeam commit 4bc1ab41eee9d02ad2483bf8f51a7b72e3504eba upstream. Move upstream stream off to just after receiving the last EOF completion and disabling the CSI (and thus before

[PATCH 4.14 160/183] PM / wakeup: Rework wakeup source timer cancellation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit 1fad17fb1bbcd73159c2b992668a6957ecc5af8a upstream. If wakeup_source_add() is called right after wakeup_source_remove() for the same wakeup source, timer_setup() may be

[PATCH 4.14 162/183] x86/unwind/orc: Fix ORC unwind table alignment

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit f76a16adc485699f95bb71fce114f97c832fe664 upstream. The .orc_unwind section is a packed array of 6-byte structs. It's currently aligned to 6 bytes, which is causing

[PATCH 4.14 177/183] KVM: Call kvm_arch_memslots_updated() before updating memslots

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit 152482580a1b0accb60676063a1ac57b2d12daf6 upstream. kvm_arch_memslots_updated() is at this point in time an x86-specific hook for handling MMIO generation

[PATCH 4.19 012/280] crypto: ccree - fix missing break in switch statement

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit b5be853181a8d4a6e20f2073ccd273d6280cad88 upstream. Add missing break statement in order to prevent the code from falling through to case S_DIN_to_DES. This bug was

[PATCH 4.14 183/183] s390/setup: fix boot crash for machine without EDAT-1

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky commit 86a86804e4f18fc3880541b3d5a07f4df0fe29cb upstream. The fix to make WARN work in the early boot code created a problem on older machines without EDAT-1. The

[PATCH 4.14 167/183] md: Fix failed allocation of md_register_thread

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Aditya Pakki commit e406f12dde1a8375d77ea02d91f313fb1a9c6aec upstream. mddev->sync_thread can be set to NULL on kzalloc failure downstream. The patch checks for such a scenario and frees

[PATCH 4.19 002/280] 9p: use inode->i_lock to protect i_size_write() under 32-bit

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Hou Tao commit 5e3cc1ee1405a7eb3487ed24f786dec01b4cbe1f upstream. Use inode->i_lock to protect i_size_write(), else i_size_read() in generic_fillattr() may loop infinitely in

[PATCH 4.19 000/280] 4.19.31-stable review

This is the start of the stable review cycle for the 4.19.31 release. There are 280 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sun Mar 24 11:11:09 UTC 2019. Anything

[PATCH 4.19 003/280] 9p/net: fix memory leak in p9_client_create

4.19-stable review patch. If anyone has any objections, please let me know. -- From: zhengbin commit bb06c388fa20ae24cfe80c52488de718a7e3a53f upstream. If msize is less than 4096, we should close and put trans, destroy tagpool, not just free client. This patch fixes that.

[PATCH 4.19 010/280] stm class: Fix an endless loop in channel allocation

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Zhi Jin commit a1d75dad3a2c689e70a1c4e0214cca9de741d0aa upstream. There is a bug in the channel allocation logic that leads to an endless loop when looking for a contiguous range of channels

[PATCH 4.19 015/280] crypto: ccree - fix free of unallocated mlli buffer

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Hadar Gat commit a49411959ea6d4915a9fd2a7eb5ba220e6284e9a upstream. In cc_unmap_aead_request(), call dma_pool_free() for mlli buffer only if an item is allocated from the pool and not always

[PATCH 4.19 001/280] media: videobuf2-v4l2: drop WARN_ON in vb2_warn_zero_bytesused()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 5e99456c20f712dcc13d9f6ca4278937d5367355 upstream. Userspace shouldn't set bytesused to 0 for output buffers. vb2_warn_zero_bytesused() warns about this (only once!), but

[PATCH 4.19 021/280] crypto: rockchip - fix scatterlist nents error

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Zhang Zhijie commit 4359669a087633132203c52d67dd8c31e09e7b2e upstream. In some cases, the nents of src scatterlist is different from dst scatterlist. So two variables are used to handle the

[PATCH 4.19 034/280] ARM: dts: Configure clock parent for pwm vibra

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0840242e887586268f665bf58d5e1a7d6ebf35ed ] Commit 84badc5ec5fc ("ARM: dts: omap4: Move l4 child devices to probe them with ti-sysc") moved some omap4 timers to probe with ti-sysc

[PATCH 2/6] svm: Add AMD AVIC handlers for APIC ID, DFR and LDR update

During AVIC temporary deactivation, guest could update APIC ID, DFR and LDR registers, which would not be trapped by avic_unaccelerated_ccess_interception(). In this case, we need to update the AVIC logical APIC ID table accordingly. Signed-off-by: Suravee Suthikulpanit --- arch/x86/kvm/svm.c |

[PATCH 4.19 031/280] s390/dasd: fix using offset into zero size array error

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4a8ef6999bce998fa5813023a9a6b56eea329dba ] Dan Carpenter reported the following: The patch 52898025cf7d: "[S390] dasd: security and PSF update patch for EMC CKD ioctl" from Mar 8,

[PATCH 4.19 033/280] Input: pwm-vibra - stop regulator after disabling pwm, not before

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 94803aef3533676194c772383472636c453e3147 ] This patch fixes order of disable calls in pwm_vibrator_stop. Currently when starting device, we first enable vcc regulator and then setup

[PATCH 4.19 032/280] Input: pwm-vibra - prevent unbalanced regulator

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3ca232df9921f083c3b37ba5fbc76f4d9046268b ] pwm_vibrator_stop disables the regulator, but it can be called from multiple places, even when the regulator is already disabled. Fix this

[PATCH 4/6] kvm: lapic: Add apicv activate/deactivate helper function

Introduce a helper function for setting lapic parameters when activate/deactivate apicv. Signed-off-by: Suravee Suthikulpanit --- arch/x86/kvm/lapic.c | 23 ++- arch/x86/kvm/lapic.h | 1 + 2 files changed, 19 insertions(+), 5 deletions(-) diff --git a/arch/x86/kvm/lapic.c

[PATCH 4.19 036/280] ASoC: dapm: fix out-of-bounds accesses to DAPM lookup tables

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c16e12010060c6c7a31f08b4a99513064cb53b7d ] KASAN reports and additional traces point to out-of-bounds accesses to the dapm_up_seq and dapm_down_seq lookup tables. The indices used

[PATCH 4.19 038/280] KVM: arm/arm64: Reset the VCPU without preemption and vcpu state loaded

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e761a927bc9a7ee6ceb7c4f63d5922dbced87f0d ] We have two ways to reset a vcpu: - either through VCPU_INIT - or through a PSCI_ON call The first one is easy to reason about. The

[PATCH 4.19 037/280] ASoC: rsnd: fixup rsnd_ssi_master_clk_start() user count check

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d9111d36024de07784f2e1ba2ccf70b16035f378 ] commit 4d230d1271064 ("ASoC: rsnd: fixup not to call clk_get/set under non-atomic") added new rsnd_ssi_prepare() and moved

[PATCH 5/6] KVM: x86: Add interface for run-time activate/de-activate APIC virtualization

When activate / deactivate AVIC during runtime, all vcpus has to be operating in the same mode. So, introduce new interface to request all vCPUs to activate/deactivate APICV. Signed-off-by: Suravee Suthikulpanit --- arch/x86/include/asm/kvm_host.h | 8 ++ arch/x86/kvm/x86.c |

[PATCH 4.19 022/280] crypto: rockchip - update new iv to device in multiple operations

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Zhang Zhijie commit c1c214adcb56d36433480c8fedf772498e7e539c upstream. For chain mode in cipher(eg. AES-CBC/DES-CBC), the iv is continuously updated in the operation. The new iv value should

[PATCH 4.19 052/280] ipvs: fix dependency on nf_defrag_ipv6

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 098e13f5b21d3398065fce8780f07a3ef62f4812 ] ipvs relies on nf_defrag_ipv6 module to manage IPv6 fragmentation, but lacks proper Kconfig dependencies and does not explicitly request

[PATCH 4.19 027/280] ASoC: rt5682: Correct the setting while select ASRC clk for AD/DA filter

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8077ec011b1ea26abb7ca786f28ecccfb352717f ] AD/DA ASRC function control two ASRC clock sources separately. Whether AD/DA filter select which clock source, we enable AD/DA ASRC

[PATCH 4.19 051/280] blk-mq: insert rq with DONTPREP to hctx dispatch list when requeue

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aef1897cd36dcf5e296f1d2bae7e0d268561b685 ] When requeue, if RQF_DONTPREP, rq has contained some driver specific data, so insert it to hctx dispatch list to avoid any merge. Take

[PATCH 4.19 041/280] KVM: arm/arm64: vgic: Always initialize the group of private IRQs

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ab2d5eb03dbb7b37a1c6356686fb48626ab0c93e ] We currently initialize the group of private IRQs during kvm_vgic_vcpu_init, and the value of the group depends on the GIC model we are

[PATCH 4.19 029/280] KVM: arm/arm64: vgic: Make vgic_dist->lpi_list_lock a raw_spinlock

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fc3bc475231e12e9c0142f60100cf84d077c79e1 ] vgic_dist->lpi_list_lock must always be taken with interrupts disabled as it is used in interrupt context. For configurations such as

[PATCH 4.19 050/280] netfilter: compat: initialize all fields in xt_init

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8d29d16d21342a0c86405d46de0c4ac5daf1760f ] If a non zero value happens to be in xt[NFPROTO_BRIDGE].cur at init time, the following panic can be caused by running % ebtables -t

[PATCH 4.19 055/280] NFS: Dont use page_file_mapping after removing the page

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d2ceb7e57086750ea6198a31fd942d98099a0786 ] If nfs_page_async_flush() removes the page from the mapping, then we can't use page_file_mapping() on it as nfs_updatepate() is wont to do

[PATCH 4.19 057/280] Revert "mm: use early_pfn_to_nid in page_ext_init"

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2f1ee0913ce58efe7f18fbd518bd54c598559b89 ] This reverts commit fe53ca54270a ("mm: use early_pfn_to_nid in page_ext_init"). When booting a system with "page_owner=on", start_kernel

[PATCH 4.19 058/280] scsi: qla2xxx: Fix panic from use after free in qla2x00_async_tm_cmd

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 388a49959ee4e4e99f160241d9599efa62cd4299 ] In qla2x00_async_tm_cmd, we reference off sp after it has been freed. This caused a panic on a system running a slub debug kernel. Since

[PATCH 4.19 048/280] mac80211: call drv_ibss_join() on restart

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4926b51bfaa6d36bd6f398fb7698679d3962e19d ] If a driver does any significant activity in its ibss_join method, then it will very well expect that to be called during restart, before

[PATCH 4.19 061/280] mm: page_alloc: fix ref bias in page_frag_alloc() for 1-byte allocs

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2c2ade81741c66082f8211f0b96cf509cc4c0218 ] The basic idea behind ->pagecnt_bias is: If we pre-allocate the maximum number of references that we might need to create in the fastpath

[PATCH 4.19 046/280] Input: ps2-gpio - flush TX work when closing port

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 33a841ce5cef4ca6c18ad333248b6d273f54c839 ] To ensure that TX work is not running after serio port has been torn down, let's flush it when closing the port. Reported-by: Sven Van

Re: [PATCH] b/arch/x86/mm/pti.c - make local symbols static

Valdis, On Tue, 12 Mar 2019, Valdis Klētnieks wrote: I've applied the lot, but I had to fixup the subject lines. # git log path/to/file gives you a decent hint on what the usual prefix and format is. 'b/arch/x86/mm/pti.c -' is obviously not. Thanks, tglx

[PATCH 4.19 073/280] bpf: fix lockdep false positive in stackmap

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3defaf2f15b2bfd86c6664181ac009e91985f8ac ] Lockdep warns about false positive: [ 11.211460] [ cut here ] [ 11.211936] DEBUG_LOCKS_WARN_ON(depth <= 0) [

[PATCH 4.19 076/280] assoc_array: Fix shortcut creation

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bb2ba2d75a2d673e76ddaf13a9bd30d6a8b1bb08 ] Fix the creation of shortcuts for which the length of the index key value is an exact multiple of the machine word size. The problem is

[PATCH 4.19 079/280] net: systemport: Fix reception of BPDUs

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a40061ea2e39494104602b3048751341bda374a1 ] SYSTEMPORT has its RXCHK parser block that attempts to validate the packet structures, unfortunately setting the L2 header check bit will

[PATCH 4.19 089/280] ARM: dts: armada-xp: fix Armada XP boards NAND description

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6fc979179c98d2591784937d5618edc3e5cd31c1 ] Commit 3b79919946cd2cf4dac47842afc9a893acec4ed7 ("ARM: dts: armada-370-xp: update NAND node with new bindings") updated some Marvell

[PATCH 4.19 091/280] ARM: tegra: Restore DT ABI on Tegra124 Chromebooks

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 94d9b9337d09bdd27735005b3251d97ab29f7273 ] Commit 482997699ef0 ("ARM: tegra: Fix unit_address_vs_reg DTC warnings for /memory") inadventently broke device tree ABI by adding a unit-

[PATCH 4.19 060/280] x86/CPU: Add Icelake model number

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8cd8f0ce0d6aafe661cb3d6781c8b82bc696c04d ] Add the CPUID model number of Icelake (ICL) mobile processors to the Intel family list. Icelake U/Y series uses model number 0x7E.

[PATCH 4.19 067/280] clk: sunxi-ng: v3s: Fix TCON reset de-assert bit

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5c59801f7018acba11b12de59017a3fcdcf7421d ] According to the datasheet and the reference code from Allwinner, the bit used to de-assert the TCON reset is bit 4, not bit 3. Fix it in

[PATCH 4.19 065/280] auxdisplay: ht16k33: fix potential user-after-free on module unload

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 69ef9bc54715fb1cb7786ada15774e469e822209 ] On module unload/remove, we need to ensure that work does not run after we have freed resources. Concretely, cancel_delayed_work() may

Re: [PATCH v2 3/5] devfreq: rk3399_dmc: Pass ODT and auto power down parameters to TF-A.

Hi Matthias, On Thu, Mar 21, 2019 at 05:01:07PM -0700, Matthias Kaehlcke wrote: > > ... > > > > So, for a reason that I ignore, if we try to save unecessary calls to > > ROCKCHIP_SIP_CONFIG_DRAM_SET_ODT_PD (odt_enable has not changed since > > last call), we get stalled in the call to

[PATCH 4.19 111/280] tmpfs: fix uninitialized return value in shmem_link

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 29b00e609960ae0fcff382f4c7079dd0874a5311 ] When we made the shmem_reserve_inode call in shmem_link conditional, we forgot to update the declaration for ret so that it always has a

[PATCH 4.19 099/280] ARCv2: dont assume core 0x54 has dual issue

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7b2e932f633bcb7b190fc7031ce6dac75f8c3472 ] The first release of core4 (0x54) was dual issue only (HS4x). Newer releases allow hardware to be configured as single issue (HS3x) or

[PATCH 4.19 097/280] ARC: uacces: remove lp_start, lp_end from clobber list

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d5e3c55e01d8b1774b37b4647c30fb22f1d39077 ] Newer ARC gcc handles lp_start, lp_end in a different way and doesn't like them in the clobber list. Signed-off-by: Vineet Gupta

[PATCH 4.19 096/280] ARCv2: lib: memcpy: fix doing prefetchw outside of buffer

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f8a15f97664178f27dfbf86a38f780a532cb6df0 ] ARCv2 optimized memcpy uses PREFETCHW instruction for prefetching the next cache line but doesn't ensure that the line is not past the end

[PATCH 4.19 085/280] mailbox: bcm-flexrm-mailbox: Fix FlexRM ring flush timeout issue

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d7bf31a0f85faaf63c63c39d55154825a1eaaea9 ] RING_CONTROL reg was not written due to wrong address, hence all the subsequent ring flush was timing out. Fixes: a371c10ea4b3 ("mailbox:

[PATCH 4.19 088/280] qed: Fix iWARP syn packet mac address validation.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8be3dadf04050c2907760ec1955ca1c8fbc25585 ] The ll2 forwards all syn packets to the driver without validating the mac address. Add validation check in the driver's iWARP listener

[PATCH 4.19 117/280] libnvdimm/label: Clear updating flag after label-set update

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 966d23a006ca7b44ac8cf4d0c96b19785e0c3da0 upstream. The UEFI 2.7 specification sets expectations that the 'updating' flag is eventually cleared. To date, the libnvdimm core

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