[PATCH 4.18 050/171] scsi: qla2xxx: Fix re-using LoopID when handle is in use

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit 5c6400536481d9ef44ef94e7bf2c7b8e81534db7 upstream. This patch fixes issue where driver clears NPort ID map instead of marking handle in use. Once driver clears NPort ID from

[PATCH 4.18 053/171] arm64: dts: stratix10: fix multicast filtering

4.18-stable review patch. If anyone has any objections, please let me know. -- commit fd5ba6ee3187617287fb9cb187e3d6b3631210a3 upstream On Stratix 10, the EMAC has 256 hash buckets for multicast filtering. This needs to be specified in DTS, otherwise the stmmac driver defaults t

[PATCH 4.18 051/171] scsi: qla2xxx: Fix NVMe session hang on unload

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit f7d61c995df74d6bb57bbff6a2b7b1874c4a2baa upstream. Send aborts only when chip is active. Fixes: 623ee824e579 ("scsi: qla2xxx: Fix FC-NVMe IO abort during driver reset") Cc:

[PATCH 4.18 009/171] tty: check name length in tty_find_polling_driver()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Miles Chen [ Upstream commit 33a1a7be198657c8ca26ad406c4d2a89b7162bcc ] The issue is found by a fuzzing test. If tty_find_polling_driver() recevies an incorrect input such as ',,' or '0b', the

[PATCH 4.18 048/171] fuse: set FR_SENT while locked

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 4c316f2f3ff315cb48efb7435621e5bfb81df96d upstream. Otherwise fuse_dev_do_write() could come in and finish off the request, and the set_bit(FR_SENT, ...) could trigger the

[PATCH 4.18 045/171] fuse: Fix use-after-free in fuse_dev_do_read()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kirill Tkhai commit bc78abbd55dd28e2287ec6d6502b842321a17c87 upstream. We may pick freed req in this way: [cpu0] [cpu1] fuse_dev_do_read()

[PATCH 4.18 052/171] arm64: dts: stratix10: Support Ethernet Jumbo frame

4.18-stable review patch. If anyone has any objections, please let me know. -- commit a27460c9768ee19949c5b91f3d959ccd88c2a64a upstream Properly specify the RX and TX FIFO size which is important for Jumbo frames. Update the max-frame-size to support Jumbo frames. Signed-off-by

[PATCH 4.18 000/171] 4.18.20-stable review

-- NOTE, this is going to be the last 4.18.y release. After this one it is end-of-life, please move to 4.19.y at this point in time. -- This is the start of the stable review cycle for the 4.18.20 release. There are 171 patches in this series, all will be posted as

[PATCH 4.18 007/171] powerpc/Makefile: Fix PPC_BOOK3S_64 ASFLAGS

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Joel Stanley [ Upstream commit 960e30029863db95ec79a71009272d4661db5991 ] Ever since commit 15a3204d24a3 ("powerpc/64s: Set assembler machine type to POWER4") we force -mpower4 to be passed to

[PATCH 4.18 034/171] 9p: clear dangling pointers in p9stat_free

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dominique Martinet [ Upstream commit 62e3941776fea8678bb8120607039410b1b61a65 ] p9stat_free is more of a cleanup function than a 'free' function as it only frees the content of the struct; the

[PATCH 4.18 004/171] powerpc/mm: fix always true/false warning in slice.c

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy [ Upstream commit 37e9c674e7e6f445e12cb1151017bd4bacdd1e2d ] This patch fixes the following warnings (obtained with make W=1). arch/powerpc/mm/slice.c: In function 'slice_ran

[PATCH 4.18 003/171] powerpc/mm: Fix page table dump to work on Radix

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman [ Upstream commit 0d923962ab69c27cca664a2d535e90ef655110ca ] When we're running on Book3S with the Radix MMU enabled the page table dump currently prints the wrong addresses b

[PATCH 4.18 005/171] drm/amd/display: fix bug of accessing invalid memory

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Su Sung Chung [ Upstream commit 43c3ff27a47d83d153c4adc088243ba594582bf5 ] [Why] A loop inside of build_evenly_distributed_points function that traverse through the array of points become an i

[PATCH 4.18 006/171] Input: wm97xx-ts - fix exit path

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit a3f7c3fcf60868c1e90671df5d0cf9be5900a09b ] Loading then unloading wm97xx-ts.ko when CONFIG_AC97_BUS=m causes a WARNING: from drivers/base/driver.c: Unexpected d

[PATCH 4.18 032/171] udf: Prevent write-unsupported filesystem to be remounted read-write

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara [ Upstream commit a9ad01bc759df79b0012f43ee52164391e31cd96 ] There are certain filesystem features which we support for reading but not for writing. We properly refuse to mount such f

[PATCH 4.18 031/171] 9p locks: fix glock.client_id leak in do_lock

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dominique Martinet [ Upstream commit b4dc44b3cac9e8327e0655f530ed0c46f2e6214c ] the 9p client code overwrites our glock.client_id pointing to a static buffer by an allocated string holding the

[PATCH 4.18 030/171] staging: most: video: fix registration of an empty comp core_component

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit 1f447e51c0b9e8beeec0917ea5f51930f55e17c9 ] Currently we have structrues comp (which is empty) and comp_info being used to register and deregister the component

[PATCH 4.18 033/171] ARM: dts: imx6ull: keep IMX6UL_ prefix for signals on both i.MX6UL and i.MX6ULL

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sébastien Szymanski [ Upstream commit 31edaa6e7fd8143085a6a60c564447c07e76ed9f ] Signals available on both i.MX6UL and i.MX6ULL should have the same name because it is the case of all others c

[PATCH 4.18 027/171] staging:iio:ad7606: fix voltage scales

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexandru Ardelean [ Upstream commit 4ee033301c898dd0835d035d0e0eb768a3d35da1 ] Fixes commit 17be2a2905a6ec9aa27cd59521495e2f490d2af0 ("staging: iio: ad7606: replace range/range_available with

[PATCH 4.18 028/171] drm: rcar-du: Update Gen3 output limitations

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kieran Bingham [ Upstream commit 2a3181d9cfd6d5aa48f8527708d0c32072072cef ] The R-Car Gen3 DU utilises the VSP1 hardware for memory access. The limits on the RPF and WPF in this pipeline are 8

[PATCH 4.18 029/171] drm/amdgpu: Fix SDMA TO after GPU reset v3

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Grodzovsky [ Upstream commit d8de8260a45aae8f74af77eae9a162bdc0ed48d2 ] After GPU reset amdgpu_vm_clear_bo triggers VM flush but job->vm_pd_addr is not set causing SDMA TO. v2: Per adv

[PATCH 4.18 025/171] media: tvp5150: fix width alignment during set_selection()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Marco Felsch [ Upstream commit bd24db04101f45a9c1d874fe21b0c7eab7bcadec ] The driver ignored the width alignment which exists due to the UYVY colorspace format. Fix the width alignment and mak

[PATCH 4.18 024/171] sc16is7xx: Fix for multi-channel stall

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Phil Elwell [ Upstream commit 8344498721059754e09d30fe255a12dab8fb03ef ] The SC16IS752 is a dual-channel device. The two channels are largely independent, but the IRQ signals are wired togethe

[PATCH 4.18 026/171] powerpc/selftests: Wait all threads to join

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Breno Leitao [ Upstream commit 693b31b2fc1636f0aa7af53136d3b49f6ad9ff39 ] Test tm-tmspr might exit before all threads stop executing, because it just waits for the very last thread to join bef

[PATCH 4.18 022/171] powerpc/memtrace: Remove memory in chunks

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rashmica Gupta [ Upstream commit 3f7daf3d7582dc6628ac40a9045dd1bbd80c5f35 ] When hot-removing memory release_mem_region_adjustable() splits iomem resources if they are not the exact size of th

[PATCH 4.18 023/171] MIPS/PCI: Call pcie_bus_configure_settings() to set MPS/MRRS

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Huacai Chen [ Upstream commit 2794f688b2c336e0da85e9f91fed33febbd9f54a ] Call pcie_bus_configure_settings() on MIPS, like for other platforms. The function pcie_bus_configure_settings() makes

[PATCH 4.18 015/171] drm/omap: fix memory barrier bug in DMM driver

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tomi Valkeinen [ Upstream commit 538f66ba204944470a653a45f8befdf97c22 ] A DMM timeout "timed out waiting for done" has been observed on DRA7 devices. The timeout happens rarely, and only w

[PATCH 4.18 020/171] MIPS: kexec: Mark CPU offline before disabling local IRQ

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dengcheng Zhu [ Upstream commit dc57aaf95a516f70e2d527d8287a0332c481a226 ] After changing CPU online status, it will not be sent any IPIs such as in __flush_cache_all() on software coherency s

[PATCH 4.18 019/171] media: coda: dont overwrite h.264 profile_idc on decoder instance

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach [ Upstream commit 1f32061e843205f6fe8404d5100d5adcec334e75 ] On a decoder instance, after the profile has been parsed from the stream __v4l2_ctrl_s_ctrl() is called to notify users

[PATCH 4.18 017/171] drm/hisilicon: hibmc: Do not carry error code in HiBMC framebuffer pointer

4.18-stable review patch. If anyone has any objections, please let me know. -- From: John Garry [ Upstream commit 331d880b35a76b5de0eec8cbcecbf615d758a5f9 ] In hibmc_drm_fb_create(), when the call to hibmc_framebuffer_init() fails with error, do not store the error code in the

[PATCH 4.18 018/171] media: pci: cx23885: handle adding to list failure

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire [ Upstream commit c5d59528e24ad22500347b199d52b9368e686a42 ] altera_hw_filt_init() which calls append_internal() assumes that the node was successfully linked in while in fac

[PATCH 4.18 021/171] powerpc/boot: Ensure _zimage_start is a weak symbol

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Joel Stanley [ Upstream commit ee9d21b3b3583712029a0db65a4b7c081d08d3b3 ] When building with clang crt0's _zimage_start is not marked weak, which breaks the build when linking the kernel image

[PATCH 4.18 016/171] drm/amd/display: fix gamma not being applied

4.18-stable review patch. If anyone has any objections, please let me know. -- From: SivapiriyanKumarasamy [ Upstream commit 30049754ab7c4b6148dd3cd64af7d54850604582 ] [WHY] Previously night light forced a full update by applying a transfer function update regardless of if it

[PATCH 4.18 011/171] drm/amdgpu/powerplay: fix missing break in switch statements

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit 14b284832e7dea6f54f0adfd7bed105548b94e57 ] There are several switch statements that are missing break statements. Add missing breaks to handle any fall-through

[PATCH 4.18 014/171] powerpc/mm: Dont report hugepage tables as memory leaks when using kmemleak

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy [ Upstream commit 803d690e68f0c5230183f1a42c7d50a41d16e380 ] When a process allocates a hugepage, the following leak is reported by kmemleak. This is a false positive which is

[PATCH 4.18 012/171] ARM: imx_v6_v7_defconfig: Select CONFIG_TMPFS_POSIX_ACL

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Fabio Estevam [ Upstream commit 35d3cbe84544da74e39e1cec01374092467e3119 ] Andreas Müller reports: "Fixes: | Sep 04 09:05:10 imx6qdl-variscite-som systemd-udevd[220]: Failed to apply ACL on

[PATCH 4.18 010/171] tracing/kprobes: Check the probe on unloaded module correctly

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu [ Upstream commit 59158ec4aef7d44be51a6f3e7e17fc64c32604eb ] Current kprobe event doesn't checks correctly whether the given event is on unloaded module or not. It just checks

[PATCH 4.18 001/171] powerpc/traps: restore recoverability of machine_check interrupts

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy [ Upstream commit daf00ae71dad8aa05965713c62558aeebf2df48e ] commit b96672dd840f ("powerpc: Machine check interrupt is a non- maskable interrupt") added a call to nmi_enter()

[PATCH 4.19 184/205] drm/i915/dp: Link train Fallback on eDP only if fallback link BW can fit panels native mode

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Manasi Navare commit 04158835d7fb2c9f042598bfe16bf375b15d upstream. This patch fixes the original commit c0cfb10d9e1de49 ("drm/i915/edp: Do not do link training fallback or prune modes on

[PATCH 4.19 193/205] drm/i915/hdmi: Add HDMI 2.0 audio clock recovery N values

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Clint Taylor commit 6503493145cba4413ecd3d4d153faeef4a1e9b85 upstream. HDMI 2.0 594Mhz modes were incorrectly selecting 25.200Mhz Automatic N value mode instead of HDMI specification values.

[PATCH 4.19 192/205] drm/i915/icl: Fix the macros for DFLEXDPMLE register bits

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Manasi Navare commit e528c2affcf216b3d02b22004895cb678769629b upstream. This patch fixes the macros used for defining the DFLEXDPMLE register bit fields. This accounts for changes in the spec.

[PATCH 4.19 191/205] drm/i915/dp: Restrict link retrain workaround to external monitors

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Dhinakaran Pandiyan commit f9776280c29e77a18cbc7ebb6d48f7885e494990 upstream. Commit '3cf71bc9904d ("drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse"")' appli

[PATCH 4.19 203/205] drm/i915: Fix NULL deref when re-enabling HPD IRQs on systems with MST

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul commit 541ff7e96c13cd5d67f6021d233f8e1c3df49278 upstream. Turns out that if you trigger an HPD storm on a system that has an MST topology connected to it, you'll end up causing the

[PATCH 4.19 201/205] drm/i915/execlists: Force write serialisation into context image vs execution

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit 0a823e8fd4fd67726697854578f3584ee3a49b1d upstream. Ensure that the writes into the context image are completed prior to the register mmio to trigger execution. Although pre

[PATCH 4.19 200/205] drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit fb5bbae9b1333d44023713946fdd28db0cd85751 upstream. Exercising the gpu reloc path strenuously revealed an issue where the updated relocations (from MI_STORE_DWORD_IMM) were

[PATCH 4.19 204/205] drm/i915: Fix hpd handling for pins with two encoders

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ville Syrjälä commit 44a7276b30c3c15f2b7790a5729640597fb6a1df upstream. In my haste to remove irq_port[] I accidentally changed the way we deal with hpd pins that are shared by multiple encode

[PATCH 4.19 186/205] drm/i915: Restore vblank interrupts earlier

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ville Syrjälä commit 7cada4d0b7a0fb813dbc9777fec092e9ed0546e9 upstream. Plane sanitation needs vblank interrupts (on account of CxSR disable). So let's restore vblank interrupts earlier. v2:

[PATCH 4.19 190/205] drm/i915/dp: Fix link retraining comment in intel_dp_long_pulse()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Dhinakaran Pandiyan commit 49af5d95b9b3c21a84ad115a9db9acbc036d849a upstream. Comment claims link needs to be retrained because the connected sink raised a long pulse to indicate link loss. If

[PATCH 4.19 188/205] drm/i915: Skip vcpi allocation for MSTB ports that are gone

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul commit c02ba4ef16eefe663fdefcccaa57fad32d5481bf upstream. Since we need to be able to allow DPMS on->off prop changes after an MST port has disappeared from the system, we need to b

[PATCH 4.19 189/205] drm/i915: Large page offsets for pread/pwrite

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit ab0d6a141843e0b4b2709dfd37b53468b5452c3a upstream. Handle integer overflow when computing the sub-page length for shmem backed pread/pwrite. Reported-by: Tvrtko Ursulin S

Re: Memory hotplug softlock issue

On 11/19/18 3:10 PM, Michal Hocko wrote: > On Mon 19-11-18 13:51:21, Michal Hocko wrote: >> On Mon 19-11-18 13:40:33, Michal Hocko wrote: >>> How are >>> we supposed to converge when the swapin code waits for the migration to >>> finish with the reference count elevated? Indeed this looks wrong. H

[PATCH 4.19 205/205] CONFIG_XEN_PV breaks xen_create_contiguous_region on ARM

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Stabellini commit f9005571701920551bcf54a500973fb61f2e1eda upstream. xen_create_contiguous_region has now only an implementation if CONFIG_XEN_PV is defined. However, on ARM we never s

[PATCH 4.19 199/205] drm/i915: Mark pin flags as u64

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit 0014868b9c3c1dda1de6711cf58c3486fb422d07 upstream. Since the flags are being used to operate on a u64 variable, they too need to be marked as such so that the inverses are

[PATCH 4.19 198/205] drm/i915: Dont oops during modeset shutdown after lpe audio deinit

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ville Syrjälä commit 6a8915d0f8cf323e1beb792a33095cf652db4056 upstream. We deinit the lpe audio device before we call drm_atomic_helper_shutdown(), which means the platform device may already

[PATCH 4.19 195/205] drm/i915: Fix error handling for the NV12 fb dimensions check

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ville Syrjälä commit f42f343887016330b321dd40eebc68c7292e4f1b upstream. Let's not leak obj->framebuffer_references when we decide that the framebuffer domensions are not suitable for NV12. Cc

[PATCH 4.19 194/205] drm/i915: Mark up GTT sizes as u64

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit c58281056a8b26d5d9dc15c19859a7880835ef44 upstream. Since we use a 64b virtual GTT irrespective of the system, we want to ensure that the GTT computations remains 64b even o

[PATCH 4.19 185/205] drm/i915: Use the correct crtc when sanitizing plane mapping

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ville Syrjälä commit 9b27390139dbe0dc10d1899545248862fe826b61 upstream. When we decide that a plane is attached to the wrong pipe we try to turn off said plane. However we are passing around t

[PATCH 4.19 197/205] drm/i915: Compare users 64b GTT offset even on 32b

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit 085603287452fc96376ed4888bf29f8c095d2b40 upstream. Beware mixing unsigned long constants and 64b values, as on 32b the constant will be zero extended and discard the high 3

[PATCH 4.19 143/205] ext4: release bs.bh before re-using in ext4_xattr_block_find()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Averin commit 45ae932d246f721e6584430017176cbcadfde610 upstream. bs.bh was taken in previous ext4_xattr_block_find() call, it should be released before re-using Fixes: 7e01c8e5420b ("e

[PATCH 4.19 152/205] ARM: cpuidle: Dont register the driver when back-end init returns -ENXIO

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ulf Hansson commit 763f191af51f127cf8e69cd361f50bf6180768a5 upstream. There's no point to register the cpuidle driver for the current CPU, when the initialization of the arch specific back-end

[PATCH 4.19 150/205] mnt: fix __detach_mounts infinite loop

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Coddington commit 1e9c75fb9c47a75a9aec0cd17db5f6dc36b58e00 upstream. Since commit ff17fa561a04 ("d_invalidate(): unhash immediately") immediately unhashes the dentry, we'll never retu

[PATCH 4.19 149/205] mount: Prevent MNT_DETACH from disconnecting locked mounts

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit 9c8e0a1b683525464a2abe9fb4b54404a50ed2b4 upstream. Timothy Baldwin wrote: > As per mount_namespaces(7) unprivileged users should not be able to look > under mount po

[PATCH 4.19 180/205] drm/etnaviv: fix bogus fence complete check in timeout handler

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach commit 6fce3a406108ee6c8a61e2a33e52e9198a626ea0 upstream. The GPU hardware fences and the job out-fences are on different timelines so it's wrong to compare them. Fix this by only

[PATCH 4.19 181/205] drm/dp_mst: Check if primary mstb is null

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Stanislav Lisovskiy commit 23d8003907d094f77cf959228e2248d6db819fa7 upstream. Unfortunately drm_dp_get_mst_branch_device which is called from both drm_dp_mst_handle_down_rep and drm_dp_mst_han

[PATCH 4.19 178/205] drm/nouveau: Fix nv50_mstc->best_encoder()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul commit 7b0f61e91b6056c71649efa3204112a4b6cf5fc8 upstream. As mentioned in the previous commit, we currently prevent new modesets on recently-removed MST connectors by returning no e

[PATCH 4.19 147/205] mount: Retest MNT_LOCKED in do_umount

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit 25d202ed820ee347edec0bf3bf553544556bf64b upstream. It was recently pointed out that the one instance of testing MNT_LOCKED outside of the namespace_sem is in ksys_umou

[PATCH 4.19 182/205] drm/atomic_helper: Disallow new modesets on unregistered connectors

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul commit e96550956fbcd090629c0e2b5b8cded2eded2adf upstream. With the exception of modesets which would switch the DPMS state of a connector from on to off, we want to make sure that w

[PATCH 4.19 176/205] drm/amdgpu: Suppress keypresses from ACPI_VIDEO events

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul commit 582f58de36834096a91cc1de2540c2f7269f850d upstream. Currently we return NOTIFY_DONE for any event which we don't think is ours. However, many laptops will send more then just

[PATCH 4.19 183/205] drm: panel-orientation-quirks: Add quirk for Acer One 10 (S1003)

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 0e8afefd5da4875ddea9aa4ad17a2540a2bf9736 upstream. The Acer One 10 uses a clamshell design with a detachable keyboard. As such in normal operating mode, with the keyboard

[PATCH 4.19 177/205] drm/nouveau: Check backlight IDs are >= 0, not > 0

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul commit dc854914999d5d52ac1b31740cb0ea8d89d0372e upstream. Remember, ida IDs start at 0, not 1! Signed-off-by: Lyude Paul Reviewed-by: Karol Herbst Cc: sta...@vger.kernel.org Sign

[PATCH 4.19 148/205] mount: Dont allow copying MNT_UNBINDABLE|MNT_LOCKED mounts

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit df7342b240185d58d3d9665c0bbf0a0f5570ec29 upstream. Jonathan Calmels from NVIDIA reported that he's able to bypass the mount visibility security check in place in the L

[PATCH 4.19 172/205] scripts/spdxcheck.py: make python3 compliant

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Uwe Kleine-König commit 6f4d29df66acd49303a99025046b85cabe7aa17a upstream. Without this change the following happens when using Python3 (3.6.6): $ echo "GPL-2.0" | python3 scripts/spd

[PATCH 4.19 174/205] drm/amdgpu: Fix typo in amdgpu_vmid_mgr_init

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Rex Zhu commit 3df27645395e8f79c0dc20a15cf1da61f376000d upstream. fix a typo in for loop: i->j Reviewed-by: Christian König Signed-off-by: Rex Zhu Signed-off-by: Alex Deucher Cc: sta...@vg

Re: [PATCH] debugobjects: add a new Kconfig for POOL_SIZE

On Mon, 2018-11-19 at 17:25 +0100, Thomas Gleixner wrote: > On Mon, 19 Nov 2018, Waiman Long wrote: > > On 11/19/2018 10:17 AM, Qian Cai wrote: > > > Right, I can remember that now . However, if I understand correctly, since > > > the > > > early static pool size needs to be determined during the c

[PATCH 4.19 173/205] drm/rockchip: Allow driver to be shutdown on reboot/kexec

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 7f3ef5dedb146e3d5063b6845781ad1bb59b92b5 upstream. Leaving the DRM driver enabled on reboot or kexec has the annoying effect of leaving the display generating transactions

[PATCH 4.19 171/205] mm: dont reclaim inodes with many attached pages

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Roman Gushchin commit a76cf1a474d7dbcd9336b5f5afb0162baa142cf0 upstream. Spock reported that commit 172b06c32b94 ("mm: slowly shrink slabs with a relatively small number of objects") leads to

[PATCH 4.19 146/205] ext4: fix buffer leak in __ext4_read_dirblock() on error path

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Averin commit de59fae0043f07de5d25e02ca360f7d57bfa5866 upstream. Fixes: dc6982ff4db1 ("ext4: refactor code to read directory blocks ...") Signed-off-by: Vasily Averin Signed-off-by: Th

[PATCH 4.19 167/205] lib/ubsan.c: dont mark __ubsan_handle_builtin_unreachable as noreturn

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 1c23b4108d716cc848b38532063a8aca4f86add8 upstream. gcc-8 complains about the prototype for this function: lib/ubsan.c:432:1: error: ignoring attribute 'noreturn' in dec

Re: [RFC PATCH 0/5] iommu: APIs for paravirtual PASID allocation

On Mon, Nov 12, 2018 at 02:44:56PM +0800, Lu Baolu wrote: > This adds an uniformed API set for global PASIDs used by IOMMU > and device drivers which depend on IOMMU. It works for drivers > running on bare metal, full virtualized environments and para- > virtualized environment. > Are there also

[PATCH 4.19 166/205] crypto: user - fix leaking uninitialized memory to userspace

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit f43f39958beb206b53292801e216d9b8a660f087 upstream. All bytes of the NETLINK_CRYPTO report structures must be initialized, since they are copied to userspace. The change fr

[PATCH 4.19 165/205] libata: blacklist SAMSUNG MZ7TD256HAFV-000L9 SSD

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Diego Viola commit 410b5c7b48368317af95f0113692561d01d8144e upstream. med_power_with_dipm still causes freezes after updating the firmware to the latest version (DXT04L5Q). Set model_rev to N

[PATCH 4.19 164/205] gfs2: Fix metadata read-ahead during truncate (2)

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher commit e7445ceddfc220c1aede6d42758a5acb8844e9c3 upstream. The previous attempt to fix for metadata read-ahead during truncate was incorrect: for files with a height > 2 (10

[PATCH 4.19 170/205] efi/arm/libstub: Pack FDT after populating it

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 72a58a63a164b4e9d2d914e65caeb551846883f1 upstream. Commit: 24d7c494ce46 ("efi/arm-stub: Round up FDT allocation to mapping size") increased the allocation size for th

[PATCH 4.19 169/205] mm/swapfile.c: use kvzalloc for swap_info_struct allocation

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Averin commit 873d7bcfd03e3e50113dc4a0de19289b6354 upstream. Commit a2468cc9bfdf ("swap: choose swap device according to numa node") changed 'avail_lists' field of 'struct swap_info

[PATCH 4.19 161/205] fuse: fix possibly missed wake-up after abort

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 2d84a2d19b6150c6dbac1e6ebad9c82e4c123772 upstream. In current fuse_drop_waiting() implementation it's possible that fuse_wait_aborted() will not be woken up in the unlike

[PATCH 4.19 145/205] ext4: fix buffer leak in ext4_expand_extra_isize_ea() on error path

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Averin commit 53692ec074d00589c2cf1d6d17ca76ad0adce6ec upstream. Fixes: de05ca852679 ("ext4: move call to ext4_error() into ...") Signed-off-by: Vasily Averin Signed-off-by: Theodore T

[PATCH 4.19 162/205] selinux: check length properly in SCTP bind hook

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ondrej Mosnacek commit c138325fb8713472d5a0c3c7258b9131bab40725 upstream. selinux_sctp_bind_connect() must verify if the address buffer has sufficient length before accessing the 'sa_family' f

[PATCH 4.19 163/205] gfs2: Put bitmap buffers in put_super

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher commit 10283ea525d30f2e99828978fd04d8427876a7ad upstream. gfs2_put_super calls gfs2_clear_rgrpd to destroy the gfs2_rgrpd objects attached to the resource group glocks. Th

[PATCH 4.19 157/205] nfsd: COPY and CLONE operations require the saved filehandle to be set

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Scott Mayhew commit 01310bb7c9c98752cc763b36532fab028e0f8f81 upstream. Make sure we have a saved filehandle, otherwise we'll oops with a null pointer dereference in nfs4_preprocess_stateid_op(

[PATCH 4.19 159/205] fuse: fix use-after-free in fuse_direct_IO()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Czerner commit ebacb81273599555a7a19f7754a1451206a5fc4f upstream. In async IO blocking case the additional reference to the io is taken for it to survive fuse_aio_complete(). In non bloc

[PATCH 4.19 158/205] rtc: hctosys: Add missing range error reporting

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit 7ce9a992ffde8ce93d5ae5767362a5c7389ae895 upstream. Fix an issue with the 32-bit range error path in `rtc_hctosys' where no error code is set and consequently the succe

[PATCH 4.19 160/205] fuse: fix leaked notify reply

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 7fabaf303458fcabb694999d6fa772cc13d4e217 upstream. fuse_request_send_notify_reply() may fail if the connection was reset for some reason (e.g. fs was unmounted). Don't l

[PATCH 4.19 156/205] NFSv4: Dont exit the state manager without clearing NFS4CLNT_MANAGER_RUNNING

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 21a446cf186570168b7281b154b1993968598aca upstream. If we exit the NFSv4 state manager due to a umount, then we can end up leaving the NFS4CLNT_MANAGER_RUNNING flag set.

[PATCH 4.19 154/205] kdb: print real address of pointers instead of hashed addresses

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 568fb6f42ac6851320adaea25f8f1b94de14e40a upstream. Since commit ad67b74d2469 ("printk: hash addresses printed with %p"), all pointers printed with %p are printed with h

[PATCH 4.19 155/205] sunrpc: correct the computation for page_ptr when truncating

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Frank Sorenson commit 5d7a5bcb67c70cbc904057ef52d3fcfeb24420bb upstream. When truncating the encode buffer, the page_ptr is getting advanced, causing the next page to be skipped while encoding

[PATCH 4.19 111/205] hwmon: (core) Fix double-free in __hwmon_device_register()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Osipenko commit 74e3512731bd5c9673176425a76a7cc5efa8ddb6 upstream. Fix double-free that happens when thermal zone setup fails, see KASAN log below.

[PATCH 4.19 144/205] ext4: fix buffer leak in ext4_xattr_move_to_block() on error path

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Averin commit 6bdc9977fcdedf47118d2caf7270a19f4b6d8a8f upstream. Fixes: 3f2571c1f91f ("ext4: factor out xattr moving") Fixes: 6dd4ee7cab7e ("ext4: Expand extra_inodes space per ...") Re

[PATCH 4.19 153/205] kdb: use correct pointer when btc calls btt

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit dded2e159208a9edc21dd5c5f583afa28d378d39 upstream. On a powerpc 8xx, 'btc' fails as follows: Entering kdb (current=0x(ptrval), pid 282) due to Keyboard Entry kdb> btc

[PATCH 4.19 102/205] ocfs2: free up write context when direct IO failed

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Wengang Wang commit 5040f8df56fb90c7919f1c9b0b6e54c843437456 upstream. The write context should also be freed even when direct IO failed. Otherwise a memory leak is introduced and entries rema

[PATCH 4.19 142/205] ext4: fix buffer leak in ext4_xattr_get_block() on error path

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Averin commit ecaaf408478b6fb4d9986f9b6652f3824e374f4c upstream. Fixes: dec214d00e0d ("ext4: xattr inode deduplication") Signed-off-by: Vasily Averin Signed-off-by: Theodore Ts'o Cc:

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