Re: [PATCH v2 0/4] [powerpc] perf vendor events: Add JSON metrics for POWER8

Em Thu, Feb 07, 2019 at 12:53:10PM -0500, Paul Clarke escreveu: > The patches define metrics and metric groups for computation by "perf" for > POWER8 processors. > > Paul Clarke (4): > [powerpc] perf vendor events: Add JSON metrics for POWER8 1/4 > [powerpc] perf vendor events: Add JSON

[PATCH 4.20 314/352] ALSA: compress: Fix stop handling on compressed capture streams

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Charles Keepax commit 4f2ab5e1d13d6aa77c55f4914659784efd776eb4 upstream. It is normal user behaviour to start, stop, then start a stream again without closing it. Currently this works for

[PATCH 4.20 350/352] serial: sh-sci: Do not free irqs that have already been freed

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Chris Brandt commit 4d95987a32db53f3beca76f8c4c8309ef6a5f192 upstream. Since IRQs might be muxed on some parts, we need to pay attention when we are freeing them. Otherwise we get the ugly

Re: [PATCH 6/7] ARM: dts: suniv: Add pinmux for SPI0 and SPI1 of F1C100s

On Mon, Feb 11, 2019 at 12:21:12PM +0300, Mesih Kilinc wrote: > PC0~PC4 is pin group for SPI0. PA0~PA4 is pin group for SPI1. > Add device tree nodes for this groups. > > Signed-off-by: Mesih Kilinc > --- > arch/arm/boot/dts/suniv-f1c100s.dtsi | 10 ++ > 1 file changed, 10 insertions(+)

[PATCH 4.20 352/352] nfsd: Fix error return values for nfsd4_clone_file_range()

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit e3fdc89ca47ef34dfb6fd5101fec084c3dba5486 upstream. If the parameter 'count' is non-zero, nfsd4_clone_file_range() will currently clobber all errors returned by

Re: [PATCH 1/2] PM-runtime: Take suppliers into account in __pm_runtime_set_status()

On Mon, 11 Feb 2019 at 14:27, Ulf Hansson wrote: > > On Thu, 7 Feb 2019 at 19:46, Rafael J. Wysocki wrote: > > > > From: Rafael J. Wysocki > > > > If the target device has any suppliers, as reflected by device links > > to them, __pm_runtime_set_status() does not take them into account, > >

[PATCH 4.20 344/352] perf/x86/intel: Delay memory deallocation until x86_pmu_dead_cpu()

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 602cae04c4864bb3487dfe4c2126c8d9e7e1614a upstream. intel_pmu_cpu_prepare() allocated memory for ->shared_regs among other members of struct cpu_hw_events. This memory is

[PATCH 4.20 345/352] x86/MCE: Initialize mce.bank in the case of a fatal error in mce_no_way_out()

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit d28af26faa0b1daf3c692603d46bc4687c16f19e upstream. Internal injection testing crashed with a console log that said: mce: [Hardware Error]: CPU 7: Machine Check Exception:

[PATCH 4.20 343/352] perf/x86/intel/uncore: Add Node ID mask

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Kan Liang commit 9e63a7894fd302082cf3627fe90844421a6cbe7f upstream. Some PCI uncore PMUs cannot be registered on an 8-socket system (HPE Superdome Flex). To understand which Socket the PCI

[PATCH] fix flush_tlb_all typo

Fix typo, flush_tlb_all should be flush_iotlb_all Signed-off-by: Tom Murphy --- include/linux/iommu.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/iommu.h b/include/linux/iommu.h index a1d28f42cb77..bb4bf1269e5d 100644 --- a/include/linux/iommu.h +++

Re: [PATCH v3 1/7] dump_stack: Support adding to the dump stack arch description

On Mon 2019-02-11 13:50:35, Andrea Parri wrote: > Hi Michael, > > > On Thu, Feb 07, 2019 at 11:46:29PM +1100, Michael Ellerman wrote: > > Arch code can set a "dump stack arch description string" which is > > displayed with oops output to describe the hardware platform. > > > > It is useful to

[PATCH 4.19 019/313] ARM: 8808/1: kexec:offline panic_smp_self_stop CPU

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 82c08c3e7f171aa7f579b231d0abbc1d62e91974 ] In case panic() and panic() called at the same time on different CPUS. For example: CPU 0: panic() __crash_kexec

[PATCH 4.19 003/313] staging: iio: adc: ad7280a: handle error from __ad7280_read32()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0559ef7fde67bc6c83c6eb6329dbd6649528263e ] Inside __ad7280_read32(), the spi_sync_transfer() can fail with negative error code. This change will ensure that this error is being

[PATCH 4.19 002/313] drm/bufs: Fix Spectre v1 vulnerability

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a37805098900a6e73a55b3a43b7d3bcd987bb3f4 ] idx can be indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre variant 1 vulnerability. This

[PATCH 4.19 006/313] ASoC: Intel: mrfld: fix uninitialized variable access

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1539c7f23f256120f89f8b9ec53160790bce9ed2 ] Randconfig testing revealed a very old bug, with gcc-8: sound/soc/intel/atom/sst/sst_loader.c: In function 'sst_load_fw':

[PATCH 4.19 005/313] pinctrl: bcm2835: Use raw spinlock for RT compatibility

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3c7b30f704b6f5e53eed6bf89cf2c8d1b38b02c0 ] The BCM2835 pinctrl driver acquires a spinlock in its ->irq_enable, ->irq_disable and ->irq_set_type callbacks. Spinlocks become sleeping

[PATCH 4.19 007/313] gpiolib: Fix possible use after free on label

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 18534df419041e6c1f4b41af56ee7d41f757815c ] gpiod_request_commit() copies the pointer to the label passed as an argument only to be used later. But there's a chance the caller could

[PATCH 4.19 032/313] fpga: altera-cvp: Fix registration for CvP incapable devices

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 68f60538daa4bc3da5d0764d46f391916fba20fd ] The probe function needs to verify the CvP enable bit in order to properly determine if FPGA Manager functionality can be safely enabled.

[PATCH 4.19 039/313] staging: iio: ad7780: update voltage on read

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 336650c785b62c3bea7c8cf6061c933a90241f67 ] The ad7780 driver previously did not read the correct device output, as it read an outdated value set at initialization. It now updates

[PATCH 4.19 038/313] scsi: hisi_sas: change the time of SAS SSP connection

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 15bc43f31a074076f114e0b87931e3b220b7bff1 ] Currently the time of SAS SSP connection is 1ms, which means the link connection will fail if no IO response after this period. For some

[PATCH 4.19 023/313] powerpc/pseries: add of_node_put() in dlpar_detach_node()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5b3f5c408d8cc59b87e47f1ab9803dbd006e4a91 ] The previous commit, "of: overlay: add missing of_node_get() in __of_attach_node_sysfs" added a missing of_node_get() to

[PATCH 4.19 034/313] fpga: altera-cvp: fix bad IO access on x86_64

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 187fade88ca0ff2df9d360ca751d948d73db7095 ] If mapping the CvP BAR fails, we still can configure the FPGA via PCI config space access. In this case the iomap pointer is NULL. On

[PATCH 4.19 036/313] platform/chrome: dont report EC_MKBP_EVENT_SENSOR_FIFO as wakeup

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6ad16b78a039b45294b1ad5d69c14ac57b2fe706 ] EC_MKBP_EVENT_SENSOR_FIFO events can be triggered for a variety of reasons, and there are very few cases in which they should be treated

[PATCH 4.19 026/313] serial: fsl_lpuart: clear parity enable bit when disable parity

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 397bd9211fe014b347ca8f95a8f4e1017bac1aeb ] Current driver only enable parity enable bit and never clear it when user set the termios. The fix clear the parity enable bit when PARENB

[PATCH 4.19 052/313] media: mtk-vcodec: Release device nodes in mtk_vcodec_init_enc_pm()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8ea0f2ba0fa3f91ea1b8d823a54b042026ada6b3 ] of_parse_phandle() returns the device node with refcount incremented. There are two nodes that are used temporary in

Re: [PATCH v3 0/8] Fix breakage caused by the NTB multi-port patchset

On Wed, Jan 09, 2019 at 12:22:25PM -0700, Logan Gunthorpe wrote: > Hey, > > I'm resending this because I've recently found out that the change we > made to use the NTB struct device in DMA allocations is wrong and > needs to be reverted. Turns out that, when running with an IOMMU, >

[PATCH 4.19 051/313] media: video-i2c: avoid accessing released memory area when removing driver

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c764da98a600a4b068d25c77164f092f159cecec ] The video device release() callback for video-i2c driver frees the whole struct video_i2c_data. If there is no user left for the video

[PATCH 4.19 050/313] media: rc: ensure close() is called on rc_unregister_device

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8e782fcf78275f505194e767c515202d4fd274bc ] If userspace has an open file descriptor on the rc input device or lirc device when rc_unregister_device() is called, then the rc close()

Re: [PATCH 4.20 018/352] ath9k: dynack: use authentication messages for late ack

On 11.02.19 15:14, Greg Kroah-Hartman wrote: 4.20-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3831a2a0010c72e3956020cbf1057a1701a2e469 ] In order to properly support dynack in ad-hoc mode running wpa_supplicant, take into

[PATCH 4.19 027/313] ptp: check gettime64 return code in PTP_SYS_OFFSET ioctl

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 83d0bdc7390b890905634186baaa294475cd6a06 ] If a gettime64 call fails, return the error and avoid copying data back to user. Cc: Richard Cochran Cc: Jacob Keller Signed-off-by:

[PATCH 4.19 046/313] net/mlx5: EQ, Use the right place to store/read IRQ affinity hint

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1e86ace4c140fd5a693e266c9b23409358f25381 ] Currently the cpu affinity hint mask for completion EQs is stored and read from the wrong place, since reading and storing is done from

[PATCH 4.19 064/313] media: adv*/tc358743/ths8200: fill in min width/height/pixelclock

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2912289a518077ddb8214e05336700148e97e235 ] The v4l2_dv_timings_cap struct is used to do sanity checks when setting and enumerating DV timings, ensuring that only valid timings as

[PATCH 4.19 065/313] ACPI: SPCR: Consider baud rate 0 as preconfigured state

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b413b1abeb21b4a152c0bf8d1379efa30759b6e3 ] Since SPCR 1.04 [1] the baud rate of 0 means a preconfigured state of UART. Assume firmware or bootloader configures console correctly.

[PATCH 4.19 030/313] iwlwifi: fw: do not set sgi bits for HE connection

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5c2dbebb446539eb9640bf59a02756d6e7f1fc53 ] If the association supports HE, HT/VHT rates will never be used for Tx and therefore there's no need to set the

[PATCH 4.19 067/313] f2fs: move dir data flush to write checkpoint process

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b61ac5b720146c619c7cdf17eff2551b934399e5 ] This patch move dir data flush to write checkpoint process, by doing this, it may reduce some time for dir fsync. pre:

Re: [PATCH] staging: android: vsoc: Remove VSOC_WAIT_FOR_INCOMING_INTERRUPT

On Mon, Feb 11, 2019 at 9:10 PM Greg KH wrote: > > On Mon, Feb 11, 2019 at 08:56:02PM +0530, Souptick Joarder wrote: > > As mentioned in TODO list, Removed VSOC_WAIT_FOR_INCOMING_INTERRUPT > > ioctl. This functionality has been superseded by the futex and is > > there for legacy reasons. > > > >

[PATCH 4.19 073/313] net: aquantia: return err if set MPI_DEINIT state fails

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4e3c7c00bba0636b97eb23d582c20b0f5d95ce20 ] Fixes gcc '-Wunused-but-set-variable' warning: drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c:260:7: warning: variable

[PATCH 4.19 075/313] soc: bcm: brcmstb: Dont leak device tree node reference

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1861a7f07e02292830a1ca256328d370deefea30 ] of_find_node_by_path() acquires a reference to the node returned by it and that reference needs to be dropped by its caller.

Re: [PATCH] slub: fix SLAB_CONSISTENCY_CHECKS + KASAN_SW_TAGS

On Sat, Feb 9, 2019 at 5:41 AM Qian Cai wrote: > > Enabling SLUB_DEBUG's SLAB_CONSISTENCY_CHECKS with KASAN_SW_TAGS > triggers endless false positives during boot below due to > check_valid_pointer() checks tagged pointers which have no addresses > that is valid within slab pages. > > [

[PATCH 4.19 082/313] firmware/efi: Add NULL pointer checks in efivars API functions

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ab2180a15ce54739fed381efb4cb12e78dfb1561 ] Since commit: ce2e6db554fa ("brcmfmac: Add support for getting nvram contents from EFI variables") we have a device driver accessing

[PATCH 4.19 077/313] drm: Clear state->acquire_ctx before leaving drm_atomic_helper_commit_duplicated_state()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aa394b0dd68cb00c483e151dcd84713d4d517ed1 ] drm_atomic_helper_commit_duplicated_state() sets state->acquire_ctx to the context given in the argument and leaves it in state after it

[PATCH 4.19 081/313] thermal: Fix locking in cooling device sysfs update cur_state

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 68000a0d983f539c95ebe5dccd4f29535c7ac0af ] Sysfs interface to update cooling device cur_state does not currently holding cooling device lock sometimes leading to stale values in

[PATCH 4.19 079/313] arm64: io: Ensure value passed to __iormb() is held in a 64-bit register

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1b57ec8c75279b873639eb44a215479236f93481 ] As of commit 6460d3201471 ("arm64: io: Ensure calls to delay routines are ordered against prior readX()"), MMIO reads smaller than 64 bits

[PATCH 4.19 057/313] clk: meson: meson8b: mark the CPU clock as CLK_IS_CRITICAL

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0dad1ec65bc30a549aba38d34a727309bbf41bc8 ] We don't want the common clock framework to disable the "cpu_clk" if it's not used by any device. The cpufreq-dt driver does not enable

[PATCH 4.19 059/313] dmaengine: xilinx_dma: Remove __aligned attribute on zynqmp_dma_desc_ll

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aeaebcc17cdf37065d2693865eeb1ff1c7dc5bf3 ] Clang warns: drivers/dma/xilinx/zynqmp_dma.c:166:4: warning: attribute 'aligned' is ignored, place it after "struct" to apply attribute

Re: [PATCH v2] PCI: Fixup the RTIT_BAR of Intel TH on Denverton

On Mon, Feb 11, 2019 at 08:41:41AM +0100, Ingo Molnar wrote: > > * Alexander Shishkin wrote: > > > On Denverton's integration of the Intel(R) Trace Hub (for a reference > > and overview see Documentation/trace/intel_th.txt) the reported size of > > one of its resources (RTIT_BAR) doesn't match

Re: [5.0-rc5 regression] "scsi: kill off the legacy IO path" causes 5 minute delay during boot on Sun Blade 2500

On 2/11/19 8:42 AM, James Bottomley wrote: > On Mon, 2019-02-11 at 08:28 -0700, Jens Axboe wrote: >> On 2/11/19 8:25 AM, James Bottomley wrote: >>> On Sun, 2019-02-10 at 09:35 -0700, Jens Axboe wrote: On 2/10/19 9:25 AM, James Bottomley wrote: > On Sun, 2019-02-10 at 09:05 -0700, Jens

[PATCH 4.19 100/313] clk: sunxi-ng: a33: Set CLK_SET_RATE_PARENT for all audio module clocks

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6e6da2039c82271dd873b9ad2b902a692a7dd554 ] All the audio interfaces on Allwinner SoCs need to change their module clocks during operation, to switch between support for 44.1 kHz and

[PATCH 4.19 105/313] kobject: return error code if writing /sys/.../uevent fails

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit df44b479654f62b478c18ee4d8bc4e9f897a9844 ] Propagate error code back to userspace if writing the /sys/.../uevent file fails. Before, the write operation always returned with

[PATCH 4.19 112/313] ARM: dts: Fix OMAP4430 SDP Ethernet startup

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 84fb6c7feb1494ebb7d1ec8b95cfb7ada0264465 ] It was noticed that unbinding and rebinding the KSZ8851 ethernet resulted in the driver reporting "failed to read device ID" at probe.

[PATCH 4.19 091/313] media: i2c: TDA1997x: select CONFIG_HDMI

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 79e89e36dc8a47ef965a35b484d737a5227feed1 ] Without CONFIG_HDMI, we get a link error for this driver: drivers/media/i2c/tda1997x.o: In function `tda1997x_parse_infoframe':

Re: [PATCH v5 3/6] math64: New DIV64_U64_ROUND_CLOSEST helper

On Mon, Feb 11, 2019 at 4:22 PM Sergei Shtylyov wrote: > On 02/11/2019 04:58 PM, Simon Horman wrote: > > Provide DIV64_U64_ROUND_CLOSEST helper which performs division rounded to > > the closes integer using an unsigned 64bit dividend and divisor. > >Closest? > > > This will be used in a

[PATCH 4.19 118/313] ARM: dts: imx51-zii-rdu1: Do not specify "power-gpio" for hpa1

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 79da07dec740a42c70963ebacbd2bf8866af9e20 ] TPA6130A2 SD pin on RDU1 is not really controlled by SoC and instead is only meant to notify the system that audio was "muted" by external

[PATCH 4.19 116/313] tracing: Have trace_stack nr_entries compare not be so subtle

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ca16b0fbb05242f18da9d810c07d3882ffed831c ] Dan Carpenter reviewed the trace_stack.c code and figured he found an off by one bug. "From reviewing the code, it seems possible for

[PATCH 4.19 114/313] media: coda: fix H.264 deblocking filter controls

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 75fa6e4f83a0923fe753827d354998d448b4fd6a ] Add support for the third loop filter mode V4L2_MPEG_VIDEO_H264_LOOP_FILTER_MODE_DISABLED_AT_SLICE_BOUNDARY, and fix

[PATCH 4.19 096/313] usb: dwc2: Disable power down feature on Samsung SoCs

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 35a6054132286a4ab92b536595093b82e6bdfcbc ] Power down feature of DWC2 module integrated in Samsung SoCs doesn't work properly or needs some additional handling in PHY or SoC glue

[PATCH 4.19 131/313] lightnvm: pblk: fix resubmission of overwritten write err lbas

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c12fa401ac8c94a74aff68bb5736b3f1dc695fa8 ] Make sure we only look up valid lba addresses on the resubmission path. If an lba is invalidated in the write buffer, that sector will be

[PATCH 4.19 138/313] selftests/bpf: use __bpf_constant_htons in test_prog.c

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a0517a0f7ef23550b4484c37e2b9c2d32abebf64 ] For some reason, my older GCC (< 4.8) isn't smart enough to optimize the !__builtin_constant_p() branch in bpf_htons, I see: error:

[PATCH 4.19 130/313] drm/msm: dpu: Only check flush register against pending flushes

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5f79e03b1f7c1b2cf0019ce6365fe5d52629813d ] There exists a case where a flush of a plane/dma may have been triggered & started from an async commit. If that plane/dma is subsequently

[PATCH 4.19 133/313] i2c-axxia: check for error conditions first

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4f5c85fe3a60ace555d09898166af372547f97fc ] It was observed that when using seqentional mode contrary to the documentation, the SS bit (which is supposed to only be set if

[PATCH 4.19 145/313] mmc: meson-mx-sdio: check devm_kasprintf for failure

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b0d06f1cb0e2079a3c64fb6e27c19d9a55c723a1 ] devm_kasprintf() may return NULL on failure of internal allocation thus the assignments to init.name are not safe if not checked. On

[PATCH 4.19 123/313] sata_rcar: fix deferred probing

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9f83cfdb1ace3ef268ecc6fda50058d2ec37d603 ] The driver overrides the error codes returned by platform_get_irq() to -EINVAL, so if it returns -EPROBE_DEFER, the driver would fail the

[PATCH 4.19 146/313] memstick: Prevent memstick host from getting runtime suspended during card detection

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e03e303edf1c63e6dd455ccd568c74e93ef3ba8c ] We can use MEMSTICK_POWER_{ON,OFF} along with pm_runtime_{get,put} helpers to let memstick host support runtime pm. The rpm count may go

[PATCH 4.19 144/313] mmc: bcm2835: reset host on timeout

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f6000a4eb34e6462bc0dd39809c1bb99f9633269 ] The bcm2835 mmc host tends to lock up for unknown reason so reset it on timeout. The upper mmc block layer tries retransimitting with

[PATCH 4.19 142/313] KVM: PPC: Book3S: Only report KVM_CAP_SPAPR_TCE_VFIO on powernv machines

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 693ac10a88a2219bde553b2e8460dbec97e594e6 ] The kvm capability KVM_CAP_SPAPR_TCE_VFIO is used to indicate the availability of in kernel tce acceleration for vfio. However it is

[PATCH 4.19 147/313] mmc: sdhci-of-esdhc: Fix timeout checks

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ea6d027312111c6d96309ad1a684b33cb37e6764 ] Always check the wait condition before returning timeout. Signed-off-by: Adrian Hunter Reviewed-by: Yangbo Lu Signed-off-by: Ulf

[PATCH] staging: iio: ad5933: move out of staging

Move ad5933 impedance-analyzer driver from staging to mainline. The ad5933 is a high precision impedance converter system solution that combines an on-board frequency generator with an analog-to-digital converter (ADC). This driver was designed to be compatible with both ad5933 and ad5934 chips.

[PATCH 4.19 124/313] clk: imx6sl: ensure MMDC CH0 handshake is bypassed

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0efcc2c0fd2001a83240a8c3d71f67770484917e ] Same as other i.MX6 SoCs, ensure unused MMDC channel's handshake is bypassed, this is to make sure no request signal will be generated

Re: [5.0-rc5 regression] "scsi: kill off the legacy IO path" causes 5 minute delay during boot on Sun Blade 2500

On Mon, 2019-02-11 at 08:28 -0700, Jens Axboe wrote: > On 2/11/19 8:25 AM, James Bottomley wrote: > > On Sun, 2019-02-10 at 09:35 -0700, Jens Axboe wrote: > > > On 2/10/19 9:25 AM, James Bottomley wrote: > > > > On Sun, 2019-02-10 at 09:05 -0700, Jens Axboe wrote: > > > > > On 2/10/19 8:44 AM,

[PATCH 4.19 127/313] OPP: Use opp_table->regulators to verify no regulator case

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 90e3577b5feb42bac1269e16bb3d2bdd8f6df40f ] The value of opp_table->regulator_count is not very consistent right now and it may end up being 0 while we do have a "opp-microvolt"

Re: [PATCH] driver: platform: Add support for GpioInt() ACPI to platform_get_irq()

Hi, On 11-02-19 11:30, Mika Westerberg wrote: Hi, On Thu, Feb 07, 2019 at 12:29:17PM -0800, Dmitry Torokhov wrote: Do you have a suggestion as to how to write ACPI tables to avoid the issue? 1. Allocate new ID and use it (perhaps not the best path). 2. Use GPE(s). Or just solve the

[PATCH 4.19 170/313] perf header: Fix up argument to ctime()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0afcf29bab35d3785204cd9bd51693b231ad7181 ] Reducing this noise when cross building to the Android NDK: util/header.c: In function 'perf_header__fprintf_info':

[PATCH 4.19 169/313] usb: musb: dsps: fix runtime pm for peripheral mode

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 54578ee883e34d2d1c518d48f1c1e2dd3f387188 ] Since the runtime PM support was added in musb, dsps relies on the timer calling otg_timer() to activate the usb subsystem. However the

[PATCH 4.19 164/313] KVM: s390: unregister debug feature on failing arch init

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 308c3e6673b012beecb96ef04cc65f4a0e7cdd99 ] Make sure the debug feature and its allocated resources get released upon unsuccessful architecture initialization. A related indication

[PATCH 4.19 154/313] serial: sh-sci: Fix locking in sci_submit_rx()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dd1f2250da95e87cb3e612858f94b14f99445a7c ] Some callers of sci_submit_rx() hold the port spinlock, others don't. During fallback to PIO, the driver needs to obtain the port

[PATCH 4.19 181/313] scsi: smartpqi: correct host serial num for ssa

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b2346b5030cf9458f30a84028d9fe904b8c942a7 ] Reviewed-by: Scott Benesh Reviewed-by: Ajish Koshy Reviewed-by: Murthy Bhat Reviewed-by: Mahesh Rajashekhara Reviewed-by: Dave Carroll

[PATCH 4.19 155/313] serial: sh-sci: Resume PIO in sci_rx_interrupt() on DMA failure

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 71ab1c0336c71ace5725740f200beca9667a339f ] On (H)SCIF, sci_submit_rx() is called in the receive interrupt handler. Hence if DMA submission fails, the interrupt handler should resume

[PATCH 4.19 158/313] perf dso: Fix unchecked usage of strncpy()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fca5085c15255bbde203b7322c15f07ebb12f63e ] The strncpy() function may leave the destination string buffer unterminated, better use strlcpy() that we have a __weak fallback

[PATCH 4.19 185/313] net: hns3: add max vector number check for pf

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 75edb610860fda65ceedb017fc69afabd2806b8b ] Each pf supports max 64 vectors and 128 tqps. For 2p/4p core scenario, there may be more than 64 cpus online. So the result of min_t(u16,

[PATCH 4.19 160/313] btrfs: use tagged writepage to mitigate livelock of snapshot

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3cd24c698004d2f7668e0eb9fc1f096f533c791b ] Snapshot is expected to be fast. But if there are writers steadily creating dirty pages in our subvolume, the snapshot may take a very

[PATCH 4.19 202/313] fbdev: fbcon: Fix unregister crash when more than one framebuffer

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2122b40580dd9d0620398739c773d07a7b7939d0 ] When unregistering fbdev using unregister_framebuffer(), any bound console will unbind automatically. This is working fine if this is the

[PATCH 4.19 197/313] fbdev: fbmem: behave better with small rotated displays and many CPUs

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f75df8d4b4fabfad7e3cba2debfad12741c6fde7 ] Blitting an image with "negative" offsets is not working since there is no clipping. It hopefully just crashes. For the bootup logo, there

[PATCH 4.19 203/313] powerpc/mm: Fix reporting of kernel execute faults on the 8xx

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ffca395b11c4a5a6df6d6345f794b0e3d578e2d0 ] On the 8xx, no-execute is set via PPP bits in the PTE. Therefore a no-exec fault generates DSISR_PROTFAULT error bits, not

[PATCH 4.19 187/313] iwlwifi: mvm: fix setting HE ppe FW config

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 189b8d441b0f7825f0b4278851c52afaa0515ed2 ] The FW expects to get the ppe value for each NSS-BW pair in the same format as in the he phy capabilities IE, which means that a value of

[PATCH 4.19 198/313] i40e: define proper net_device::neigh_priv_len

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 31389b53b3e0b535867af9090a5d19ec64768d55 ] Out of bound read reported by KASan. i40iw_net_event() reads unconditionally 16 bytes from neigh->primary_key while the memory allocated

Re: possible deadlock in pipe_lock (2)

On Mon, Feb 11, 2019 at 4:07 PM Amir Goldstein wrote: > > On Mon, Feb 11, 2019 at 4:33 PM Miklos Szeredi wrote: > > > > On Mon, Feb 11, 2019 at 2:08 PM Amir Goldstein wrote: > > > > > > On Mon, Feb 11, 2019 at 2:37 PM Miklos Szeredi wrote: > > > > > > > > On Mon, Feb 11, 2019 at 1:06 PM Miklos

Re: [PATCH] staging: android: vsoc: Remove VSOC_WAIT_FOR_INCOMING_INTERRUPT

On Mon, Feb 11, 2019 at 08:56:02PM +0530, Souptick Joarder wrote: > As mentioned in TODO list, Removed VSOC_WAIT_FOR_INCOMING_INTERRUPT > ioctl. This functionality has been superseded by the futex and is > there for legacy reasons. > > Signed-off-by: Souptick Joarder > --- >

Re: [PATCH] doc:dmaengine: clarify DMA desc. pointer after submission

On Fri, 8 Feb 2019 16:30:38 +0100 Federico Vaga wrote: > It clarifies that the DMA description pointer returned by > `dmaengine_prep_*` function should not be used after submission. > > Signed-off-by: Federico Vaga > --- > Documentation/driver-api/dmaengine/client.rst | 7 +++ > 1 file

[PATCH 4.19 205/313] pinctrl: meson: meson8b: fix the GPIO function for the GPIOAO pins

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2b745ac3cceb8fc1d9985990c8241a821ea97e53 ] The GPIOAO pins (as well as the two exotic GPIO_BSD_EN and GPIO_TEST_N) only belong to the pin controller in the AO domain. With the

[PATCH 4.19 207/313] powerpc/fadump: Do not allow hot-remove memory from fadump reserved area.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0db6896ff6332ba694f1e61b93ae3b2640317633 ] For fadump to work successfully there should not be any holes in reserved memory ranges where kernel has asked firmware to move the

[PATCH 4.19 210/313] perf build: Dont unconditionally link the libbfd feature test to -liberty and -lz

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 14541b1e7e723859ff2c75c6fc10cdbbec6b8c34 ] Current libbfd feature test unconditionally links against -liberty and -lz. While it's required on some systems (e.g. opensuse), it's

[PATCH 4.19 189/313] mlx5: update timecounter at least twice per counter overflow

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5d8678365c90b9ce1fd2243ff5ea562609f6cec1 ] The timecounter needs to be updated at least once in half of the cyclecounter interval to prevent timecounter_cyc2time() interpreting a

[PATCH 4.19 214/313] crypto: ux500 - Use proper enum in cryp_set_dma_transfer

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9d880c5945c748d8edcac30965f3349a602158c4 ] Clang warns when one enumerated type is implicitly converted to another: drivers/crypto/ux500/cryp/cryp_core.c:559:5: warning: implicit

[PATCH 4.19 218/313] f2fs: fix use-after-free issue when accessing sbi->stat_info

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 60aa4d5536ab7fe32433ca1173bd9d6633851f27 ] iput() on sbi->node_inode can update sbi->stat_info in the below context, if the f2fs_write_checkpoint() has failed with error.

[PATCH 4.19 191/313] drbd: disconnect, if the wrong UUIDs are attached on a connected peer

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b17b59602b6dcf8f97a7dc7bc489a48388d7063a ] With "on-no-data-accessible suspend-io", DRBD requires the next attach or connect to be to the very same data generation uuid tag it lost

[PATCH 4.19 190/313] drbd: narrow rcu_read_lock in drbd_sync_handshake

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d29e89e34952a9ad02c77109c71a80043544296e ] So far there was the possibility that we called genlmsg_new(GFP_NOIO)/mutex_lock() while holding an rcu_read_lock(). This included cases

[PATCH 4.19 195/313] video: clps711x-fb: release disp device node in probe()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fdac751355cd76e049f628afe6acb8ff4b1399f7 ] clps711x_fb_probe() increments refcnt of disp device node by of_parse_phandle() and leaves it undecremented on both successful and error

[PATCH 4.19 221/313] f2fs: fix sbi->extent_list corruption issue

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e4589fa545e0020dbbc3c9bde35f35f949901392 ] When there is a failure in f2fs_fill_super() after/during the recovery of fsync'd nodes, it frees the current sbi and retries again. This

[PATCH 4.19 229/313] zram: fix lockdep warning of free block handling

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3c9959e025472122a61faebb208525cf26b305d1 ] Patch series "zram idle page writeback", v3. Inherently, swap device has many idle pages which are rare touched since it was allocated.

[PATCH 4.19 236/313] PCI: imx: Enable MSI from downstream components

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 75cb8d20c112aba70f23d98e3f8d0a38ace16006 ] The MSI Enable bit in the MSI Capability (PCIe r4.0, sec 7.7.1.2) controls whether a Function can request service using MSI. i.MX6 Root

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