[PATCH 5.0 115/238] intel_th: Dont reference unassigned outputs

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit 9ed3f3c33347ed963e7c7019cf2956dd4e37 upstream. When an output port driver is removed, also remove references to it from any masters. Failing to do this causes a NU

[PATCH 5.0 112/238] kernel/sysctl.c: add missing range check in do_proc_dointvec_minmax_conv

5.0-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 Gleixner's

[PATCH 5.0 088/238] ovl: During copy up, first copy up data and then xattrs

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Vivek Goyal commit 5f32879ea35523b9842bdbdc0065e13635caada2 upstream. If a file with capability set (and hence security.capability xattr) is written kernel clears security.capability xattr. For

[PATCH 5.0 094/238] btrfs: drop the lock on error in btrfs_dev_replace_cancel

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 669e859b5ea7c6f4fce0149d3907c64e550c294b upstream. We should drop the lock on this error path. This has been found by a static tool. The lock needs to be released, it's t

Re: [PATCH V2 04/23] perf/x86/intel: Support adaptive PEBSv4

On Thu, Mar 21, 2019 at 08:40:03PM -0400, Liang, Kan wrote: > > > On 3/21/2019 5:20 PM, Peter Zijlstra wrote: > > On Thu, Mar 21, 2019 at 01:56:44PM -0700, kan.li...@linux.intel.com wrote: > > > @@ -933,6 +1001,34 @@ pebs_update_state(bool needed_cb, struct > > > cpu_hw_events *cpuc, struct pmu

[PATCH 5.0 096/238] btrfs: init csum_list before possible free

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Dan Robertson commit e49be14b8d80e23bb7c53d78c21717a474ade76b upstream. The scrub_ctx csum_list member must be initialized before scrub_free_ctx is called. If the csum_list is not initialized b

[PATCH 5.0 123/238] ext4: fix crash during online resizing

5.0-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 s_first_

[PATCH 5.0 138/238] ext2: Fix underflow in ext2_max_size()

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 1c2d14212b15a60300a2d4f6364753e87394c521 upstream. When ext2 filesystem is created with 64k block size, ext2_max_size() will return value less than 0. Also, we cannot write any

[PATCH] ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol

w_text_param can be NULL and it is being dereferenced without checking. Add the missing sanity check to prevent NULL pointer dereference. Signed-off-by: Pankaj Bharadiya --- sound/soc/soc-dapm.c | 4 1 file changed, 4 insertions(+) diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c

[PATCH 5.0 097/238] Btrfs: fix corruption reading shared and compressed extents after hole punching

5.0-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 cons

[PATCH 5.0 124/238] dma: Introduce dma_max_mapping_size()

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Joerg Roedel commit 133d624b1cee16906134e92d5befb843b58bcf31 upstream. The function returns the maximum size that can be mapped using DMA-API functions. The patch also adds the implementation f

[PATCH 5.0 145/238] usb: chipidea: tegra: Fix missed ci_hdrc_remove_device()

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Osipenko commit 563b9372f7ec57e44e8f9a8600c5107d7ffdd166 upstream. The ChipIdea's platform device need to be unregistered on Tegra's driver module removal. Fixes: dfebb5f43a78827a ("usb

[PATCH 5.0 150/238] serial: 8250_pci: Fix number of ports for ACCES serial cards

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Jay Dolan commit b896b03bc7fce43a07012cc6bf5e2ab2fddf3364 upstream. Have the correct number of ports created for ACCES serial cards. Two port cards show up as four ports, and four port cards sh

[PATCH 5.0 148/238] serial: uartps: Fix stuck ISR if RX disabled with non-empty FIFO

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Anssi Hannula commit 7abab1605139bc41442864c18f9573440f7ca105 upstream. If RX is disabled while there are still unprocessed bytes in RX FIFO, cdns_uart_handle_rx() called from interrupt handler

Re: [PATCH -next] coresight: catu: Make catu_helper_ops and catu_ops static

On 03/21/2019 03:18 PM, Yue Haibing wrote: From: YueHaibing Fix sparse warnings: drivers/hwtracing/coresight/coresight-catu.c:488:35: warning: symbol 'catu_helper_ops' was not declared. Should it be static? drivers/hwtracing/coresight/coresight-catu.c:493:28: warning: symbol 'catu_ops' was

[PATCH 5.0 153/238] jbd2: fix compile warning when using JBUFFER_TRACE

5.0-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 JBUFFER_TR

[PATCH 5.0 174/238] arm64: KVM: Fix architecturally invalid reset value for FPEXC32_EL2

5.0-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 this

[PATCH 5.0 168/238] powerpc/traps: fix recoverability of machine check handling on book3s/32

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 0bbea75c476b77fa7d7811d6be911cc7583e640f upstream. Looks like book3s/32 doesn't set RI on machine check, so checking RI before calling die() will always be fatal allthou

[PATCH 5.0 172/238] arm64: debug: Dont propagate UNKNOWN FAR into si_code for debug signals

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit b9a4b9d084d978f80eb9210727c81804588b42ff upstream. FAR_EL1 is UNKNOWN for all debug exceptions other than those caused by taking a hardware watchpoint. Unfortunately, if a de

[PATCH 5.0 169/238] powerpc/traps: Fix the message printed when stack overflows

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 9bf3d3c4e4fd82c7174f4856df372ab2a71005b9 upstream. Today's message is useless: [ 42.253267] Kernel stack overflow in process (ptrval), r1=c65500b0 This patch fixes

[PATCH 5.0 130/238] PCI: dwc: skip MSI init if MSIs have been explicitly disabled

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach commit 3afc8299f39a27b60e1519a28e18878ce878e7dd upstream. Since 7c5925afbc58 (PCI: dwc: Move MSI IRQs allocation to IRQ domains hierarchical API) the MSI init claims one of the cont

[PATCH 5.0 177/238] ipmi_si: fix use-after-free of resource->name

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Yang Yingliang commit 401e7e88d4ef80188ffa07095ac00456f901b8c4 upstream. When we excute the following commands, we got oops rmmod ipmi_si cat /proc/ioports [ 1623.482380] Unable to handle kern

[PATCH 5.0 180/238] media: cx25840: mark pad sig_types to fix cx231xx init

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Cody P Schafer commit 46c039d06b6ecabb94bd16c3a999b28dc83b79ce upstream. Without this, we get failures like this when the kernel attempts to initialize a cx231xx device: [16046.153653]

[PATCH 5.0 182/238] cpcap-charger: generate events for userspace

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Machek commit fd10606f93a149a9f3d37574e5385b083b4a7b32 upstream. The driver doesn't generate uevents on charger connect/disconnect. This leads to UPower not detecting when AC is on or off

[PATCH 5.0 158/238] powerpc/powernv: Make opal log only readable by root

5.0-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 p

[PATCH 4.9 113/118] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Zhang, Jun commit 1d1f898df6586c5ea9aeaf349f13089c6fa37903 upstream. The rcu_gp_kthread_wake() function is invoked when it might be necessary to wake the RCU grace-period kthread. Because self

[PATCH 5.0 179/238] dm integrity: limit the rate of error messages

5.0-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 fai

[PATCH 5.0 211/238] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Zhang, Jun commit 1d1f898df6586c5ea9aeaf349f13089c6fa37903 upstream. The rcu_gp_kthread_wake() function is invoked when it might be necessary to wake the RCU grace-period kthread. Because self

[PATCH 3.18 132/134] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Zhang, Jun commit 1d1f898df6586c5ea9aeaf349f13089c6fa37903 upstream. The rcu_gp_kthread_wake() function is invoked when it might be necessary to wake the RCU grace-period kthread. Because sel

[PATCH 4.14 170/183] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Zhang, Jun commit 1d1f898df6586c5ea9aeaf349f13089c6fa37903 upstream. The rcu_gp_kthread_wake() function is invoked when it might be necessary to wake the RCU grace-period kthread. Because sel

[PATCH 4.19 262/280] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Zhang, Jun commit 1d1f898df6586c5ea9aeaf349f13089c6fa37903 upstream. The rcu_gp_kthread_wake() function is invoked when it might be necessary to wake the RCU grace-period kthread. Because sel

[PATCH 5.0 156/238] powerpc/32: Clear on-stack exception marker upon exception return

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 9580b71b5a7863c24a9bd18bcd2ad759b86b1eff upstream. Clear the on-stack STACK_FRAME_REGS_MARKER on exception exit in order to avoid confusing stacktrace like the one below

[PATCH 5.0 163/238] powerpc: Fix 32-bit KVM-PR lockup and host crash with MacOS guest

5.0-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 M

[PATCH 4.4 225/230] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Zhang, Jun commit 1d1f898df6586c5ea9aeaf349f13089c6fa37903 upstream. The rcu_gp_kthread_wake() function is invoked when it might be necessary to wake the RCU grace-period kthread. Because self

[PATCH 5.0 183/238] cpuidle: governor: Add new governors to cpuidle_governors again

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 22782b3f9bb8ae21c710e2880db21bc729771e92 upstream. After commit 61cb5758d3c4 ("cpuidle: Add cpuidle.governor= command line parameter") new cpuidle governors are not add

[PATCH 5.0 162/238] powerpc/64s/hash: Fix assert_slb_presence() use of the slbfee. instruction

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit 7104dccfd052fde51eecc9972dad9c40bd3e0d11 upstream. The slbfee. instruction must have bit 24 of RB clear, failure to do so can result in false negatives that result in inc

[PATCH 5.0 190/238] NFSv4.1: Reinitialise sequence results before retransmitting a request

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit c1dffe0bf7f9c3d57d9f237a7cb2a81e62babd2b upstream. If we have to retransmit a request, we should ensure that we reinitialise the sequence results structure, since in the

[PATCH 5.0 186/238] NFS: Dont recoalesce on error in nfs_pageio_complete_mirror()

5.0-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 try

[PATCH 5.0 218/238] media: imx: csi: Disable CSI immediately after last EOF

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Steve Longerbeam commit 2e0fe66e0a136252f4d89dbbccdcb26deb867eb8 upstream. Disable the CSI immediately after receiving the last EOF before stream off (and thus before disabling the IDMA channel

[PATCH 5.0 204/238] perf/x86/intel/uncore: Fix client IMC events return huge result

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Kan Liang commit 8041ffd36f42d8521d66dd1e236feb58cecd68bc upstream. The client IMC bandwidth events currently return very large values: $ perf stat -e uncore_imc/data_reads/ -e uncore_imc/da

[PATCH 5.0 209/238] tpm/tpm_crb: Avoid unaligned reads in crb_recv()

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Sakkinen commit 3d7a850fdc1a2e4d2adbc95cc0fc962974725e88 upstream. The current approach to read first 6 bytes from the response and then tail of the response, can cause the 2nd memcpy_fr

[PATCH 5.0 203/238] perf intel-pt: Fix overlap calculation for padding

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 5a99d99e3310a565b0cf63f785b347be9ee0da45 upstream. Auxtrace records might have up to 7 bytes of padding appended. Adjust the overlap accordingly. Signed-off-by: Adrian Hun

[PATCH 5.0 214/238] media: sun6i: Fix CSI regmaps max_register

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit d31b282e2c0de9c7fb113516820340251f03a625 upstream. max_register is currently set to 0x1000. This is beyond the mapped address range of the hardware, so attempts to dump the

[PATCH 5.0 220/238] drm/fb-helper: generic: Fix drm_fbdev_client_restore()

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Noralf Trønnes commit 78de14c23e031420aa5f61973583635eccd6cd2a upstream. If fbdev setup has failed, lastclose will give a NULL pointer deref: [ 77.794295] [drm:drm_lastclose] [ 77.794414]

[PATCH 5.0 226/238] KVM: VMX: Zero out *all* general purpose registers after VM-Exit

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit 0e0ab73c9a0243736bcd779b30b717e23ba9a56d upstream. ...except RSP, which is restored by hardware as part of VM-Exit. Paolo theorized that restoring registers from the

[PATCH 5.0 224/238] KVM: Call kvm_arch_memslots_updated() before updating memslots

5.0-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 wraparound.

[PATCH 5.0 234/238] net: dsa: lantiq_gswip: fix OF child-node lookups

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit c8cbcb0d8bd72d44fad1a5ddc348ac10e0fb1b37 upstream. Use the new of_get_compatible_child() helper to look up child nodes to avoid ever matching non-child nodes elsewhere in th

[PATCH 5.0 197/238] stable-kernel-rules.rst: add link to networking patch queue

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit a41e8f25fa8f8f67360d88eb0eebbabe95a64bdf upstream. The networking maintainer keeps a public list of the patches being queued up for the next round of stable releases.

[PATCH 5.0 195/238] bcache: treat stale && dirty keys as bad keys

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Tang Junhui commit 58ac323084ebf44f8470eeb8b82660f9d0ee3689 upstream. Stale && dirty keys can be produced in the follow way: After writeback in write_dirty_finish(), dirty keys k1 will replace

[PATCH 5.0 200/238] perf intel-pt: Fix CYC timestamp calculation after OVF

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 03997612904866abe7cdcc992784ef65cb3a4b81 upstream. CYC packet timestamp calculation depends upon CBR which was being cleared upon overflow (OVF). That can cause errors due

[PATCH 5.0 232/238] KVM: nVMX: Check a single byte for VMCS "launched" in nested early checks

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit 1ce072cbfd8dba46f117804850398e0b3040a541 upstream. Nested early checks does a manual comparison of a VMCS' launched status in its asm blob to execute the correct VM-E

[PATCH 5.0 229/238] KVM: nVMX: Sign extend displacements of VMX instrs mem operands

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit 946c522b603f281195af1df91837a1d4d1eb3bc9 upstream. The VMCS.EXIT_QUALIFCATION field reports the displacements of memory operands for various instructions, including V

[PATCH 5.0 231/238] KVM: nVMX: Ignore limit checks on VMX instructions using flat segments

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit 34333cc6c2cb021662fd32e24e618d1b86de95bf upstream. Regarding segments with a limit==0x, the SDM officially states: When the effective limit is H

[PATCH 5.0 235/238] s390/setup: fix boot crash for machine without EDAT-1

5.0-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 setup_lowco

[PATCH 5.0 227/238] KVM: x86/mmu: Detect MMIO generation wrap in any address space

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit e1359e2beb8b0a1188abc997273acbaedc8ee791 upstream. The check to detect a wrap of the MMIO generation explicitly looks for a generation number of zero. Now that uniqu

[PATCH 5.0 236/238] SUNRPC: Prevent thundering herd when the socket is not connected

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit ed7dc973bd91da234d93aff6d033a5206a6c9885 upstream. If the socket is not connected, then we want to initiate a reconnect rather that trying to transmit requests. If there

[PATCH 5.0 230/238] KVM: nVMX: Apply addr size mask to effective address for VMX instructions

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit 8570f9e881e3fde98801bb3a47eef84dd934d405 upstream. The address size of an instruction affects the effective address, not the virtual/linear address. The final addres

[PATCH 5.0 233/238] net: dsa: lantiq_gswip: fix use-after-free on failed probe

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit aed13f2e00ce278f039b76e7ac84d419aff48ef6 upstream. Make sure to disable and deregister the switch on late probe errors to avoid use-after-free when the device-resource-manag

[PATCH 5.0 238/238] SUNRPC: Respect RPC call timeouts when retrying transmission

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 7b3fef8e4157ed424bcde039a60a730aa0dfb0eb upstream. Fix a regression where soft and softconn requests are not timing out as expected. Fixes: 89f90fe1ad8b ("SUNRPC: Allow

[PATCH 5.0 198/238] vt: perform safe console erase in the right order

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Pitre commit a6dbe44275560ca54a9b8ecfd9606be0ea75 upstream. Commit 4b4ecd9cb853 ("vt: Perform safe console erase only once") removed what appeared to be an extra call to scr_memsetw

[PATCH 5.0 237/238] SUNRPC: Fix up RPC back channel transmission

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 477687e1116ad16180caf8633dd830b296a5ce73 upstream. Now that transmissions happen through a queue, we require the RPC tasks to handle error conditions that may have been s

[PATCH 5.0 191/238] svcrpc: fix UDP on servers with lots of threads

5.0-stable review patch. If anyone has any objections, please let me know. -- From: J. Bruce Fields commit b7e5034cbecf5a65b7bfdc2b20a8378039577706 upstream. James Pearson found that an NFS server stopped responding to UDP requests if started with more than 1017 threads. sv_m

[PATCH 5.0 196/238] bcache: use (REQ_META|REQ_PRIO) to indicate bio for metadata

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Coly Li commit dc7292a5bcb4c878b076fca2ac3fc22f81b8f8df upstream. In 'commit 752f66a75aba ("bcache: use REQ_PRIO to indicate bio for metadata")' REQ_META is replaced by REQ_PRIO to indicate met

[PATCH 5.0 199/238] x86/unwind/orc: Fix ORC unwind table alignment

5.0-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 warnin

[PATCH 5.0 228/238] KVM: x86/mmu: Do not cache MMIO accesses while memslots are in flux

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit ddfd1730fd829743e41213e32ccc8b4aa6dc8325 upstream. When installing new memslots, KVM sets bit 0 of the generation number to indicate that an update is in-progress. U

[PATCH 5.0 222/238] drm/amd/powerplay: correct power reading on fiji

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Evan Quan commit f5742ec36422a39b57f0256e4847f61b3c432f8c upstream. Set sampling period as 500ms to provide a smooth power reading output. Also, correct the register for power reading. Signed-

[PATCH 5.0 223/238] drm/amd/display: dont call dm_pp_ function from an fpu block

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Harry Wentland commit 59d3191f14dc18881fec1172c7096b7863622803 upstream. Powerplay functions called from dm_pp_* functions tend to do a mutex_lock which isn't safe to do inside a kernel_fpu_beg

[PATCH 5.0 225/238] KVM: VMX: Compare only a single byte for VMCS "launched" in vCPU-run

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit 61c08aa9606d4e48a8a50639c956448a720174c3 upstream. The vCPU-run asm blob does a manual comparison of a VMCS' launched status to execute the correct VM-Enter instructi

[PATCH 5.0 212/238] media: imx: prpencvf: Stop upstream before disabling IDMA channel

5.0-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 a

[PATCH 5.0 213/238] media: lgdt330x: fix lock status reporting

5.0-stable review patch. If anyone has any objections, please let me know. -- From: French, Nicholas A commit 1b4fd9de6ec7f3722c2b3e08cc5ad171c11f93be upstream. A typo in code cleanup commit db9c1007bc07 ("media: lgdt330x: do some cleanups at status logic") broke the FE_HAS_LO

[PATCH 5.0 215/238] media: uvcvideo: Avoid NULL pointer dereference at the end of streaming

5.0-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 bu

[PATCH 5.0 221/238] drm/radeon/evergreen_cs: fix missing break in switch statement

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

[PATCH 5.0 193/238] PM / OPP: Update performance state when freq == old_freq

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit faef080f6db5320011862f7baf1aa66d0851559f upstream. At boot up, CPUFreq core performs a sanity check to see if the system is running at a frequency defined in the frequency t

[PATCH 5.0 216/238] media: vimc: Add vimc-streamer for stream control

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Lucas A. M. Magalhães commit adc589d2a20808fb99d46a78175cd023f2040338 upstream. Add a linear pipeline logic for the stream control. It's created by walking backwards on the entity graph. When t

[PATCH 5.0 210/238] tpm: Unify the send callback behaviour

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Sakkinen commit f5595f5baa30e009bf54d0d7653a9a0cc465be60 upstream. The send() callback should never return length as it does not in every driver except tpm_crb in the success case. The r

[PATCH 5.0 217/238] media: imx-csi: Input connections to CSI should be optional

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Steve Longerbeam commit 337e90ed028643c7acdfd0d31e3224d05ca03d66 upstream. Some imx platforms do not have fwnode connections to all CSI input ports, and should not be treated as an error. This

[PATCH 5.0 194/238] bcache: never writeback a discard operation

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Axtens commit 9951379b0ca88c95876ad9778b9099e19a95d566 upstream. Some users see panics like the following when performing fstrim on a bcached volume: [ 529.803060] BUG: unable to handl

[PATCH 5.0 219/238] media: imx: csi: Stop upstream before disabling IDMA channel

5.0-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 disabl

[PATCH 5.0 165/238] powerpc/hugetlb: Dont do runtime allocation of 16G pages in LPAR configuration

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Aneesh Kumar K.V commit 35f2806b481f5b9207f25e1886cba5d1c4d12cc7 upstream. We added runtime allocation of 16G pages in commit 4ae279c2c96a ("powerpc/mm/hugetlb: Allow runtime allocation of 16G.

[PATCH 5.0 208/238] x86/ftrace: Fix warning and considate ftrace_jmp_replace() and ftrace_call_replace()

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit 745cfeaac09ce359130a5451d90cb0bd4094c290 upstream. Arnd reported the following compiler warning: arch/x86/kernel/ftrace.c:669:23: error: 'ftrace_jmp_replace' def

[PATCH 5.0 207/238] x86/kvmclock: set offset for kvm unstable clock

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Tatashin commit b5179ec4187251a751832193693d6e474d3445ac upstream. VMs may show incorrect uptime and dmesg printk offsets on hypervisors with unstable clock. The problem is produced when

[PATCH 5.0 206/238] md: Fix failed allocation of md_register_thread

5.0-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 alloca

[PATCH 5.0 202/238] perf auxtrace: Define auxtrace record alignment

5.0-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 intel-

[PATCH 5.0 205/238] perf intel-pt: Fix divide by zero when TSC is not available

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 076333870c2f5bdd9b6d31e7ca1909cf0c84cbfa upstream. When TSC is not available, "timeless" decoding is used but a divide by zero occurs if perf_time_to_tsc() is called. Ensu

[PATCH 5.0 192/238] PM / wakeup: Rework wakeup source timer cancellation

5.0-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 calle

[PATCH 5.0 164/238] powerpc/ptrace: Simplify vr_get/set() to avoid GCC warning

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit ca6d5149d2ad0a8d2f9c28cbe379802260a0a5e0 upstream. GCC 8 warns about the logic in vr_get/set(), which with -Werror breaks the build: In function ‘user_regset_copyin’,

[PATCH 5.0 201/238] perf tools: Fix split_kallsyms_for_kcore() for trampoline symbols

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit d6d457451eb94fa747dc202765592eb8885a7352 upstream. Kallsyms symbols do not have a size, so the size becomes the distance to the next symbol. Consequently the recently adde

[PATCH 5.0 159/238] powerpc/83xx: Also save/restore SPRG4-7 during suspend

5.0-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: e300c2

[PATCH 5.0 161/238] powerpc/powernv: Dont reprogram SLW image on every KVM guest entry/exit

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 19f8a5b5be2898573a5e1dc1db93e8d40117606a upstream. Commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via stop-api only on Hotplug", 2017-07-21) added two calls to

[PATCH 5.0 189/238] nfsd: fix wrong check in write_v4_end_grace()

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Yihao Wu commit dd838821f0a29781b185cd8fb8e48d5c177bd838 upstream. Commit 62a063b8e7d1 "nfsd4: fix crash on writing v4_end_grace before nfsd startup" is trying to fix a NULL dereference issue,

[PATCH 5.0 187/238] nfsd: fix performance-limiting session calculation

5.0-stable review patch. If anyone has any objections, please let me know. -- From: J. Bruce Fields commit c54f24e338ed2a35218f117a4a1afb5f9e2b4e64 upstream. We're unintentionally limiting the number of slots per nfsv4.1 session to 10. Often more than 10 simultaneous RPCs are

[PATCH 5.0 188/238] nfsd: fix memory corruption caused by readdir

5.0-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit b602345da6cbb135ba68cf042df8ec9a73da7981 upstream. If the result of an NFSv3 readdir{,plus} request results in the "offset" on one entry having to be split across 2 pages, and

[PATCH 5.0 160/238] powerpc/kvm: Save and restore host AMR/IAMR/UAMOR

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit c3c7470c75566a077c8dc71dcf8f1948b8ddfab4 upstream. When the hash MMU is active the AMR, IAMR and UAMOR are used for pkeys. The AMR is directly writable by user space, an

[PATCH 5.0 184/238] NFS: Fix I/O request leakages

5.0-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. Howev

[PATCH 5.0 185/238] NFS: Fix an I/O request leakage in nfs_do_recoalesce

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 4d91969ed4dbcefd0e78f77494f0cb8fada9048a upstream. Whether we need to exit early, or just reprocess the list, we must not lost track of the request which failed to get re

[PATCH 5.0 181/238] mfd: sm501: Fix potential NULL pointer dereference

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit ae7b8eda27b33b1f688dfdebe4d46f690a8f9162 upstream. There is a potential NULL pointer dereference in case devm_kzalloc() fails and returns NULL. Fix this by adding a

[PATCH 5.0 178/238] dm: fix to_sector() for 32bit

5.0-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 0bdb50c531f7377a9da80d3ce2d61f389c84cb30 upstream. A dm-raid array with devices larger than 4GB won't assemble on a 32 bit host since _check_data_dev_sectors() was added in 4.1

[PATCH 5.0 170/238] ARM: s3c24xx: Fix boolean expressions in osiris_dvs_notify

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit e2477233145f2156434afb799583bccd878f3e9f upstream. Fix boolean expressions by using logical AND operator '&&' instead of bitwise operator '&'. This issue was detecte

[PATCH 5.0 175/238] Revert "KVM/MMU: Flush tlb directly in the kvm_zap_gfn_range()"

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Ben Gardon commit 92da008fa21034c369cdb8ca2b629fe5c196826b upstream. This reverts commit 71883a62fcd6c70639fa12cda733378b4d997409. The above commit contains an optimization to kvm_zap_gfn_rang

[PATCH 5.0 131/238] PCI: pciehp: Disable Data Link Layer State Changed event on suspend

5.0-stable review patch. If anyone has any objections, please let me know. -- From: Mika Westerberg commit bbe54ea5330d828cc396d451c0e1e5c3f9764c1e upstream. Commit 0e157e528604 ("PCI/PME: Implement runtime PM callbacks") tried to solve an issue where the hierarchy immediately

<    5   6   7   8   9   10   11   12   13   14   >