2020-03-24 13:30:58

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 000/119] 5.5.12-rc1 review

This is the start of the stable review cycle for the 5.5.12 release.
There are 119 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.

Responses should be made by Thu, 26 Mar 2020 13:06:42 +0000.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.5.12-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.5.y
and the diffstat can be found below.

thanks,

greg k-h

-------------
Pseudo-Shortlog of commits:

Greg Kroah-Hartman <[email protected]>
Linux 5.5.12-rc1

Masahiro Yamada <[email protected]>
int128: fix __uint128_t compiler test in Kconfig

Masahiro Yamada <[email protected]>
kconfig: introduce m32-flag and m64-flag

Johan Hovold <[email protected]>
staging: greybus: loopback_test: fix potential path truncations

Johan Hovold <[email protected]>
staging: greybus: loopback_test: fix potential path truncation

Matt Roper <[email protected]>
drm/i915: Handle all MCR ranges

Chris Wilson <[email protected]>
drm/i915/execlists: Track active elements during dequeue

Jernej Skrabec <[email protected]>
drm/bridge: dw-hdmi: fix AVI frame colorimetry

Caz Yokoyama <[email protected]>
Revert "drm/i915/tgl: Add extra hdc flush workaround"

Filipe Manana <[email protected]>
btrfs: fix removal of raid[56|1c34} incompat flags after removing block group

Xiao Yang <[email protected]>
modpost: Get proper section index by get_secindex() instead of st_shndx

Sagi Grimberg <[email protected]>
nvmet-tcp: set MSG_MORE only if we actually have more to send

Cristian Marussi <[email protected]>
arm64: smp: fix crash_smp_send_stop() behaviour

Cristian Marussi <[email protected]>
arm64: smp: fix smp_send_stop() behaviour

Dan Carpenter <[email protected]>
thunderbolt: Fix error code in tb_port_is_width_supported()

Kai-Heng Feng <[email protected]>
ALSA: hda/realtek: Fix pop noise on ALC225

Thomas Gleixner <[email protected]>
futex: Unbreak futex hashing

Peter Zijlstra <[email protected]>
futex: Fix inode life-time issue

Pavel Begunkov <[email protected]>
io_uring: NULL-deref for IOSQE_{ASYNC,DRAIN}

Joerg Roedel <[email protected]>
x86/mm: split vmalloc_sync_all()

Qian Cai <[email protected]>
page-flags: fix a crash at SetPageError(THP_SWAP)

Vlastimil Babka <[email protected]>
mm, slub: prevent kmalloc_node crashes and memory leaks

Linus Torvalds <[email protected]>
mm: slub: be more careful about the double cmpxchg of freelist

Roman Penyaev <[email protected]>
epoll: fix possible lost wakeup on epoll_ctl() path

Michal Hocko <[email protected]>
mm: do not allow MADV_PAGEOUT for CoW pages

Baoquan He <[email protected]>
mm/hotplug: fix hot remove failure in SPARSEMEM|!VMEMMAP case

Chris Down <[email protected]>
mm, memcg: throttle allocators based on ancestral memory.high

Chris Down <[email protected]>
mm, memcg: fix corruption on 64-bit divisor in memory.high throttling

Chunguang Xu <[email protected]>
memcg: fix NULL pointer dereference in __mem_cgroup_usage_unregister_event

Alexander Shishkin <[email protected]>
stm class: sys-t: Fix the use of time_after()

Qiujun Huang <[email protected]>
drm/lease: fix WARNING in idr_destroy

Tom St Denis <[email protected]>
drm/amd/amdgpu: Fix GPR read from debugfs (v2)

Filipe Manana <[email protected]>
btrfs: fix log context list corruption after rename whiteout error

Steven Rostedt (VMware) <[email protected]>
xhci: Do not open code __print_symbolic() in xhci trace events

Vincenzo Frascino <[email protected]>
arm64: compat: Fix syscall number of compat_clock_getres

Corentin Labbe <[email protected]>
rtc: max8907: add missing select REGMAP_IRQ

Jessica Yu <[email protected]>
modpost: move the namespace field in Module.symvers last

Alexander Shishkin <[email protected]>
intel_th: pci: Add Elkhart Lake CPU support

Alexander Shishkin <[email protected]>
intel_th: Fix user-visible error codes

Alexander Shishkin <[email protected]>
intel_th: msu: Fix the unexpected state warning

Samuel Thibault <[email protected]>
staging/speakup: fix get_word non-space look-ahead

Johan Hovold <[email protected]>
staging: greybus: loopback_test: fix poll-mask build breakage

Michael Straube <[email protected]>
staging: rtl8188eu: Add device id for MERCUSYS MW150US v2

Nathan Chancellor <[email protected]>
kbuild: Disable -Wpointer-to-enum-cast

Murphy Zhou <[email protected]>
CIFS: fiemap: do not return EINVAL if get nothing

Hans de Goede <[email protected]>
mmc: sdhci-acpi: Disable write protect detection on Acer Aspire Switch 10 (SW5-012)

Hans de Goede <[email protected]>
mmc: sdhci-acpi: Switch signal voltage back to 3.3V on suspend on external microSD on Lenovo Miix 320

Masahiro Yamada <[email protected]>
mmc: sdhci-cadence: set SDHCI_QUIRK2_PRESET_VALUE_BROKEN for UniPhier

Michał Mirosław <[email protected]>
mmc: sdhci-of-at91: fix cd-gpios for SAMA5D2

Ricky Wu <[email protected]>
mmc: rtsx_pci: Fix support for speed-modes that relies on tuning

Tomas Novotny <[email protected]>
iio: light: vcnl4000: update sampling periods for vcnl4040

Tomas Novotny <[email protected]>
iio: light: vcnl4000: update sampling periods for vcnl4200

Eugen Hristev <[email protected]>
iio: adc: at91-sama5d2_adc: fix differential channels in triggered mode

Olivier Moysan <[email protected]>
iio: adc: stm32-dfsdm: fix sleep in atomic context

Stephan Gerhold <[email protected]>
iio: magnetometer: ak8974: Fix negative raw values in sysfs

Alexandru Tachici <[email protected]>
iio: accel: adxl372: Set iio_chan BE

Fabrice Gasnier <[email protected]>
iio: trigger: stm32-timer: disable master mode when stopping

Wen-chien Jesse Sung <[email protected]>
iio: st_sensors: remap SMO8840 to LIS2DH12

Petr Štetiar <[email protected]>
iio: chemical: sps30: fix missing triggered buffer dependency

Eric Biggers <[email protected]>
tty: fix compat TIOCGSERIAL checking wrong function ptr

Eric Biggers <[email protected]>
tty: fix compat TIOCGSERIAL leaking uninitialized memory

Takashi Iwai <[email protected]>
ALSA: pcm: oss: Remove WARNING from snd_pcm_plug_alloc() checks

Takashi Iwai <[email protected]>
ALSA: pcm: oss: Avoid plugin buffer overflow

Takashi Iwai <[email protected]>
ALSA: seq: oss: Fix running status after receiving sysex

Takashi Iwai <[email protected]>
ALSA: seq: virmidi: Fix running status after receiving sysex

Jian-Hong Pan <[email protected]>
ALSA: hda/realtek - Enable the headset of Acer N50-600 with ALC662

Jian-Hong Pan <[email protected]>
ALSA: hda/realtek - Enable headset mic of Acer X2660G with ALC662

Takashi Iwai <[email protected]>
ALSA: line6: Fix endless MIDI read loop

Anthony Mallet <[email protected]>
USB: cdc-acm: fix rounding error in TIOCSSERIAL

Anthony Mallet <[email protected]>
USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL

Heikki Krogerus <[email protected]>
usb: typec: ucsi: displayport: Fix a potential race during registration

Heikki Krogerus <[email protected]>
usb: typec: ucsi: displayport: Fix NULL pointer dereference

Alberto Mattea <[email protected]>
usb: xhci: apply XHCI_SUSPEND_DELAY to AMD XHCI controller 1022:145c

Scott Chen <[email protected]>
USB: serial: pl2303: add device-id for HP LD381

Ran Wang <[email protected]>
usb: host: xhci-plat: add a shutdown

Peter Chen <[email protected]>
usb: chipidea: udc: fix sleeping function called from invalid context

Daniele Palmas <[email protected]>
USB: serial: option: add ME910G1 ECM composition 0x110b

Hans de Goede <[email protected]>
usb: quirks: add NO_LPM quirk for RTL8153 based ethernet adapters

Kai-Heng Feng <[email protected]>
USB: Disable LPM on WD19's Realtek Hub

Sasha Levin <[email protected]>
Revert "drm/fbdev: Fallback to non tiled mode if all tiles not present"

Christian Brauner <[email protected]>
binderfs: use refcount for binder control devices too

Pavel Begunkov <[email protected]>
io_uring: fix lockup with timeouts

Jonathan Neuschäfer <[email protected]>
parse-maintainers: Mark as executable

Tycho Andersen <[email protected]>
riscv: fix seccomp reject syscall code path

Dongli Zhang <[email protected]>
xenbus: req->err should be updated before req->state

Dongli Zhang <[email protected]>
xenbus: req->body should be updated before req->state

Josip Pavic <[email protected]>
drm/amd/display: fix dcc swath size calculations on dcn1

Bhawanpreet Lakha <[email protected]>
drm/amd/display: Clear link settings on MST disable connector

Yintian Tao <[email protected]>
drm/amdgpu: clean wptr on wb when gpu recovery

Alexandre Ghiti <[email protected]>
riscv: Fix range looking for kernel image memblock

Damien Le Moal <[email protected]>
riscv: Force flat memory model with no-mmu

Aaro Koskinen <[email protected]>
spi: spi_register_controller(): free bus id on error paths

Olivier Moysan <[email protected]>
ASoC: stm32: sai: manage rebind issue

Vincent Chen <[email protected]>
riscv: avoid the PIC offset of static percpu data in module beyond 2G limits

Mike Snitzer <[email protected]>
dm integrity: use dm_bio_record and dm_bio_restore

Mike Snitzer <[email protected]>
dm bio record: save/restore bi_end_io and bi_integrity

Daniel Axtens <[email protected]>
altera-stapl: altera_get_note: prevent write beyond end of 'key'

Stefan Wahren <[email protected]>
ARM: bcm2835_defconfig: Explicitly restore CONFIG_DEBUG_FS

Pavel Begunkov <[email protected]>
io-wq: fix IO_WQ_WORK_NO_CANCEL cancellation

luanshi <[email protected]>
drivers/perf: arm_pmu_acpi: Fix incorrect checking of gicc pointer

Joakim Zhang <[email protected]>
drivers/perf: fsl_imx8_ddr: Correct the CLEAR bit definition

Marek Szyprowski <[email protected]>
drm/exynos: hdmi: don't leak enable HDMI_EN regulator if probe fails

Marek Szyprowski <[email protected]>
drm/exynos: dsi: fix workaround for the legacy clock name

Marek Szyprowski <[email protected]>
drm/exynos: dsi: propagate error value and silence meaningless warning

Stefan Wahren <[email protected]>
ARM: dts: bcm283x: Add missing properties to the PWR LED

Thommy Jakobsson <[email protected]>
spi/zynqmp: remove entry that causes a cs glitch

Evan Green <[email protected]>
spi: pxa2xx: Add CS control clock quirk

Kishon Vijay Abraham I <[email protected]>
ARM: dts: dra7: Add "dma-ranges" property to PCIe RC DT nodes

Steve French <[email protected]>
cifs: add missing mount option to /proc/mounts

Paulo Alcantara (SUSE) <[email protected]>
cifs: fix potential mismatch of UNC paths

Naveen N. Rao <[email protected]>
powerpc: Include .BTF section

Yuji Sasaki <[email protected]>
spi: qup: call spi_qup_pm_resume_runtime before suspending

Grygorii Strashko <[email protected]>
ARM: dts: dra7-l4: mark timer13-16 as pwm capable

Grygorii Strashko <[email protected]>
phy: ti: gmii-sel: do not fail in case of gmii

Grygorii Strashko <[email protected]>
phy: ti: gmii-sel: fix set of copy-paste errors

Sean Paul <[email protected]>
drm/mediatek: Ensure the cursor plane is on top of other overlays

Evan Benn <[email protected]>
drm/mediatek: Find the cursor plane instead of hard coding it

Vignesh Raghavendra <[email protected]>
spi: spi-omap2-mcspi: Support probe deferral for DMA channels

Linus Torvalds <[email protected]>
locks: reinstate locks_delete_block optimization

yangerkun <[email protected]>
locks: fix a potential use-after-free problem when wakeup a waiter


-------------

Diffstat:

Documentation/kbuild/modules.rst | 4 +-
Makefile | 4 +-
arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 2 +
arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts | 2 +
arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts | 2 +
arch/arm/boot/dts/dra7-l4.dtsi | 4 +
arch/arm/boot/dts/dra7.dtsi | 2 +
arch/arm/configs/bcm2835_defconfig | 1 +
arch/arm64/include/asm/unistd.h | 2 +-
arch/arm64/kernel/smp.c | 25 ++++-
arch/powerpc/kernel/vmlinux.lds.S | 6 ++
arch/riscv/Kconfig | 1 +
arch/riscv/include/asm/syscall.h | 7 --
arch/riscv/kernel/entry.S | 11 +--
arch/riscv/kernel/module.c | 16 ++++
arch/riscv/kernel/ptrace.c | 11 +--
arch/riscv/mm/init.c | 2 +-
arch/x86/mm/fault.c | 26 +++++-
drivers/acpi/apei/ghes.c | 2 +-
drivers/android/binderfs.c | 1 +
drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c | 6 +-
drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c | 1 +
drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 1 +
.../amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 1 +
.../gpu/drm/amd/display/dc/dcn10/dcn10_hubbub.c | 4 +-
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 46 +++++----
drivers/gpu/drm/drm_client_modeset.c | 72 --------------
drivers/gpu/drm/drm_lease.c | 3 +-
drivers/gpu/drm/exynos/exynos_drm_dsi.c | 12 ++-
drivers/gpu/drm/exynos/exynos_hdmi.c | 22 +++--
drivers/gpu/drm/i915/gt/intel_lrc.c | 52 +++--------
drivers/gpu/drm/i915/gt/intel_workarounds.c | 25 ++++-
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 26 ++++--
drivers/hwtracing/intel_th/msu.c | 13 +--
drivers/hwtracing/intel_th/pci.c | 5 +
drivers/hwtracing/stm/p_sys-t.c | 6 +-
drivers/iio/accel/adxl372.c | 1 +
drivers/iio/accel/st_accel_i2c.c | 2 +-
drivers/iio/adc/at91-sama5d2_adc.c | 15 +++
drivers/iio/adc/stm32-dfsdm-adc.c | 43 ++-------
drivers/iio/chemical/Kconfig | 2 +
drivers/iio/light/vcnl4000.c | 15 +--
drivers/iio/magnetometer/ak8974.c | 2 +-
drivers/iio/trigger/stm32-timer-trigger.c | 11 ++-
drivers/md/dm-bio-record.h | 15 +++
drivers/md/dm-integrity.c | 32 ++-----
drivers/misc/altera-stapl/altera.c | 12 +--
drivers/misc/cardreader/rts5227.c | 2 +-
drivers/misc/cardreader/rts5249.c | 2 +
drivers/misc/cardreader/rts5260.c | 2 +-
drivers/misc/cardreader/rts5261.c | 2 +-
drivers/mmc/host/rtsx_pci_sdmmc.c | 13 ++-
drivers/mmc/host/sdhci-acpi.c | 84 ++++++++++++++++-
drivers/mmc/host/sdhci-cadence.c | 18 +++-
drivers/mmc/host/sdhci-of-at91.c | 8 +-
drivers/nvme/target/tcp.c | 12 ++-
drivers/perf/arm_pmu_acpi.c | 7 +-
drivers/perf/fsl_imx8_ddr_perf.c | 10 +-
drivers/phy/ti/phy-gmii-sel.c | 10 +-
drivers/rtc/Kconfig | 1 +
drivers/spi/spi-omap2-mcspi.c | 77 ++++++++-------
drivers/spi/spi-pxa2xx.c | 23 +++++
drivers/spi/spi-qup.c | 11 ++-
drivers/spi/spi-zynqmp-gqspi.c | 3 -
drivers/spi/spi.c | 32 +++----
drivers/staging/greybus/tools/loopback_test.c | 21 +++--
drivers/staging/rtl8188eu/os_dep/usb_intf.c | 1 +
drivers/staging/speakup/main.c | 2 +-
drivers/thunderbolt/switch.c | 2 +-
drivers/tty/tty_io.c | 6 +-
drivers/usb/chipidea/udc.c | 7 +-
drivers/usb/class/cdc-acm.c | 34 ++++---
drivers/usb/core/quirks.c | 6 ++
drivers/usb/host/xhci-pci.c | 3 +-
drivers/usb/host/xhci-plat.c | 1 +
drivers/usb/host/xhci-trace.h | 23 ++---
drivers/usb/serial/option.c | 2 +
drivers/usb/serial/pl2303.c | 1 +
drivers/usb/serial/pl2303.h | 1 +
drivers/usb/typec/ucsi/displayport.c | 12 ++-
drivers/xen/xenbus/xenbus_comms.c | 4 +
drivers/xen/xenbus/xenbus_xs.c | 9 +-
fs/btrfs/block-group.c | 4 +-
fs/btrfs/inode.c | 4 +
fs/cifs/cifs_dfs_ref.c | 2 +
fs/cifs/cifsfs.c | 2 +
fs/cifs/file.c | 3 +-
fs/cifs/smb2ops.c | 2 +-
fs/eventpoll.c | 8 +-
fs/inode.c | 1 +
fs/io-wq.c | 20 ++--
fs/io_uring.c | 9 ++
fs/locks.c | 60 ++++++++----
include/linux/fs.h | 1 +
include/linux/futex.h | 17 ++--
include/linux/page-flags.h | 2 +-
include/linux/vmalloc.h | 5 +-
init/Kconfig | 3 +-
kernel/futex.c | 93 +++++++++++--------
kernel/notifier.c | 2 +-
mm/madvise.c | 12 ++-
mm/memcontrol.c | 103 +++++++++++++--------
mm/nommu.c | 10 +-
mm/slub.c | 32 ++++---
mm/sparse.c | 8 +-
mm/vmalloc.c | 11 ++-
scripts/Kconfig.include | 7 ++
scripts/Makefile.extrawarn | 1 +
scripts/export_report.pl | 2 +-
scripts/mod/modpost.c | 27 +++---
scripts/parse-maintainers.pl | 0
sound/core/oss/pcm_plugin.c | 12 ++-
sound/core/seq/oss/seq_oss_midi.c | 1 +
sound/core/seq/seq_virmidi.c | 1 +
sound/pci/hda/patch_realtek.c | 25 +++++
sound/soc/stm/stm32_sai_sub.c | 18 ++--
sound/usb/line6/driver.c | 2 +-
sound/usb/line6/midibuf.c | 2 +-
118 files changed, 945 insertions(+), 595 deletions(-)



2020-03-24 13:31:04

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 007/119] phy: ti: gmii-sel: do not fail in case of gmii

From: Grygorii Strashko <[email protected]>

[ Upstream commit 58aa7729310db04ffcc022c98002dd8fcb486c58 ]

The "gmii" PHY interface mode is supported on TI AM335x/437x/5xx SoCs, so
don't fail if it's selected.

Signed-off-by: Grygorii Strashko <[email protected]>
Signed-off-by: Kishon Vijay Abraham I <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
drivers/phy/ti/phy-gmii-sel.c | 1 +
1 file changed, 1 insertion(+)

diff --git a/drivers/phy/ti/phy-gmii-sel.c b/drivers/phy/ti/phy-gmii-sel.c
index e998e9cd8d1f8..1c536fc03c83c 100644
--- a/drivers/phy/ti/phy-gmii-sel.c
+++ b/drivers/phy/ti/phy-gmii-sel.c
@@ -80,6 +80,7 @@ static int phy_gmii_sel_mode(struct phy *phy, enum phy_mode mode, int submode)
break;

case PHY_INTERFACE_MODE_MII:
+ case PHY_INTERFACE_MODE_GMII:
gmii_sel_mode = AM33XX_GMII_SEL_MODE_MII;
break;

--
2.20.1



2020-03-24 13:31:09

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 006/119] phy: ti: gmii-sel: fix set of copy-paste errors

From: Grygorii Strashko <[email protected]>

[ Upstream commit eefed634eb61e4094b9fb8183cb8d43b26838517 ]

- under PHY_INTERFACE_MODE_MII the 'mode' func parameter is assigned
instead of 'gmii_sel_mode' and it's working only because the default value
'gmii_sel_mode' is set to 0.

- console outputs use 'rgmii_id' and 'mode' values to print PHY mode
instead of using 'submode' value which is representing PHY interface mode
now.

This patch fixes above two cases.

Signed-off-by: Grygorii Strashko <[email protected]>
Signed-off-by: Kishon Vijay Abraham I <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
drivers/phy/ti/phy-gmii-sel.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/drivers/phy/ti/phy-gmii-sel.c b/drivers/phy/ti/phy-gmii-sel.c
index a28bd15297f53..e998e9cd8d1f8 100644
--- a/drivers/phy/ti/phy-gmii-sel.c
+++ b/drivers/phy/ti/phy-gmii-sel.c
@@ -80,20 +80,19 @@ static int phy_gmii_sel_mode(struct phy *phy, enum phy_mode mode, int submode)
break;

case PHY_INTERFACE_MODE_MII:
- mode = AM33XX_GMII_SEL_MODE_MII;
+ gmii_sel_mode = AM33XX_GMII_SEL_MODE_MII;
break;

default:
- dev_warn(dev,
- "port%u: unsupported mode: \"%s\". Defaulting to MII.\n",
- if_phy->id, phy_modes(rgmii_id));
+ dev_warn(dev, "port%u: unsupported mode: \"%s\"\n",
+ if_phy->id, phy_modes(submode));
return -EINVAL;
}

if_phy->phy_if_mode = submode;

dev_dbg(dev, "%s id:%u mode:%u rgmii_id:%d rmii_clk_ext:%d\n",
- __func__, if_phy->id, mode, rgmii_id,
+ __func__, if_phy->id, submode, rgmii_id,
if_phy->rmii_clock_external);

regfield = if_phy->fields[PHY_GMII_SEL_PORT_MODE];
--
2.20.1



2020-03-24 13:31:36

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 063/119] iio: st_sensors: remap SMO8840 to LIS2DH12

From: Wen-chien Jesse Sung <[email protected]>

commit e43d110cdc206b6df4dd438cd10c81d1da910aad upstream.

According to ST, the HID is for LIS2DH12.

Fixes: 3d56e19815b3 ("iio: accel: st_accel: Add support for the SMO8840 ACPI id")
Signed-off-by: Wen-chien Jesse Sung <[email protected]>
Tested-by: Hans de Goede <[email protected]>
Reviewed-by: Hans de Goede <[email protected]>
Cc: <[email protected]>
Signed-off-by: Jonathan Cameron <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
drivers/iio/accel/st_accel_i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/iio/accel/st_accel_i2c.c
+++ b/drivers/iio/accel/st_accel_i2c.c
@@ -114,7 +114,7 @@ MODULE_DEVICE_TABLE(of, st_accel_of_matc

#ifdef CONFIG_ACPI
static const struct acpi_device_id st_accel_acpi_match[] = {
- {"SMO8840", (kernel_ulong_t)LNG2DM_ACCEL_DEV_NAME},
+ {"SMO8840", (kernel_ulong_t)LIS2DH12_ACCEL_DEV_NAME},
{"SMO8A90", (kernel_ulong_t)LNG2DM_ACCEL_DEV_NAME},
{ },
};


2020-03-24 13:31:40

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 005/119] drm/mediatek: Ensure the cursor plane is on top of other overlays

From: Sean Paul <[email protected]>

[ Upstream commit 26d696192aa5f4fe9119d6d23f90ed535053abca ]

Currently the cursor is placed on the first overlay plane, which means
it will be at the bottom of the stack when the hw does the compositing
with anything other than primary plane. Since mtk doesn't support plane
zpos, change the cursor location to the top-most plane.

Signed-off-by: Sean Paul <[email protected]>
Signed-off-by: CK Hu <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/mediatek/mtk_drm_crtc.c b/drivers/gpu/drm/mediatek/mtk_drm_crtc.c
index 7104504babde0..1d46fbe9e07c6 100644
--- a/drivers/gpu/drm/mediatek/mtk_drm_crtc.c
+++ b/drivers/gpu/drm/mediatek/mtk_drm_crtc.c
@@ -606,11 +606,12 @@ static int mtk_drm_crtc_num_comp_planes(struct mtk_drm_crtc *mtk_crtc,
}

static inline
-enum drm_plane_type mtk_drm_crtc_plane_type(unsigned int plane_idx)
+enum drm_plane_type mtk_drm_crtc_plane_type(unsigned int plane_idx,
+ unsigned int num_planes)
{
if (plane_idx == 0)
return DRM_PLANE_TYPE_PRIMARY;
- else if (plane_idx == 1)
+ else if (plane_idx == (num_planes - 1))
return DRM_PLANE_TYPE_CURSOR;
else
return DRM_PLANE_TYPE_OVERLAY;
@@ -629,7 +630,8 @@ static int mtk_drm_crtc_init_comp_planes(struct drm_device *drm_dev,
ret = mtk_plane_init(drm_dev,
&mtk_crtc->planes[mtk_crtc->layer_nr],
BIT(pipe),
- mtk_drm_crtc_plane_type(mtk_crtc->layer_nr),
+ mtk_drm_crtc_plane_type(mtk_crtc->layer_nr,
+ num_planes),
mtk_ddp_comp_supported_rotations(comp));
if (ret)
return ret;
--
2.20.1



2020-03-24 13:31:52

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 051/119] USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL

From: Anthony Mallet <[email protected]>

commit 633e2b2ded739a34bd0fb1d8b5b871f7e489ea29 upstream.

close_delay and closing_wait are specified in hundredth of a second but stored
internally in jiffies. Use the jiffies_to_msecs() and msecs_to_jiffies()
functions to convert from each other.

Signed-off-by: Anthony Mallet <[email protected]>
Cc: stable <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
drivers/usb/class/cdc-acm.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)

--- a/drivers/usb/class/cdc-acm.c
+++ b/drivers/usb/class/cdc-acm.c
@@ -896,10 +896,10 @@ static int get_serial_info(struct tty_st

ss->xmit_fifo_size = acm->writesize;
ss->baud_base = le32_to_cpu(acm->line.dwDTERate);
- ss->close_delay = acm->port.close_delay / 10;
+ ss->close_delay = jiffies_to_msecs(acm->port.close_delay) / 10;
ss->closing_wait = acm->port.closing_wait == ASYNC_CLOSING_WAIT_NONE ?
ASYNC_CLOSING_WAIT_NONE :
- acm->port.closing_wait / 10;
+ jiffies_to_msecs(acm->port.closing_wait) / 10;
return 0;
}

@@ -909,9 +909,10 @@ static int set_serial_info(struct tty_st
unsigned int closing_wait, close_delay;
int retval = 0;

- close_delay = ss->close_delay * 10;
+ close_delay = msecs_to_jiffies(ss->close_delay * 10);
closing_wait = ss->closing_wait == ASYNC_CLOSING_WAIT_NONE ?
- ASYNC_CLOSING_WAIT_NONE : ss->closing_wait * 10;
+ ASYNC_CLOSING_WAIT_NONE :
+ msecs_to_jiffies(ss->closing_wait * 10);

mutex_lock(&acm->port.mutex);



2020-03-24 13:32:12

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 003/119] spi: spi-omap2-mcspi: Support probe deferral for DMA channels

From: Vignesh Raghavendra <[email protected]>

[ Upstream commit 32f2fc5dc3992b4b60cc6b1a6a31be605cc9c3a2 ]

dma_request_channel() can return -EPROBE_DEFER, if DMA driver is not
ready. Currently driver just falls back to PIO mode on probe deferral.
Fix this by requesting all required channels during probe and
propagating EPROBE_DEFER error code.

Signed-off-by: Vignesh Raghavendra <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Mark Brown <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
drivers/spi/spi-omap2-mcspi.c | 77 ++++++++++++++++++++----------------------
1 file changed, 38 insertions(+), 39 deletions(-)

--- a/drivers/spi/spi-omap2-mcspi.c
+++ b/drivers/spi/spi-omap2-mcspi.c
@@ -974,20 +974,12 @@ static int omap2_mcspi_setup_transfer(st
* Note that we currently allow DMA only if we get a channel
* for both rx and tx. Otherwise we'll do PIO for both rx and tx.
*/
-static int omap2_mcspi_request_dma(struct spi_device *spi)
+static int omap2_mcspi_request_dma(struct omap2_mcspi *mcspi,
+ struct omap2_mcspi_dma *mcspi_dma)
{
- struct spi_master *master = spi->master;
- struct omap2_mcspi *mcspi;
- struct omap2_mcspi_dma *mcspi_dma;
int ret = 0;

- mcspi = spi_master_get_devdata(master);
- mcspi_dma = mcspi->dma_channels + spi->chip_select;
-
- init_completion(&mcspi_dma->dma_rx_completion);
- init_completion(&mcspi_dma->dma_tx_completion);
-
- mcspi_dma->dma_rx = dma_request_chan(&master->dev,
+ mcspi_dma->dma_rx = dma_request_chan(mcspi->dev,
mcspi_dma->dma_rx_ch_name);
if (IS_ERR(mcspi_dma->dma_rx)) {
ret = PTR_ERR(mcspi_dma->dma_rx);
@@ -995,7 +987,7 @@ static int omap2_mcspi_request_dma(struc
goto no_dma;
}

- mcspi_dma->dma_tx = dma_request_chan(&master->dev,
+ mcspi_dma->dma_tx = dma_request_chan(mcspi->dev,
mcspi_dma->dma_tx_ch_name);
if (IS_ERR(mcspi_dma->dma_tx)) {
ret = PTR_ERR(mcspi_dma->dma_tx);
@@ -1004,20 +996,40 @@ static int omap2_mcspi_request_dma(struc
mcspi_dma->dma_rx = NULL;
}

+ init_completion(&mcspi_dma->dma_rx_completion);
+ init_completion(&mcspi_dma->dma_tx_completion);
+
no_dma:
return ret;
}

+static void omap2_mcspi_release_dma(struct spi_master *master)
+{
+ struct omap2_mcspi *mcspi = spi_master_get_devdata(master);
+ struct omap2_mcspi_dma *mcspi_dma;
+ int i;
+
+ for (i = 0; i < master->num_chipselect; i++) {
+ mcspi_dma = &mcspi->dma_channels[i];
+
+ if (mcspi_dma->dma_rx) {
+ dma_release_channel(mcspi_dma->dma_rx);
+ mcspi_dma->dma_rx = NULL;
+ }
+ if (mcspi_dma->dma_tx) {
+ dma_release_channel(mcspi_dma->dma_tx);
+ mcspi_dma->dma_tx = NULL;
+ }
+ }
+}
+
static int omap2_mcspi_setup(struct spi_device *spi)
{
int ret;
struct omap2_mcspi *mcspi = spi_master_get_devdata(spi->master);
struct omap2_mcspi_regs *ctx = &mcspi->ctx;
- struct omap2_mcspi_dma *mcspi_dma;
struct omap2_mcspi_cs *cs = spi->controller_state;

- mcspi_dma = &mcspi->dma_channels[spi->chip_select];
-
if (!cs) {
cs = kzalloc(sizeof *cs, GFP_KERNEL);
if (!cs)
@@ -1042,13 +1054,6 @@ static int omap2_mcspi_setup(struct spi_
}
}

- if (!mcspi_dma->dma_rx || !mcspi_dma->dma_tx) {
- ret = omap2_mcspi_request_dma(spi);
- if (ret)
- dev_warn(&spi->dev, "not using DMA for McSPI (%d)\n",
- ret);
- }
-
ret = pm_runtime_get_sync(mcspi->dev);
if (ret < 0) {
pm_runtime_put_noidle(mcspi->dev);
@@ -1065,12 +1070,8 @@ static int omap2_mcspi_setup(struct spi_

static void omap2_mcspi_cleanup(struct spi_device *spi)
{
- struct omap2_mcspi *mcspi;
- struct omap2_mcspi_dma *mcspi_dma;
struct omap2_mcspi_cs *cs;

- mcspi = spi_master_get_devdata(spi->master);
-
if (spi->controller_state) {
/* Unlink controller state from context save list */
cs = spi->controller_state;
@@ -1079,19 +1080,6 @@ static void omap2_mcspi_cleanup(struct s
kfree(cs);
}

- if (spi->chip_select < spi->master->num_chipselect) {
- mcspi_dma = &mcspi->dma_channels[spi->chip_select];
-
- if (mcspi_dma->dma_rx) {
- dma_release_channel(mcspi_dma->dma_rx);
- mcspi_dma->dma_rx = NULL;
- }
- if (mcspi_dma->dma_tx) {
- dma_release_channel(mcspi_dma->dma_tx);
- mcspi_dma->dma_tx = NULL;
- }
- }
-
if (gpio_is_valid(spi->cs_gpio))
gpio_free(spi->cs_gpio);
}
@@ -1302,6 +1290,9 @@ static bool omap2_mcspi_can_dma(struct s
if (spi_controller_is_slave(master))
return true;

+ master->dma_rx = mcspi_dma->dma_rx;
+ master->dma_tx = mcspi_dma->dma_tx;
+
return (xfer->len >= DMA_MIN_BYTES);
}

@@ -1464,6 +1455,11 @@ static int omap2_mcspi_probe(struct plat
for (i = 0; i < master->num_chipselect; i++) {
sprintf(mcspi->dma_channels[i].dma_rx_ch_name, "rx%d", i);
sprintf(mcspi->dma_channels[i].dma_tx_ch_name, "tx%d", i);
+
+ status = omap2_mcspi_request_dma(mcspi,
+ &mcspi->dma_channels[i]);
+ if (status == -EPROBE_DEFER)
+ goto free_master;
}

status = platform_get_irq(pdev, 0);
@@ -1501,6 +1497,7 @@ disable_pm:
pm_runtime_put_sync(&pdev->dev);
pm_runtime_disable(&pdev->dev);
free_master:
+ omap2_mcspi_release_dma(master);
spi_master_put(master);
return status;
}
@@ -1510,6 +1507,8 @@ static int omap2_mcspi_remove(struct pla
struct spi_master *master = platform_get_drvdata(pdev);
struct omap2_mcspi *mcspi = spi_master_get_devdata(master);

+ omap2_mcspi_release_dma(master);
+
pm_runtime_dont_use_autosuspend(mcspi->dev);
pm_runtime_put_sync(mcspi->dev);
pm_runtime_disable(&pdev->dev);


2020-03-24 13:32:23

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 020/119] drivers/perf: fsl_imx8_ddr: Correct the CLEAR bit definition

From: Joakim Zhang <[email protected]>

[ Upstream commit 049d919168458ac54e7fad27cd156a958b042d2f ]

When disabling a counter from ddr_perf_event_stop(), the counter value
is reset to 0 at the same time.

Preserve the counter value by performing a read-modify-write of the
PMU register and clearing only the enable bit.

Signed-off-by: Joakim Zhang <[email protected]>
Signed-off-by: Will Deacon <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
drivers/perf/fsl_imx8_ddr_perf.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/drivers/perf/fsl_imx8_ddr_perf.c b/drivers/perf/fsl_imx8_ddr_perf.c
index 95dca2cb52650..90884d14f95fa 100644
--- a/drivers/perf/fsl_imx8_ddr_perf.c
+++ b/drivers/perf/fsl_imx8_ddr_perf.c
@@ -388,9 +388,10 @@ static void ddr_perf_counter_enable(struct ddr_pmu *pmu, int config,

if (enable) {
/*
- * must disable first, then enable again
- * otherwise, cycle counter will not work
- * if previous state is enabled.
+ * cycle counter is special which should firstly write 0 then
+ * write 1 into CLEAR bit to clear it. Other counters only
+ * need write 0 into CLEAR bit and it turns out to be 1 by
+ * hardware. Below enable flow is harmless for all counters.
*/
writel(0, pmu->base + reg);
val = CNTL_EN | CNTL_CLEAR;
@@ -398,7 +399,8 @@ static void ddr_perf_counter_enable(struct ddr_pmu *pmu, int config,
writel(val, pmu->base + reg);
} else {
/* Disable counter */
- writel(0, pmu->base + reg);
+ val = readl_relaxed(pmu->base + reg) & CNTL_EN_MASK;
+ writel(val, pmu->base + reg);
}
}

--
2.20.1



2020-03-24 13:32:26

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 021/119] drivers/perf: arm_pmu_acpi: Fix incorrect checking of gicc pointer

From: luanshi <[email protected]>

[ Upstream commit 3ba52ad55b533760a1f65836aa0ec9d35e36bb4f ]

Fix bogus NULL checks on the return value of acpi_cpu_get_madt_gicc()
by checking for a 0 'gicc->performance_interrupt' value instead.

Signed-off-by: Liguang Zhang <[email protected]>
Signed-off-by: Will Deacon <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
drivers/perf/arm_pmu_acpi.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/drivers/perf/arm_pmu_acpi.c b/drivers/perf/arm_pmu_acpi.c
index acce8781c456c..f5c7a845cd7bf 100644
--- a/drivers/perf/arm_pmu_acpi.c
+++ b/drivers/perf/arm_pmu_acpi.c
@@ -24,8 +24,6 @@ static int arm_pmu_acpi_register_irq(int cpu)
int gsi, trigger;

gicc = acpi_cpu_get_madt_gicc(cpu);
- if (WARN_ON(!gicc))
- return -EINVAL;

gsi = gicc->performance_interrupt;

@@ -64,11 +62,10 @@ static void arm_pmu_acpi_unregister_irq(int cpu)
int gsi;

gicc = acpi_cpu_get_madt_gicc(cpu);
- if (!gicc)
- return;

gsi = gicc->performance_interrupt;
- acpi_unregister_gsi(gsi);
+ if (gsi)
+ acpi_unregister_gsi(gsi);
}

#if IS_ENABLED(CONFIG_ARM_SPE_PMU)
--
2.20.1



2020-03-24 13:32:35

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 016/119] ARM: dts: bcm283x: Add missing properties to the PWR LED

From: Stefan Wahren <[email protected]>

[ Upstream commit bff211bab301db890e38de872d43cbb459940daa ]

This adds the missing properties to the PWR LED for the RPi 3 & 4 boards,
which are already set for the other boards. Without them we will lose
the LED state after suspend.

Signed-off-by: Stefan Wahren <[email protected]>
Tested-by: Peter Robinson <[email protected]>
Signed-off-by: Florian Fainelli <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 2 ++
arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts | 2 ++
arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts | 2 ++
3 files changed, 6 insertions(+)

diff --git a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
index 1b5a835f66bd3..b8c4b5bb265a9 100644
--- a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
+++ b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
@@ -31,6 +31,8 @@
pwr {
label = "PWR";
gpios = <&expgpio 2 GPIO_ACTIVE_LOW>;
+ default-state = "keep";
+ linux,default-trigger = "default-on";
};
};

diff --git a/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts b/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts
index 66ab35eccba7b..28be0332c1c81 100644
--- a/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts
+++ b/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts
@@ -26,6 +26,8 @@
pwr {
label = "PWR";
gpios = <&expgpio 2 GPIO_ACTIVE_LOW>;
+ default-state = "keep";
+ linux,default-trigger = "default-on";
};
};
};
diff --git a/arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts b/arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts
index 74ed6d0478070..37343148643db 100644
--- a/arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts
+++ b/arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts
@@ -27,6 +27,8 @@
pwr {
label = "PWR";
gpios = <&expgpio 2 GPIO_ACTIVE_LOW>;
+ default-state = "keep";
+ linux,default-trigger = "default-on";
};
};

--
2.20.1



2020-03-24 13:32:36

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 015/119] spi/zynqmp: remove entry that causes a cs glitch

From: Thommy Jakobsson <[email protected]>

[ Upstream commit 5dd8304981ecffa77bb72b1c57c4be5dfe6cfae9 ]

In the public interface for chipselect, there is always an entry
commented as "Dummy generic FIFO entry" pushed down to the fifo right
after the activate/deactivate command. The dummy entry is 0x0,
irregardless if the intention was to activate or deactive the cs. This
causes the cs line to glitch rather than beeing activated in the case
when there was an activate command.

This has been observed on oscilloscope, and have caused problems for at
least one specific flash device type connected to the qspi port. After
the change the glitch is gone and cs goes active when intended.

The reason why this worked before (except for the glitch) was because
when sending the actual data, the CS bits are once again set. Since
most flashes uses mode 0, there is always a half clk period anyway for
cs to clk active setup time. If someone would rely on timing from a
chip_select call to a transfer_one, it would fail though.

It is unknown why the dummy entry was there in the first place, git log
seems to be of no help in this case. The reference manual gives no
indication of the necessity of this. In fact the lower 8 bits are a
setup (or hold in case of deactivate) time expressed in cycles. So this
should not be needed to fulfill any setup/hold timings.

Signed-off-by: Thommy Jakobsson <[email protected]>
Reviewed-by: Naga Sureshkumar Relli <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Mark Brown <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
drivers/spi/spi-zynqmp-gqspi.c | 3 ---
1 file changed, 3 deletions(-)

diff --git a/drivers/spi/spi-zynqmp-gqspi.c b/drivers/spi/spi-zynqmp-gqspi.c
index 60c4de4e44856..7412a3042a8d2 100644
--- a/drivers/spi/spi-zynqmp-gqspi.c
+++ b/drivers/spi/spi-zynqmp-gqspi.c
@@ -401,9 +401,6 @@ static void zynqmp_qspi_chipselect(struct spi_device *qspi, bool is_high)

zynqmp_gqspi_write(xqspi, GQSPI_GEN_FIFO_OFST, genfifoentry);

- /* Dummy generic FIFO entry */
- zynqmp_gqspi_write(xqspi, GQSPI_GEN_FIFO_OFST, 0x0);
-
/* Manually start the generic FIFO command */
zynqmp_gqspi_write(xqspi, GQSPI_CONFIG_OFST,
zynqmp_gqspi_read(xqspi, GQSPI_CONFIG_OFST) |
--
2.20.1



2020-03-24 13:32:51

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.5 001/119] locks: fix a potential use-after-free problem when wakeup a waiter

From: yangerkun <[email protected]>

[ Upstream commit 6d390e4b5d48ec03bb87e63cf0a2bff5f4e116da ]

'16306a61d3b7 ("fs/locks: always delete_block after waiting.")' add the
logic to check waiter->fl_blocker without blocked_lock_lock. And it will
trigger a UAF when we try to wakeup some waiter:

Thread 1 has create a write flock a on file, and now thread 2 try to
unlock and delete flock a, thread 3 try to add flock b on the same file.

Thread2 Thread3
flock syscall(create flock b)
...flock_lock_inode_wait
flock_lock_inode(will insert
our fl_blocked_member list
to flock a's fl_blocked_requests)
sleep
flock syscall(unlock)
...flock_lock_inode_wait
locks_delete_lock_ctx
...__locks_wake_up_blocks
__locks_delete_blocks(
b->fl_blocker = NULL)
...
break by a signal
locks_delete_block
b->fl_blocker == NULL &&
list_empty(&b->fl_blocked_requests)
success, return directly
locks_free_lock b
wake_up(&b->fl_waiter)
trigger UAF

Fix it by remove this logic, and this patch may also fix CVE-2019-19769.

Cc: [email protected]
Fixes: 16306a61d3b7 ("fs/locks: always delete_block after waiting.")
Signed-off-by: yangerkun <[email protected]>
Signed-off-by: Jeff Layton <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
fs/locks.c | 14 --------------
1 file changed, 14 deletions(-)

diff --git a/fs/locks.c b/fs/locks.c
index 44b6da0328426..426b55d333d5b 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -753,20 +753,6 @@ int locks_delete_block(struct file_lock *waiter)
{
int status = -ENOENT;

- /*
- * If fl_blocker is NULL, it won't be set again as this thread
- * "owns" the lock and is the only one that might try to claim
- * the lock. So it is safe to test fl_blocker locklessly.
- * Also if fl_blocker is NULL, this waiter is not listed on
- * fl_blocked_requests for some lock, so no other request can
- * be added to the list of fl_blocked_requests for this
- * request. So if fl_blocker is NULL, it is safe to
- * locklessly check if fl_blocked_requests is empty. If both
- * of these checks succeed, there is no need to take the lock.
- */
- if (waiter->fl_blocker == NULL &&
- list_empty(&waiter->fl_blocked_requests))
- return status;
spin_lock(&blocked_lock_lock);
if (waiter->fl_blocker)
status = 0;
--
2.20.1



2020-03-24 19:47:28

by Shuah Khan

[permalink] [raw]
Subject: Re: [PATCH 5.5 000/119] 5.5.12-rc1 review

On 3/24/20 7:09 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.5.12 release.
> There are 119 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu, 26 Mar 2020 13:06:42 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.5.12-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.5.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>

Compiled and booted on my test system. No dmesg regressions.

thanks,
-- Shuah

2020-03-24 20:57:41

by Guenter Roeck

[permalink] [raw]
Subject: Re: [PATCH 5.5 000/119] 5.5.12-rc1 review

On 3/24/20 6:09 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.5.12 release.
> There are 119 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu, 26 Mar 2020 13:06:42 +0000.
> Anything received after that time might be too late.
>

Build results:
total: 157 pass: 157 fail: 0
Qemu test results:
total: 428 pass: 428 fail: 0

Guenter

2020-03-25 05:48:02

by Naresh Kamboju

[permalink] [raw]
Subject: Re: [PATCH 5.5 000/119] 5.5.12-rc1 review

On Tue, 24 Mar 2020 at 18:52, Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 5.5.12 release.
> There are 119 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu, 26 Mar 2020 13:06:42 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.5.12-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.5.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.

Summary
------------------------------------------------------------------------

kernel: 5.5.12-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-5.5.y
git commit: 738ff80e1bc68169f717060d4bca7cb6098741c5
git describe: v5.5.11-120-g738ff80e1bc6
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.5-oe/build/v5.5.11-120-g738ff80e1bc6

No regressions (compared to build v5.5.10-55-gbea94317c526)


No fixes (compared to build v5.5.10-55-gbea94317c526)

Ran 37203 total tests in the following environments and test suites.

Environments
--------------
- dragonboard-410c
- hi6220-hikey
- i386
- juno-r2
- juno-r2-compat
- juno-r2-kasan
- nxp-ls2088
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15
- x86
- x86-kasan

Test Suites
-----------
* build
* install-android-platform-tools-r2600
* install-android-platform-tools-r2800
* libgpiod
* libhugetlbfs
* linux-log-parser
* ltp-cve-tests
* ltp-dio-tests
* ltp-fs-tests
* ltp-io-tests
* perf
* v4l2-compliance
* ltp-cap_bounds-tests
* ltp-cpuhotplug-tests
* ltp-crypto-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* network-basic-tests
* kselftest
* kvm-unit-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-ipc-tests
* ltp-math-tests
* spectre-meltdown-checker-test
* ltp-open-posix-tests
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none

--
Linaro LKFT
https://lkft.linaro.org

2020-03-25 17:55:03

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 5.5 000/119] 5.5.12-rc1 review

On Tue, Mar 24, 2020 at 01:45:06PM -0600, shuah wrote:
> On 3/24/20 7:09 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.5.12 release.
> > There are 119 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Thu, 26 Mar 2020 13:06:42 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.5.12-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.5.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> >
>
> Compiled and booted on my test system. No dmesg regressions.

Thanks for testing these and letting me know.

greg k-h

2020-03-25 17:55:39

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 5.5 000/119] 5.5.12-rc1 review

On Tue, Mar 24, 2020 at 01:56:35PM -0700, Guenter Roeck wrote:
> On 3/24/20 6:09 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.5.12 release.
> > There are 119 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Thu, 26 Mar 2020 13:06:42 +0000.
> > Anything received after that time might be too late.
> >
>
> Build results:
> total: 157 pass: 157 fail: 0
> Qemu test results:
> total: 428 pass: 428 fail: 0

Thanks ofr testinging all of these and letting me know.

greg k-h

2020-03-25 17:55:41

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 5.5 000/119] 5.5.12-rc1 review

On Wed, Mar 25, 2020 at 11:16:22AM +0530, Naresh Kamboju wrote:
> On Tue, 24 Mar 2020 at 18:52, Greg Kroah-Hartman
> <[email protected]> wrote:
> >
> > This is the start of the stable review cycle for the 5.5.12 release.
> > There are 119 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Thu, 26 Mar 2020 13:06:42 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.5.12-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.5.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Results from Linaro’s test farm.
> No regressions on arm64, arm, x86_64, and i386.

Great, thanks for testing these and letting me know.

greg k-h