[PATCH 5.3 140/148] riscv: Avoid interrupts being erroneously enabled in handle_exception()

2019-10-10 Thread Greg Kroah-Hartman
From: Vincent Chen [ Upstream commit c82dd6d078a2bb29d41eda032bb96d05699a524d ] When the handle_exception function addresses an exception, the interrupts will be unconditionally enabled after finishing the context save. However, It may erroneously enable the interrupts if the interrupts are disa

[PATCH 5.3 142/148] coresight: etm4x: Use explicit barriers on enable/disable

2019-10-10 Thread Greg Kroah-Hartman
From: Andrew Murray commit 1004ce4c255fc3eb3ad9145ddd53547d1b7ce327 upstream. Synchronization is recommended before disabling the trace registers to prevent any start or stop points being speculative at the point of disabling the unit (section 7.3.77 of ARM IHI 0064D). Synchronization is also r

[PATCH 5.3 131/148] i2c: qcom-geni: Disable DMA processing on the Lenovo Yoga C630

2019-10-10 Thread Greg Kroah-Hartman
From: Lee Jones [ Upstream commit 127068abe85bf3dee50df51cb039a5a987a4a666 ] We have a production-level laptop (Lenovo Yoga C630) which is exhibiting a rather horrific bug. When I2C HID devices are being scanned for at boot-time the QCom Geni based I2C (Serial Engine) attempts to use DMA. When

[PATCH 5.3 146/148] staging: erofs: avoid endless loop of invalid lookback distance 0

2019-10-10 Thread Greg Kroah-Hartman
From: Gao Xiang commit 598bb8913d015150b7734b55443c0e53e7189fc7 upstream. As reported by erofs-utils fuzzer, Lookback distance should be a positive number, so it should be actually looked back rather than spinning. Fixes: 02827e1796b3 ("staging: erofs: add erofs_map_blocks_iter") Cc: # 4.19+ S

[PATCH 5.3 132/148] perf unwind: Fix libunwind build failure on i386 systems

2019-10-10 Thread Greg Kroah-Hartman
From: Arnaldo Carvalho de Melo [ Upstream commit 26acf400d2dcc72c7e713e1f55db47ad92010cc2 ] Naresh Kamboju reported, that on the i386 build pr_err() doesn't get defined properly due to header ordering: perf-in.o: In function `libunwind__x86_reg_id': tools/perf/util/libunwind/../../arch/x86/

[PATCH 5.3 145/148] staging: erofs: add two missing erofs_workgroup_put for corrupted images

2019-10-10 Thread Greg Kroah-Hartman
From: Gao Xiang commit 138e1a0990e80db486ab9f6c06bd5c01f9a97999 upstream. As reported by erofs-utils fuzzer, these error handling path will be entered to handle corrupted images. Lack of erofs_workgroup_puts will cause unmounting unsuccessfully. Fix these return values to EFSCORRUPTED as well.

[PATCH 5.3 141/148] vfs: Fix EOVERFLOW testing in put_compat_statfs64

2019-10-10 Thread Greg Kroah-Hartman
From: Eric Sandeen commit cc3a7bfe62b947b423fcb2cfe89fcba92bf48fa3 upstream. Today, put_compat_statfs64() disallows nearly any field value over 2^32 if f_bsize is only 32 bits, but that makes no sense. compat_statfs64 is there for the explicit purpose of providing 64-bit fields for f_files, f_ff

[PATCH 4.19 011/114] PM / devfreq: tegra: Fix kHz to Hz conversion

2019-10-10 Thread Greg Kroah-Hartman
From: Dmitry Osipenko commit 62bacb06b9f08965c4ef10e17875450490c948c0 upstream. The kHz to Hz is incorrectly converted in a few places in the code, this results in a wrong frequency being calculated because devfreq core uses OPP frequencies that are given in Hz to clamp the rate, while tegra-dev

[PATCH 4.19 012/114] ASoC: Define a set of DAPM pre/post-up events

2019-10-10 Thread Greg Kroah-Hartman
From: Oleksandr Suvorov commit cfc8f568aada98f9608a0a62511ca18d647613e2 upstream. Prepare to use SND_SOC_DAPM_PRE_POST_PMU definition to reduce coming code size and make it more readable. Cc: sta...@vger.kernel.org Signed-off-by: Oleksandr Suvorov Reviewed-by: Marcel Ziswiler Reviewed-by: Igo

[PATCH 5.3 135/148] drm/radeon: Bail earlier when radeon.cik_/si_support=0 is passed

2019-10-10 Thread Greg Kroah-Hartman
From: Hans de Goede [ Upstream commit 9dbc88d013b79c62bd845cb9e7c0256e660967c5 ] Bail from the pci_driver probe function instead of from the drm_driver load function. This avoid /dev/dri/card0 temporarily getting registered and then unregistered again, sending unwanted add / remove udev events

[PATCH 4.19 014/114] powerpc/mce: Fix MCE handling for huge pages

2019-10-10 Thread Greg Kroah-Hartman
From: Balbir Singh commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee upstream. The current code would fail on huge pages addresses, since the shift would be incorrect. Use the correct page shift value returned by __find_linux_pte() to get the correct physical address. The code is more generic and

[PATCH 5.3 133/148] mlxsw: spectrum_flower: Fail in case user specifies multiple mirror actions

2019-10-10 Thread Greg Kroah-Hartman
From: Danielle Ratson [ Upstream commit 52feb8b588f6d23673dd7cc2b44b203493b627f6 ] The ASIC can only mirror a packet to one port, but when user is trying to set more than one mirror action, it doesn't fail. Add a check if more than one mirror action was specified per rule and if so, fail for no

[PATCH 4.19 013/114] ASoC: sgtl5000: Improve VAG power and mute control

2019-10-10 Thread Greg Kroah-Hartman
From: Oleksandr Suvorov commit b1f373a11d25fc9a5f7679c9b85799fe09b0dc4a upstream. VAG power control is improved to fit the manual [1]. This patch fixes as minimum one bug: if customer muxes Headphone to Line-In right after boot, the VAG power remains off that leads to poor sound quality from lin

[PATCH 5.3 134/148] nfp: abm: fix memory leak in nfp_abm_u32_knode_replace

2019-10-10 Thread Greg Kroah-Hartman
From: Navid Emamdoost [ Upstream commit 78beef629fd95be4ed853b2d37b832f766bd96ca ] In nfp_abm_u32_knode_replace if the allocation for match fails it should go to the error handling instead of returning. Updated other gotos to have correct errno returned, too. Signed-off-by: Navid Emamdoost Sig

Re: [PATCH] ARM: configs: at91: unselect PIT

2019-10-10 Thread Nicolas.Ferre
On 09/10/2019 at 21:48, Alexandre Belloni wrote: > The PIT is not required anymore to successfully boot and may actually harm > in case preempt-rt is used because the PIT interrupt is shared. > Disable it so the TCB clocksource is used. > > Signed-off-by: Alexandre Belloni Acked-by: Nicolas Fer

[PATCH 4.19 001/114] s390/process: avoid potential reading of freed stack

2019-10-10 Thread Greg Kroah-Hartman
From: Vasily Gorbik commit 8769f610fe6d473e5e8e221709c3ac402037da6c upstream. With THREAD_INFO_IN_TASK (which is selected on s390) task's stack usage is refcounted and should always be protected by get/put when touching other task's stack to avoid race conditions with task's destruction code. F

[PATCH 4.19 018/114] powerpc/book3s64/mm: Dont do tlbie fixup for some hardware revisions

2019-10-10 Thread Greg Kroah-Hartman
From: Aneesh Kumar K.V commit 677733e296b5c7a37c47da391fc70a43dc40bd67 upstream. The store ordering vs tlbie issue mentioned in commit a5d4b5891c2f ("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9") is fixed for Nimbus 2.3 and Cumulus 1.3 revisions. We don't need to apply the fixup if

[PATCH 4.19 025/114] crypto: ccree - account for TEE not ready to report

2019-10-10 Thread Greg Kroah-Hartman
From: Gilad Ben-Yossef commit 76a95bd8f9e10cade9c4c8df93b5c20ff45dc0f5 upstream. When ccree driver runs it checks the state of the Trusted Execution Environment CryptoCell driver before proceeding. We did not account for cases where the TEE side is not ready or not available at all. Fix it by on

[PATCH 4.19 023/114] crypto: cavium/zip - Add missing single_release()

2019-10-10 Thread Greg Kroah-Hartman
From: Wei Yongjun commit c552ffb5c93d9d65aaf34f5f001c4e7e8484ced1 upstream. When using single_open() for opening, single_release() should be used instead of seq_release(), otherwise there is a memory leak. Fixes: 09ae5d37e093 ("crypto: zip - Add Compression/Decompression statistics") Cc: Signe

[PATCH 4.19 024/114] crypto: caam - fix concurrency issue in givencrypt descriptor

2019-10-10 Thread Greg Kroah-Hartman
From: Horia Geantă commit 48f89d2a2920166c35b1c0b69917dbb0390ebec7 upstream. IV transfer from ofifo to class2 (set up at [29][30]) is not guaranteed to be scheduled before the data transfer from ofifo to external memory (set up at [38]: [29] 10FA0004 ld: ind-nfifo (len=4) imm [30] 81F

[PATCH 4.19 016/114] powerpc/powernv: Restrict OPAL symbol map to only be readable by root

2019-10-10 Thread Greg Kroah-Hartman
From: Andrew Donnellan commit e7de4f7b64c23e503a8c42af98d56f2a7462bd6d upstream. Currently the OPAL symbol map is globally readable, which seems bad as it contains physical addresses. Restrict it to root. Fixes: c8742f85125d ("powerpc/powernv: Expose OPAL firmware symbol map") Cc: sta...@vger.

[PATCH 4.19 019/114] can: mcp251x: mcp251x_hw_reset(): allow more time after a reset

2019-10-10 Thread Greg Kroah-Hartman
From: Marc Kleine-Budde commit d84ea2123f8d27144e3f4d58cd88c9c6ddc799de upstream. Some boards take longer than 5ms to power up after a reset, so allow some retries attempts before giving up. Fixes: ff06d611a31c ("can: mcp251x: Improve mcp251x_hw_reset()") Cc: linux-stable Tested-by: Sean Nyekj

[PATCH 4.19 021/114] crypto: qat - Silence smp_processor_id() warning

2019-10-10 Thread Greg Kroah-Hartman
From: Alexander Sverdlin commit 1b82feb6c5e1996513d0fb0bbb475417088b4954 upstream. It seems that smp_processor_id() is only used for a best-effort load-balancing, refer to qat_crypto_get_instance_node(). It's not feasible to disable preemption for the duration of the crypto requests. Therefore,

[PATCH 4.19 026/114] crypto: ccree - use the full crypt length value

2019-10-10 Thread Greg Kroah-Hartman
From: Gilad Ben-Yossef commit 7a4be6c113c1f721818d1e3722a9015fe393295c upstream. In case of AEAD decryption verifcation error we were using the wrong value to zero out the plaintext buffer leaving the end of the buffer with the false plaintext. Signed-off-by: Gilad Ben-Yossef Fixes: ff27e85a85

Re: [PATCH] usb: mtk-xhci: Set the XHCI_NO_64BIT_SUPPORT quirk

2019-10-10 Thread Chunfeng Yun
Hi, Tomasz, On Thu, 2019-10-10 at 16:50 +0900, Tomasz Figa wrote: > MediaTek XHCI host controller does not support 64-bit addressing despite > the AC64 bit of HCCPARAMS1 register being set. The platform-specific > glue sets the DMA mask to 32 bits on its own, but it has no effect, > because xhci_g

[PATCH 4.19 034/114] PCI: Restore Resizable BAR size bits correctly for 1MB BARs

2019-10-10 Thread Greg Kroah-Hartman
From: Sumit Saxena commit d2182b2d4b71ff0549a07f414d921525fade707b upstream. In a Resizable BAR Control Register, bits 13:8 control the size of the BAR. The encoded values of these bits are as follows (see PCIe r5.0, sec 7.8.6.3): ValueBAR size 0 1 MB (2^20 bytes) 1 2 MB

[PATCH 4.19 031/114] usercopy: Avoid HIGHMEM pfn warning

2019-10-10 Thread Greg Kroah-Hartman
From: Kees Cook commit 314eed30ede02fa925990f535652254b5bad6b65 upstream. When running on a system with >512MB RAM with a 32-bit kernel built with: CONFIG_DEBUG_VIRTUAL=y CONFIG_HIGHMEM=y CONFIG_HARDENED_USERCOPY=y all execve()s will fail due to argv copying into kmap()

[PATCH 4.19 027/114] MIPS: Treat Loongson Extensions as ASEs

2019-10-10 Thread Greg Kroah-Hartman
From: Jiaxun Yang commit d2f965549006acb865c4638f1f030ebcefdc71f6 upstream. Recently, binutils had split Loongson-3 Extensions into four ASEs: MMI, CAM, EXT, EXT2. This patch do the samething in kernel and expose them in cpuinfo so applications can probe supported ASEs at runtime. Signed-off-by

[PATCH 4.19 033/114] PCI: vmd: Fix shadow offsets to reflect spec changes

2019-10-10 Thread Greg Kroah-Hartman
From: Jon Derrick commit a1a30170138c9c5157bd514ccd4d76b47060f29b upstream. The shadow offset scratchpad was moved to 0x2000-0x2010. Update the location to get the correct shadow offset. Fixes: 6788958e4f3c ("PCI: vmd: Assign membar addresses from shadow registers") Signed-off-by: Jon Derrick

[PATCH 4.19 028/114] power: supply: sbs-battery: use correct flags field

2019-10-10 Thread Greg Kroah-Hartman
From: Michael Nosthoff commit 99956a9e08251a1234434b492875b1eaff502a12 upstream. the type flag is stored in the chip->flags field not in the client->flags field. This currently leads to never using the ti specific health function as client->flags doesn't use that bit. So it's always falling back

[PATCH 4.19 030/114] tracing: Make sure variable reference alias has correct var_ref_idx

2019-10-10 Thread Greg Kroah-Hartman
From: Tom Zanussi commit 17f8607a1658a8e70415eef67909f990d13017b5 upstream. Original changelog from Steve Rostedt (except last sentence which explains the problem, and the Fixes: tag): I performed a three way histogram with the following commands: echo 'irq_lat u64 lat pid_t pid' > synthetic_e

[PATCH 4.19 035/114] watchdog: imx2_wdt: fix min() calculation in imx2_wdt_set_timeout

2019-10-10 Thread Greg Kroah-Hartman
From: Rasmus Villemoes commit 144783a80cd2cbc45c6ce17db649140b65f203dd upstream. Converting from ms to s requires dividing by 1000, not multiplying. So this is currently taking the smaller of new_timeout and 1.28e8, i.e. effectively new_timeout. The driver knows what it set max_hw_heartbeat_ms

[PATCH 4.19 055/114] ceph: fix directories inode i_blkbits initialization

2019-10-10 Thread Greg Kroah-Hartman
From: Luis Henriques [ Upstream commit 750670341a24cb714e624e0fd7da30900ad93752 ] When filling an inode with info from the MDS, i_blkbits is being initialized using fl_stripe_unit, which contains the stripe unit in bytes. Unfortunately, this doesn't make sense for directories as they have fl_st

[PATCH 4.19 052/114] 9p: Transport error uninitialized

2019-10-10 Thread Greg Kroah-Hartman
From: Lu Shuaibing [ Upstream commit 0ce772fe79b68f83df40f07f28207b292785c677 ] The p9_tag_alloc() does not initialize the transport error t_err field. The struct p9_req_t *req is allocated and stored in a struct p9_client variable. The field t_err is never initialized before p9_conn_cancel() ch

[PATCH 4.19 037/114] drm/omap: fix max fclk divider for omap36xx

2019-10-10 Thread Greg Kroah-Hartman
From: Tomi Valkeinen commit e2c4ed148cf3ec8669a1d90dc66966028e5fad70 upstream. The OMAP36xx and AM/DM37x TRMs say that the maximum divider for DSS fclk (in CM_CLKSEL_DSS) is 32. Experimentation shows that this is not correct, and using divider of 32 breaks DSS with a flood or underflows and sync

[PATCH 4.19 006/114] KVM: PPC: Book3S HV: Check for MMU ready on piggybacked virtual cores

2019-10-10 Thread Greg Kroah-Hartman
From: Paul Mackerras commit d28eafc5a64045c78136162af9d4ba42f8230080 upstream. When we are running multiple vcores on the same physical core, they could be from different VMs and so it is possible that one of the VMs could have its arch.mmu_ready flag cleared (for example by a concurrent HPT res

Re: [RFC PATCH 00/13] vsock: add multi-transports support

2019-10-10 Thread Stefano Garzarella
On Wed, Oct 09, 2019 at 02:29:52PM +0100, Stefan Hajnoczi wrote: > On Fri, Sep 27, 2019 at 01:26:50PM +0200, Stefano Garzarella wrote: > > Hi all, > > this series adds the multi-transports support to vsock, following > > this proposal: > > https://www.spinics.net/lists/netdev/msg575792.html > > Ni

[PATCH 4.19 004/114] s390/cio: exclude subchannels with no parent from pseudo check

2019-10-10 Thread Greg Kroah-Hartman
From: Vasily Gorbik commit ab5758848039de9a4b249d46e4ab591197eebaf2 upstream. ccw console is created early in start_kernel and used before css is initialized or ccw console subchannel is registered. Until then console subchannel does not have a parent. For that reason assume subchannels with no

[PATCH 4.19 005/114] KVM: PPC: Book3S HV: Fix race in re-enabling XIVE escalation interrupts

2019-10-10 Thread Greg Kroah-Hartman
From: Paul Mackerras commit 959c5d5134786b4988b6fdd08e444aa67d1667ed upstream. Escalation interrupts are interrupts sent to the host by the XIVE hardware when it has an interrupt to deliver to a guest VCPU but that VCPU is not running anywhere in the system. Hence we disable the escalation inte

[PATCH 4.19 053/114] 9p: avoid attaching writeback_fid on mmap with type PRIVATE

2019-10-10 Thread Greg Kroah-Hartman
From: Chengguang Xu [ Upstream commit c87a37ebd40b889178664c2c09cc187334146292 ] Currently on mmap cache policy, we always attach writeback_fid whether mmap type is SHARED or PRIVATE. However, in the use case of kata-container which combines 9p(Guest OS) with overlayfs(Host OS), this behavior wi

[PATCH 4.19 051/114] fs: nfs: Fix possible null-pointer dereferences in encode_attrs()

2019-10-10 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit e2751463eaa6f9fec8fea80abbdc62dbc487b3c5 ] In encode_attrs(), there is an if statement on line 1145 to check whether label is NULL: if (label && (attrmask[2] & FATTR4_WORD2_SECURITY_LABEL)) When label is NULL, it is used on lines 1178-1181: *p++ = cpu_

[PATCH 4.19 061/114] pNFS: Ensure we do clear the return-on-close layout stateid on fatal errors

2019-10-10 Thread Greg Kroah-Hartman
From: Trond Myklebust [ Upstream commit 9c47b18cf722184f32148784189fca945a7d0561 ] IF the server rejected our layout return with a state error such as NFS4ERR_BAD_STATEID, or even a stale inode error, then we do want to clear out all the remaining layout segments and mark that stateid as invalid

[PATCH 4.19 047/114] cfg80211: initialize on-stack chandefs

2019-10-10 Thread Greg Kroah-Hartman
From: Johannes Berg commit f43e5210c739fe76a4b0ed851559d6902f20ceb1 upstream. In a few places we don't properly initialize on-stack chandefs, resulting in EDMG data to be non-zero, which broke things. Additionally, in a few places we rely on the driver to init the data completely, but perhaps w

[PATCH 4.19 060/114] drm/amdgpu: Check for valid number of registers to read

2019-10-10 Thread Greg Kroah-Hartman
From: Trek [ Upstream commit 73d8e6c7b841d9bf298c8928f228fb433676635c ] Do not try to allocate any amount of memory requested by the user. Instead limit it to 128 registers. Actually the longest series of consecutive allowed registers are 48, mmGB_TILE_MODE0-31 and mmGB_MACROTILE_MODE0-15 (0x264

[PATCH 4.19 057/114] watchdog: aspeed: Add support for AST2600

2019-10-10 Thread Greg Kroah-Hartman
From: Ryan Chen [ Upstream commit b3528b4874480818e38e4da019d655413c233e6a ] The ast2600 can be supported by the same code as the ast2500. Signed-off-by: Ryan Chen Signed-off-by: Joel Stanley Reviewed-by: Guenter Roeck Link: https://lore.kernel.org/r/20190819051738.17370-3-j...@jms.id.au Sig

[PATCH 4.19 049/114] ima: always return negative code for error

2019-10-10 Thread Greg Kroah-Hartman
From: Sascha Hauer [ Upstream commit f5e1040196dbfe14c77ce3dfe3b7b08d2d961e88 ] integrity_kernel_read() returns the number of bytes read. If this is a short read then this positive value is returned from ima_calc_file_hash_atfm(). Currently this is only indirectly called from ima_calc_file_hash(

[PATCH 4.19 056/114] ceph: reconnect connection if session hang in opening state

2019-10-10 Thread Greg Kroah-Hartman
From: Erqi Chen [ Upstream commit 71a228bc8d65900179e37ac309e678f8c523f133 ] If client mds session is evicted in CEPH_MDS_SESSION_OPENING state, mds won't send session msg to client, and delayed_work skip CEPH_MDS_SESSION_OPENING state session, the session hang forever. Allow ceph_con_keepalive

[PATCH 4.19 064/114] ntb: point to right memory window index

2019-10-10 Thread Greg Kroah-Hartman
From: Sanjay R Mehta [ Upstream commit ae89339b08f3fe02457ec9edd512ddc3d246d0f8 ] second parameter of ntb_peer_mw_get_addr is pointing to wrong memory window index by passing "peer gidx" instead of "local gidx". For ex, "local gidx" value is '0' and "peer gidx" value is '1', then on peer side

[PATCH 4.19 062/114] pwm: stm32-lp: Add check in case requested period cannot be achieved

2019-10-10 Thread Greg Kroah-Hartman
From: Fabrice Gasnier [ Upstream commit c91e3234c6035baf5a79763cb4fcd5d23ce75c2b ] LPTimer can use a 32KHz clock for counting. It depends on clock tree configuration. In such a case, PWM output frequency range is limited. Although unlikely, nothing prevents user from requesting a PWM frequency a

[PATCH 4.19 039/114] drm/nouveau/kms/nv50-: Dont create MSTMs for eDP connectors

2019-10-10 Thread Greg Kroah-Hartman
From: Lyude Paul commit 698c1aa9f83b618de79e9e5e19a58f70a4a6ae0f upstream. On the ThinkPad P71, we have one eDP connector exposed along with 5 DP connectors, resulting in a total of 11 TMDS encoders. Since the GPU on this system is also capable of MST, we create an additional 4 fake MST encoders

[PATCH 4.19 065/114] thermal: Fix use-after-free when unregistering thermal zone device

2019-10-10 Thread Greg Kroah-Hartman
From: Ido Schimmel [ Upstream commit 1851799e1d2978f68eea5d9dff322e121dcf59c1 ] thermal_zone_device_unregister() cancels the delayed work that polls the thermal zone, but it does not wait for it to finish. This is racy with respect to the freeing of the thermal zone device, which can result in a

Re: [PATCH v2 07/11] VSOCK: add AF_VSOCK test cases

2019-10-10 Thread Stefano Garzarella
On Wed, Oct 09, 2019 at 04:15:03PM +0100, Stefan Hajnoczi wrote: > On Wed, Oct 09, 2019 at 12:03:53PM +0200, Stefano Garzarella wrote: > > Hi Stefan, > > I'm thinking about dividing this test into single applications, one > > for each test, do you think it makes sense? > > Or is it just a useless c

[PATCH 4.19 073/114] perf build: Add detection of java-11-openjdk-devel package

2019-10-10 Thread Greg Kroah-Hartman
From: Thomas Richter [ Upstream commit 815c1560bf8fd522b8d93a1d727868b910c1cc24 ] With Java 11 there is no seperate JRE anymore. Details: https://coderanch.com/t/701603/java/JRE-JDK Therefore the detection of the JRE needs to be adapted. This change works for s390 and x86. I have not test

[PATCH 4.19 070/114] sched/membarrier: Call sync_core only before usermode for same mm

2019-10-10 Thread Greg Kroah-Hartman
From: Mathieu Desnoyers [ Upstream commit 2840cf02fae627860156737e83326df354ee4ec6 ] When the prev and next task's mm change, switch_mm() provides the core serializing guarantees before returning to usermode. The only case where an explicit core serialization is needed is when the scheduler keep

[PATCH 4.19 040/114] drm/i915/gvt: update vgpu workload head pointer correctly

2019-10-10 Thread Greg Kroah-Hartman
From: Xiaolin Zhang commit 0a3242bdb47713e09cb004a0ba4947d3edf82d8a upstream. when creating a vGPU workload, the guest context head pointer should be updated correctly by comparing with the exsiting workload in the guest worklod queue including the current running context. in some situation, th

[PATCH 4.19 075/114] perf unwind: Fix libunwind build failure on i386 systems

2019-10-10 Thread Greg Kroah-Hartman
From: Arnaldo Carvalho de Melo [ Upstream commit 26acf400d2dcc72c7e713e1f55db47ad92010cc2 ] Naresh Kamboju reported, that on the i386 build pr_err() doesn't get defined properly due to header ordering: perf-in.o: In function `libunwind__x86_reg_id': tools/perf/util/libunwind/../../arch/x86/

[PATCH 4.19 082/114] powerpc/book3s64/radix: Rename CPU_FTR_P9_TLBIE_BUG feature flag

2019-10-10 Thread Greg Kroah-Hartman
From: Aneesh Kumar K.V Rename the #define to indicate this is related to store vs tlbie ordering issue. In the next patch, we will be adding another feature flag that is used to handles ERAT flush vs tlbie ordering issue. Fixes: a5d4b5891c2f ("powerpc/mm: Fixup tlbie vs store ordering issue on

Re: [PATCH] xen/grant-table: remove unnecessary printing

2019-10-10 Thread Jürgen Groß
On 10.10.19 10:32, Fuqian Huang wrote: xen_auto_xlat_grant_frames.vaddr is definitely NULL in this case. So the address printing is unnecessary. Signed-off-by: Fuqian Huang Reviewed-by: Juergen Gross Juergen

[PATCH 4.19 079/114] KVM: nVMX: Fix consistency check on injected exception error code

2019-10-10 Thread Greg Kroah-Hartman
From: Sean Christopherson [ Upstream commit 567926cca99ba1750be8aae9c4178796bf9bb90b ] Current versions of Intel's SDM incorrectly state that "bits 31:15 of the VM-Entry exception error-code field" must be zero. In reality, bits 31:16 must be zero, i.e. error codes are 16-bit values. The bogus

[PATCH 4.19 100/114] arm64: add sysfs vulnerability show for spectre-v2

2019-10-10 Thread Greg Kroah-Hartman
From: Jeremy Linton [ Upstream commit d2532e27b5638bb2e2dd52b80b7ea2ec65135377 ] Track whether all the cores in the machine are vulnerable to Spectre-v2, and whether all the vulnerable cores have been mitigated. We then expose this information to userspace via sysfs. Signed-off-by: Jeremy Linto

[PATCH 4.19 080/114] nbd: fix crash when the blksize is zero

2019-10-10 Thread Greg Kroah-Hartman
From: Xiubo Li [ Upstream commit 553768d1169a48c0cd87c4eb4ab57534ee663415 ] This will allow the blksize to be set zero and then use 1024 as default. Reviewed-by: Josef Bacik Signed-off-by: Xiubo Li [fix to use goto out instead of return in genl_connect] Signed-off-by: Mike Christie Signed-of

[PATCH 4.19 042/114] mmc: sdhci-of-esdhc: set DMA snooping based on DMA coherence

2019-10-10 Thread Greg Kroah-Hartman
From: Russell King commit 121bd08b029e03404c451bb237729cdff76eafed upstream. We must not unconditionally set the DMA snoop bit; if the DMA API is assuming that the device is not DMA coherent, and the device snoops the CPU caches, the device can see stale cache lines brought in by speculative pre

[PATCH 4.19 099/114] arm64: Always enable spectre-v2 vulnerability detection

2019-10-10 Thread Greg Kroah-Hartman
From: Jeremy Linton [ Upstream commit 8c1e3d2bb44cbb998cb28ff9a18f105fee7f1eb3 ] Ensure we are always able to detect whether or not the CPU is affected by Spectre-v2, so that we can later advertise this to userspace. Signed-off-by: Jeremy Linton Reviewed-by: Andre Przywara Reviewed-by: Catali

[PATCH 4.19 078/114] KVM: PPC: Book3S HV: XIVE: Free escalation interrupts before disabling the VP

2019-10-10 Thread Greg Kroah-Hartman
From: Cédric Le Goater [ Upstream commit 237aed48c642328ff0ab19b63423634340224a06 ] When a vCPU is brought done, the XIVE VP (Virtual Processor) is first disabled and then the event notification queues are freed. When freeing the queues, we check for possible escalation interrupts and free them

[PATCH 4.19 081/114] powerpc/pseries: Fix cpu_hotplug_lock acquisition in resize_hpt()

2019-10-10 Thread Greg Kroah-Hartman
From: Gautham R. Shenoy [ Upstream commit c784be435d5dae28d3b03db31753dd7a18733f0c ] The calls to arch_add_memory()/arch_remove_memory() are always made with the read-side cpu_hotplug_lock acquired via memory_hotplug_begin(). On pSeries, arch_add_memory()/arch_remove_memory() eventually call res

[PATCH 4.19 036/114] perf stat: Fix a segmentation fault when using repeat forever

2019-10-10 Thread Greg Kroah-Hartman
From: Srikar Dronamraju commit 443f2d5ba13d65ccfd879460f77941875159d154 upstream. Observe a segmentation fault when 'perf stat' is asked to repeat forever with the interval option. Without fix: # perf stat -r 0 -I 5000 -e cycles -a sleep 10 # time counts unit events

[PATCH 4.19 096/114] arm64: Always enable ssb vulnerability detection

2019-10-10 Thread Greg Kroah-Hartman
From: Jeremy Linton [ Upstream commit d42281b6e49510f078ace15a8ea10f71e6262581 ] Ensure we are always able to detect whether or not the CPU is affected by SSB, so that we can later advertise this to userspace. Signed-off-by: Jeremy Linton Reviewed-by: Andre Przywara Reviewed-by: Catalin Marin

[PATCH 4.19 097/114] arm64: Provide a command line to disable spectre_v2 mitigation

2019-10-10 Thread Greg Kroah-Hartman
From: Jeremy Linton [ Upstream commit e5ce5e7267ddcbe13ab9ead2542524e1b7993e5a ] There are various reasons, such as benchmarking, to disable spectrev2 mitigation on a machine. Provide a command-line option to do so. Signed-off-by: Jeremy Linton Reviewed-by: Suzuki K Poulose Reviewed-by: Andre

[PATCH 4.19 093/114] arm64: Add sysfs vulnerability show for spectre-v1

2019-10-10 Thread Greg Kroah-Hartman
From: Mian Yousaf Kaukab [ Upstream commit 3891ebccace188af075ce143d8b072b65e90f695 ] spectre-v1 has been mitigated and the mitigation is always active. Report this to userspace via sysfs Signed-off-by: Mian Yousaf Kaukab Signed-off-by: Jeremy Linton Reviewed-by: Andre Przywara Reviewed-by:

[PATCH 4.19 084/114] tick: broadcast-hrtimer: Fix a race in bc_set_next

2019-10-10 Thread Greg Kroah-Hartman
From: Balasubramani Vivekanandan [ Upstream commit b9023b91dd020ad7e093baa5122b6968c48cc9e0 ] When a cpu requests broadcasting, before starting the tick broadcast hrtimer, bc_set_next() checks if the timer callback (bc_handler) is active using hrtimer_try_to_cancel(). But hrtimer_try_to_cancel()

[PATCH 4.19 044/114] xen/xenbus: fix self-deadlock after killing user process

2019-10-10 Thread Greg Kroah-Hartman
From: Juergen Gross commit a8fabb38525c51a094607768bac3ba46b3f4a9d5 upstream. In case a user process using xenbus has open transactions and is killed e.g. via ctrl-C the following cleanup of the allocated resources might result in a deadlock due to trying to end a transaction in the xenbus worke

[PATCH 4.19 045/114] ieee802154: atusb: fix use-after-free at disconnect

2019-10-10 Thread Greg Kroah-Hartman
From: Johan Hovold commit 7fd25e6fc035f4b04b75bca6d7e8daa069603a76 upstream. The disconnect callback was accessing the hardware-descriptor private data after having having freed it. Fixes: 7490b008d123 ("ieee802154: add support for atusb transceiver") Cc: stable # 4.2 Cc: Alexander Aring

[PATCH 4.19 043/114] Revert "locking/pvqspinlock: Dont wait if vCPU is preempted"

2019-10-10 Thread Greg Kroah-Hartman
From: Wanpeng Li commit 89340d0935c9296c7b8222b6eab30e67cb57ab82 upstream. This patch reverts commit 75437bb304b20 (locking/pvqspinlock: Don't wait if vCPU is preempted). A large performance regression was caused by this commit. on over-subscription scenarios. The test was run on a Xeon Skyla

[PATCH 4.19 094/114] arm64: add sysfs vulnerability show for meltdown

2019-10-10 Thread Greg Kroah-Hartman
From: Jeremy Linton [ Upstream commit 1b3ccf4be0e7be8c4bd8522066b6cbc92591e912 ] We implement page table isolation as a mitigation for meltdown. Report this to userspace via sysfs. Signed-off-by: Jeremy Linton Reviewed-by: Suzuki K Poulose Reviewed-by: Andre Przywara Reviewed-by: Catalin Mar

[PATCH 4.19 105/114] arm64/speculation: Support mitigations= cmdline option

2019-10-10 Thread Greg Kroah-Hartman
From: Josh Poimboeuf commit a111b7c0f20e13b54df2fa959b3dc0bdf1925ae6 upstream. Configure arm64 runtime CPU speculation bug mitigations in accordance with the 'mitigations=' cmdline option. This affects Meltdown, Spectre v2, and Speculative Store Bypass. The default behavior is unchanged. Sign

[PATCH 4.19 111/114] staging: erofs: detect potential multiref due to corrupted images

2019-10-10 Thread Greg Kroah-Hartman
From: Gao Xiang commit e12a0ce2fa69798194f3a8628baf6edfbd5c548f upstream. As reported by erofs-utils fuzzer, currently, multiref (ondisk deduplication) hasn't been supported for now, we should forbid it properly. Fixes: 3883a79abd02 ("staging: erofs: introduce VLE decompression support") Cc: #

[PATCH 4.19 104/114] arm64: Use firmware to detect CPUs that are not affected by Spectre-v2

2019-10-10 Thread Greg Kroah-Hartman
From: Marc Zyngier commit 517953c2c47f9c00a002f588ac856a5bc70cede3 upstream. The SMCCC ARCH_WORKAROUND_1 service can indicate that although the firmware knows about the Spectre-v2 mitigation, this particular CPU is not vulnerable, and it is thus not necessary to call the firmware on this CPU. L

[PATCH 4.19 112/114] cfg80211: add and use strongly typed element iteration macros

2019-10-10 Thread Greg Kroah-Hartman
From: Johannes Berg commit 0f3b07f027f87a38ebe5c436490095df762819be upstream. Rather than always iterating elements from frames with pure u8 pointers, add a type "struct element" that encapsulates the id/datalen/data format of them. Then, add the element iteration macros * for_each_element *

[PATCH 4.19 108/114] staging: erofs: fix an error handling in erofs_readdir()

2019-10-10 Thread Greg Kroah-Hartman
From: Gao Xiang commit acb383f1dcb4f1e79b66d4be3a0b6f519a957b0d upstream. Richard observed a forever loop of erofs_read_raw_page() [1] which can be generated by forcely setting ->u.i_blkaddr to 0xdeadbeef (as my understanding block layer can handle access beyond end of device correctly). After

[PATCH 4.19 109/114] staging: erofs: some compressed cluster should be submitted for corrupted images

2019-10-10 Thread Greg Kroah-Hartman
From: Gao Xiang commit ee45197c807895e156b2be0abcaebdfc116487c8 upstream. As reported by erofs_utils fuzzer, a logical page can belong to at most 2 compressed clusters, if one compressed cluster is corrupted, but the other has been ready in submitting chain. The chain needs to submit anyway in

[PATCH 4.19 107/114] coresight: etm4x: Use explicit barriers on enable/disable

2019-10-10 Thread Greg Kroah-Hartman
From: Andrew Murray commit 1004ce4c255fc3eb3ad9145ddd53547d1b7ce327 upstream. Synchronization is recommended before disabling the trace registers to prevent any start or stop points being speculative at the point of disabling the unit (section 7.3.77 of ARM IHI 0064D). Synchronization is also r

[PATCH 4.19 110/114] staging: erofs: add two missing erofs_workgroup_put for corrupted images

2019-10-10 Thread Greg Kroah-Hartman
From: Gao Xiang commit 138e1a0990e80db486ab9f6c06bd5c01f9a97999 upstream. As reported by erofs-utils fuzzer, these error handling path will be entered to handle corrupted images. Lack of erofs_workgroup_puts will cause unmounting unsuccessfully. Fix these return values to EFSCORRUPTED as well.

[PATCH 4.19 113/114] cfg80211: Use const more consistently in for_each_element macros

2019-10-10 Thread Greg Kroah-Hartman
From: Jouni Malinen commit 7388afe09143210f555bdd6c75035e9acc1fab96 upstream. Enforce the first argument to be a correct type of a pointer to struct element and avoid unnecessary typecasts from const to non-const pointers (the change in validate_ie_attr() is needed to make this part work). In ad

[PATCH 4.19 114/114] nl80211: validate beacon head

2019-10-10 Thread Greg Kroah-Hartman
From: Johannes Berg commit f88eb7c0d002a67ef31aeb7850b42ff69abc46dc upstream. We currently don't validate the beacon head, i.e. the header, fixed part and elements that are to go in front of the TIM element. This means that the variable elements there can be malformed, e.g. have a length exceedi

[PATCH 4.19 087/114] drm/i915/userptr: Acquire the page lock around set_page_dirty()

2019-10-10 Thread Greg Kroah-Hartman
From: Chris Wilson [ Upstream commit cb6d7c7dc7ff8cace666ddec66334117a6068ce2 ] set_page_dirty says: For pages with a mapping this should be done under the page lock for the benefit of asynchronous memory errors who prefer a consistent dirty state. This rule can be broke

[PATCH 4.19 086/114] perf stat: Reset previous counts on repeat with interval

2019-10-10 Thread Greg Kroah-Hartman
From: Srikar Dronamraju [ Upstream commit b63fd11cced17fcb8e133def29001b0f6aaa5e06 ] When using 'perf stat' with repeat and interval option, it shows wrong values for events. The wrong values will be shown for the first interval on the second and subsequent repetitions. Without the fix: # p

Re: [alsa-devel] [PATCH v2 3/5] ASoC: core: add support to snd_soc_dai_get_sdw_stream()

2019-10-10 Thread Srinivas Kandagatla
On 09/10/2019 19:53, Pierre-Louis Bossart wrote: On 10/9/19 11:01 AM, Srinivas Kandagatla wrote: On 09/10/2019 15:29, Pierre-Louis Bossart wrote: On 10/9/19 3:32 AM, Srinivas Kandagatla wrote: Hi Pierre, On 14/08/2019 15:09, Pierre-Louis Bossart wrote: On 8/13/19 11:11 PM, Vinod K

[PATCH 4.14 05/61] s390/cio: exclude subchannels with no parent from pseudo check

2019-10-10 Thread Greg Kroah-Hartman
From: Vasily Gorbik commit ab5758848039de9a4b249d46e4ab591197eebaf2 upstream. ccw console is created early in start_kernel and used before css is initialized or ccw console subchannel is registered. Until then console subchannel does not have a parent. For that reason assume subchannels with no

[PATCH 4.14 07/61] KVM: nVMX: handle page fault in vmread fix

2019-10-10 Thread Greg Kroah-Hartman
From: Jack Wang During backport f7eea636c3d5 ("KVM: nVMX: handle page fault in vmread"), there was a mistake the exception reference should be passed to function kvm_write_guest_virt_system, instead of NULL, other wise, we will get NULL pointer deref, eg kvm-unit-test triggered a NULL pointer de

[PATCH 4.14 03/61] s390/topology: avoid firing events before kobjs are created

2019-10-10 Thread Greg Kroah-Hartman
From: Vasily Gorbik commit f3122a79a1b0a113d3aea748e0ec26f2cb2889de upstream. arch_update_cpu_topology is first called from: kernel_init_freeable->sched_init_smp->sched_init_domains even before cpus has been registered in: kernel_init_freeable->do_one_initcall->s390_smp_init Do not trigger kob

Re: [PATCH 0/3] ftrace: Introduce PERMANENT ftrace_ops flag

2019-10-10 Thread Petr Mladek
On Wed 2019-10-09 10:26:54, Steven Rostedt wrote: > Petr Mladek wrote: > I think Joe's approach is much easier to understand and implement. The > "ftrace_enabled" is a global flag, and affects all things ftrace (the > function bindings). What this patch was doing, was what you said. Make > ftrace_

Re: [RFC PATCH 06/13] vsock: add 'struct vsock_sock *' param to vsock_core_get_transport()

2019-10-10 Thread Stefano Garzarella
On Wed, Oct 09, 2019 at 12:54:33PM +0100, Stefan Hajnoczi wrote: > On Fri, Sep 27, 2019 at 01:26:56PM +0200, Stefano Garzarella wrote: > > -const struct vsock_transport *vsock_core_get_transport(void) > > +const struct vsock_transport *vsock_core_get_transport(struct vsock_sock > > *vsk) > > { >

[PATCH 4.14 20/61] watchdog: imx2_wdt: fix min() calculation in imx2_wdt_set_timeout

2019-10-10 Thread Greg Kroah-Hartman
From: Rasmus Villemoes commit 144783a80cd2cbc45c6ce17db649140b65f203dd upstream. Converting from ms to s requires dividing by 1000, not multiplying. So this is currently taking the smaller of new_timeout and 1.28e8, i.e. effectively new_timeout. The driver knows what it set max_hw_heartbeat_ms

[PATCH 4.14 02/61] KVM: s390: Test for bad access register and size at the start of S390_MEM_OP

2019-10-10 Thread Greg Kroah-Hartman
From: Thomas Huth commit a13b03bbb4575b350b46090af4dfd30e735aaed1 upstream. If the KVM_S390_MEM_OP ioctl is called with an access register >= 16, then there is certainly a bug in the calling userspace application. We check for wrong access registers, but only if the vCPU was already in the acces

[PATCH 4.14 13/61] crypto: qat - Silence smp_processor_id() warning

2019-10-10 Thread Greg Kroah-Hartman
From: Alexander Sverdlin commit 1b82feb6c5e1996513d0fb0bbb475417088b4954 upstream. It seems that smp_processor_id() is only used for a best-effort load-balancing, refer to qat_crypto_get_instance_node(). It's not feasible to disable preemption for the duration of the crypto requests. Therefore,

[PATCH 4.14 16/61] crypto: caam - fix concurrency issue in givencrypt descriptor

2019-10-10 Thread Greg Kroah-Hartman
From: Horia Geantă commit 48f89d2a2920166c35b1c0b69917dbb0390ebec7 upstream. IV transfer from ofifo to class2 (set up at [29][30]) is not guaranteed to be scheduled before the data transfer from ofifo to external memory (set up at [38]: [29] 10FA0004 ld: ind-nfifo (len=4) imm [30] 81F

[PATCH 4.14 10/61] powerpc/powernv: Restrict OPAL symbol map to only be readable by root

2019-10-10 Thread Greg Kroah-Hartman
From: Andrew Donnellan commit e7de4f7b64c23e503a8c42af98d56f2a7462bd6d upstream. Currently the OPAL symbol map is globally readable, which seems bad as it contains physical addresses. Restrict it to root. Fixes: c8742f85125d ("powerpc/powernv: Expose OPAL firmware symbol map") Cc: sta...@vger.

[PATCH 4.14 19/61] timer: Read jiffies once when forwarding base clk

2019-10-10 Thread Greg Kroah-Hartman
From: Li RongQing commit e430d802d6a3aaf61bd3ed03d9404888a29b9bf9 upstream. The timer delayed for more than 3 seconds warning was triggered during testing. Workqueue: events_unbound sched_tick_remote RIP: 0010:sched_tick_remote+0xee/0x100 ... Call Trace: process_one_work+0x18c/0x3a0

[PATCH 4.14 15/61] crypto: cavium/zip - Add missing single_release()

2019-10-10 Thread Greg Kroah-Hartman
From: Wei Yongjun commit c552ffb5c93d9d65aaf34f5f001c4e7e8484ced1 upstream. When using single_open() for opening, single_release() should be used instead of seq_release(), otherwise there is a memory leak. Fixes: 09ae5d37e093 ("crypto: zip - Add Compression/Decompression statistics") Cc: Signe

[PATCH 4.14 24/61] Revert "locking/pvqspinlock: Dont wait if vCPU is preempted"

2019-10-10 Thread Greg Kroah-Hartman
From: Wanpeng Li commit 89340d0935c9296c7b8222b6eab30e67cb57ab82 upstream. This patch reverts commit 75437bb304b20 (locking/pvqspinlock: Don't wait if vCPU is preempted). A large performance regression was caused by this commit. on over-subscription scenarios. The test was run on a Xeon Skyla

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