[PATCH 4.14 05/74] tools/headers: Sync objtool UAPI header

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ingo Molnar commit a356d2ae50790f49858ebed35da9e206336fafee upstream. objtool grew this new warning: Warning: synced file at 'tools/objtool/arch/x86/include/asm/inat.h'

[PATCH 4.14 05/74] tools/headers: Sync objtool UAPI header

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ingo Molnar commit a356d2ae50790f49858ebed35da9e206336fafee upstream. objtool grew this new warning: Warning: synced file at 'tools/objtool/arch/x86/include/asm/inat.h' differs from

[PATCH 4.14 08/74] x86/insn-eval: Add utility functions to get segment selector

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Neri commit 32d0b95300db03c2b23b2ea2c94769a4a138e79d upstream. [note, only the inat.h portion, to get objtool back in sync - gregkh]

[PATCH 4.14 08/74] x86/insn-eval: Add utility functions to get segment selector

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Neri commit 32d0b95300db03c2b23b2ea2c94769a4a138e79d upstream. [note, only the inat.h portion, to get objtool back in sync - gregkh] b0caa8c8c6bbc422bc3c32b64852d6d618f32b49 Mon Sep

[PATCH 4.14 10/74] x86/mm/dump_pagetables: Check PAGE_PRESENT for real

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit c05344947b37f7cda726e802457370bc6eac4d26 upstream. The check for a present page in printk_prot(): if (!pgprot_val(prot)) {

[PATCH 4.14 10/74] x86/mm/dump_pagetables: Check PAGE_PRESENT for real

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit c05344947b37f7cda726e802457370bc6eac4d26 upstream. The check for a present page in printk_prot(): if (!pgprot_val(prot)) { /* Not present */ is

[PATCH 4.14 07/74] x86/decoder: Fix and update the opcodes map

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap commit f5b5fab1780c98b74526dbac527574bd02dc16f8 upstream Update x86-opcode-map.txt based on the October 2017 Intel SDM publication. Fix INVPID to INVVPID.

[PATCH 4.14 06/74] objtool: Fix 64-bit build on 32-bit host

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 14c47b54b0d9389e3ca0718e805cdd90c5a4303a upstream. The new ORC unwinder breaks the build of a 64-bit kernel on a 32-bit host. Building the kernel

[PATCH 4.14 07/74] x86/decoder: Fix and update the opcodes map

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap commit f5b5fab1780c98b74526dbac527574bd02dc16f8 upstream Update x86-opcode-map.txt based on the October 2017 Intel SDM publication. Fix INVPID to INVVPID. Add UD0 and UD1

[PATCH 4.14 06/74] objtool: Fix 64-bit build on 32-bit host

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 14c47b54b0d9389e3ca0718e805cdd90c5a4303a upstream. The new ORC unwinder breaks the build of a 64-bit kernel on a 32-bit host. Building the kernel on a i386 or x32 host

[PATCH 4.14 21/74] x86/microcode: Dont abuse the TLB-flush interface

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 23cb7d46f371844c004784ad9552a57446f73e5a upstream. Commit: ec400ddeff20 ("x86/microcode_intel_early.c: Early update ucode on Intel's CPU") ...

[PATCH 4.14 21/74] x86/microcode: Dont abuse the TLB-flush interface

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 23cb7d46f371844c004784ad9552a57446f73e5a upstream. Commit: ec400ddeff20 ("x86/microcode_intel_early.c: Early update ucode on Intel's CPU") ... grubbed into tlbflush

[PATCH 4.14 20/74] x86/uv: Use the right TLB-flush API

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 3e46e0f5ee3643a1239be9046c7ba6c66ca2b329 upstream. Since uv_flush_tlb_others() implements flush_tlb_others() which is about flushing user mappings,

[PATCH 4.14 20/74] x86/uv: Use the right TLB-flush API

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 3e46e0f5ee3643a1239be9046c7ba6c66ca2b329 upstream. Since uv_flush_tlb_others() implements flush_tlb_others() which is about flushing user mappings, we should use

[PATCH 4.14 22/74] x86/mm: Use __flush_tlb_one() for kernel memory

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit a501686b2923ce6f2ff2b1d0d50682c6411baf72 upstream. __flush_tlb_single() is for user mappings, __flush_tlb_one() for kernel mappings.

[PATCH 4.14 22/74] x86/mm: Use __flush_tlb_one() for kernel memory

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit a501686b2923ce6f2ff2b1d0d50682c6411baf72 upstream. __flush_tlb_single() is for user mappings, __flush_tlb_one() for kernel mappings. Signed-off-by: Peter Zijlstra

[PATCH 4.14 23/74] x86/mm: Remove superfluous barriers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit b5fc6d943808b570bdfbec80f40c6b3855f1c48b upstream. atomic64_inc_return() already implies smp_mb() before and after. Signed-off-by: Peter Zijlstra

[PATCH 4.14 23/74] x86/mm: Remove superfluous barriers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit b5fc6d943808b570bdfbec80f40c6b3855f1c48b upstream. atomic64_inc_return() already implies smp_mb() before and after. Signed-off-by: Peter Zijlstra (Intel)

[PATCH 4.14 26/74] x86/mm: Remove hard-coded ASID limit checks

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Hansen commit cb0a9144a744e55207e24dcef812f05cd15a499a upstream. First, it's nice to remove the magic numbers. Second, PAGE_TABLE_ISOLATION is going to

Re: [PATCH] PCI: exynos: remove the deprecated phy codes

On Wednesday, December 27, 2017 1:43 AM, Jaehoon Chung wrote: > > pci-exynos had updated to use the PHY framework. > (drivers/phy/samsung/phy-exynos-pcie.c) > Removed the depreccated codes relevant to phy in pci-exynos.c. > Instead, use the phy-exynos-pcie.c file. > > Modified the binding

[PATCH 4.14 26/74] x86/mm: Remove hard-coded ASID limit checks

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Hansen commit cb0a9144a744e55207e24dcef812f05cd15a499a upstream. First, it's nice to remove the magic numbers. Second, PAGE_TABLE_ISOLATION is going to consume half of the available

Re: [PATCH] PCI: exynos: remove the deprecated phy codes

On Wednesday, December 27, 2017 1:43 AM, Jaehoon Chung wrote: > > pci-exynos had updated to use the PHY framework. > (drivers/phy/samsung/phy-exynos-pcie.c) > Removed the depreccated codes relevant to phy in pci-exynos.c. > Instead, use the phy-exynos-pcie.c file. > > Modified the binding

[PATCH 4.14 27/74] x86/mm: Put MMU to hardware ASID translation in one place

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Hansen commit dd95f1a4b5ca904c78e6a097091eb21436478abb upstream. There are effectively two ASID types: 1. The one stored in the mmu_context that goes from

[PATCH 4.14 11/74] x86/mm/dump_pagetables: Make the address hints correct and readable

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 146122e24bdf208015d629babba673e28d090709 upstream. The address hints are a trainwreck. The array entry numbers have to kept magically in sync with

[PATCH 4.14 27/74] x86/mm: Put MMU to hardware ASID translation in one place

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Hansen commit dd95f1a4b5ca904c78e6a097091eb21436478abb upstream. There are effectively two ASID types: 1. The one stored in the mmu_context that goes from 0..5 2. The one programmed

[PATCH 4.14 11/74] x86/mm/dump_pagetables: Make the address hints correct and readable

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 146122e24bdf208015d629babba673e28d090709 upstream. The address hints are a trainwreck. The array entry numbers have to kept magically in sync with the actual hints,

[PATCH 4.14 35/74] crypto: skcipher - set walk.iv for zero-length inputs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 2b4f27c36bcd46e820ddb9a8e6fe6a63fa4250b8 upstream. All the ChaCha20 algorithms as well as the ARM bit-sliced AES-XTS algorithms call

[PATCH 4.14 35/74] crypto: skcipher - set walk.iv for zero-length inputs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 2b4f27c36bcd46e820ddb9a8e6fe6a63fa4250b8 upstream. All the ChaCha20 algorithms as well as the ARM bit-sliced AES-XTS algorithms call skcipher_walk_virt(), then access the

[PATCH 4.14 31/74] init: Invoke init_espfix_bsp() from mm_init()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 613e396bc0d4c7604fba23256644e78454c68cf6 upstream. init_espfix_bsp() needs to be invoked before the page table isolation initialization. Move it

[PATCH 4.14 33/74] ACPI: APEI / ERST: Fix missing error handling in erst_reader()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit bb82e0b4a7e96494f0c1004ce50cec3d7b5fb3d1 upstream. The commit f6f828513290 ("pstore: pass allocated memory region back to caller") changed the check of the

[PATCH 4.14 31/74] init: Invoke init_espfix_bsp() from mm_init()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 613e396bc0d4c7604fba23256644e78454c68cf6 upstream. init_espfix_bsp() needs to be invoked before the page table isolation initialization. Move it into mm_init() which is

[PATCH 4.14 33/74] ACPI: APEI / ERST: Fix missing error handling in erst_reader()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit bb82e0b4a7e96494f0c1004ce50cec3d7b5fb3d1 upstream. The commit f6f828513290 ("pstore: pass allocated memory region back to caller") changed the check of the return value

[PATCH 4.14 36/74] crypto: mcryptd - protect the per-CPU queue with a lock

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 9abffc6f2efe46c3564c04312e52e07622d40e51 upstream. mcryptd_enqueue_request() grabs the per-CPU queue struct and protects access to it

[PATCH 4.14 36/74] crypto: mcryptd - protect the per-CPU queue with a lock

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 9abffc6f2efe46c3564c04312e52e07622d40e51 upstream. mcryptd_enqueue_request() grabs the per-CPU queue struct and protects access to it with disabled

[PATCH 4.14 38/74] crypto: af_alg - fix race accessing cipher request

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stephan Mueller commit d53c5135792319e095bb126bc43b2ee98586f7fe upstream. When invoking an asynchronous cipher operation, the invocation of the callback may be performed

[PATCH 4.14 38/74] crypto: af_alg - fix race accessing cipher request

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stephan Mueller commit d53c5135792319e095bb126bc43b2ee98586f7fe upstream. When invoking an asynchronous cipher operation, the invocation of the callback may be performed before the subsequent

[PATCH 4.14 39/74] mfd: cros ec: spi: Dont send first message too soon

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jon Hunter commit 15d8374874ded0bec37ef27f8301a6d54032c0e5 upstream. On the Tegra124 Nyan-Big chromebook the very first SPI message sent to the EC is failing. The Tegra

[PATCH 4.14 39/74] mfd: cros ec: spi: Dont send first message too soon

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jon Hunter commit 15d8374874ded0bec37ef27f8301a6d54032c0e5 upstream. On the Tegra124 Nyan-Big chromebook the very first SPI message sent to the EC is failing. The Tegra SPI driver configures

[PATCH 4.14 14/74] arch, mm: Allow arch_dup_mmap() to fail

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit c10e83f598d08046dd1ebc8360d4bb12d802d51b upstream. In order to sanitize the LDT initialization on x86 arch_dup_mmap() must be allowed to fail. Fix

[PATCH 4.14 42/74] ALSA: rawmidi: Avoid racy info ioctl via ctl device

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit c1cfd9025cc394fd137a01159d74335c5ac978ce upstream. The rawmidi also allows to obtaining the information via ioctl of ctl API. It means that user can issue

[PATCH 4.14 14/74] arch, mm: Allow arch_dup_mmap() to fail

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit c10e83f598d08046dd1ebc8360d4bb12d802d51b upstream. In order to sanitize the LDT initialization on x86 arch_dup_mmap() must be allowed to fail. Fix up all instances.

[PATCH 4.14 42/74] ALSA: rawmidi: Avoid racy info ioctl via ctl device

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit c1cfd9025cc394fd137a01159d74335c5ac978ce upstream. The rawmidi also allows to obtaining the information via ioctl of ctl API. It means that user can issue an ioctl to the

[PATCH 4.14 13/74] x86/vsyscall/64: Warn and fail vsyscall emulation in NATIVE mode

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 4831b779403a836158917d59a7ca880483c67378 upstream. If something goes wrong with pagetable setup, vsyscall=native will accidentally fall back to

[PATCH 4.14 13/74] x86/vsyscall/64: Warn and fail vsyscall emulation in NATIVE mode

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 4831b779403a836158917d59a7ca880483c67378 upstream. If something goes wrong with pagetable setup, vsyscall=native will accidentally fall back to emulation. Make it warn

[PATCH 4.14 17/74] x86/mm/64: Improve the memory map documentation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 5a7ccf4754fb3660569a6de52ba7f7fc3dfaf280 upstream. The old docs had the vsyscall range wrong and were missing the fixmap. Fix both. There used to be 8

[PATCH 4.14 17/74] x86/mm/64: Improve the memory map documentation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 5a7ccf4754fb3660569a6de52ba7f7fc3dfaf280 upstream. The old docs had the vsyscall range wrong and were missing the fixmap. Fix both. There used to be 8 MB reserved for

[PATCH 4.14 18/74] x86/doc: Remove obvious weirdnesses from the x86 MM layout documentation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit e8ffe96e5933d417195268478479933d56213a3f upstream. Signed-off-by: Peter Zijlstra (Intel) Signed-off-by: Thomas Gleixner

[PATCH 4.14 18/74] x86/doc: Remove obvious weirdnesses from the x86 MM layout documentation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit e8ffe96e5933d417195268478479933d56213a3f upstream. Signed-off-by: Peter Zijlstra (Intel) Signed-off-by: Thomas Gleixner Cc: Andy Lutomirski Cc: Boris Ostrovsky Cc:

[PATCH 4.14 44/74] ALSA: hda - Add vendor id for Cannonlake HDMI codec

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Guneshwor Singh commit 2b4584d00a6bc02b63ab3c7213060d41a74bdff1 upstream. Cannonlake HDMI codec has the same nid as Geminilake. This adds the codec entry for it.

[PATCH 4.14 44/74] ALSA: hda - Add vendor id for Cannonlake HDMI codec

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Guneshwor Singh commit 2b4584d00a6bc02b63ab3c7213060d41a74bdff1 upstream. Cannonlake HDMI codec has the same nid as Geminilake. This adds the codec entry for it. Signed-off-by: Guneshwor

[PATCH 4.14 55/74] spi: a3700: Fix clk prescaling for coefficient over 15

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maxime Chevallier commit 251c201bf4f8b5bf4f1ccb4f8920eed2e1f57580 upstream. The Armada 3700 SPI controller has 2 ranges of prescaler coefficients. One ranging from

[PATCH 4.14 55/74] spi: a3700: Fix clk prescaling for coefficient over 15

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maxime Chevallier commit 251c201bf4f8b5bf4f1ccb4f8920eed2e1f57580 upstream. The Armada 3700 SPI controller has 2 ranges of prescaler coefficients. One ranging from 0 to 15 by steps of 1, and

[PATCH 4.14 56/74] pinctrl: cherryview: Mask all interrupts on Intel_Strago based systems

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mika Westerberg commit d2b3c353595a855794f8b9df5b5bdbe8deb0c413 upstream. Guenter Roeck reported an interrupt storm on a prototype system which is based on

[PATCH 4.14 56/74] pinctrl: cherryview: Mask all interrupts on Intel_Strago based systems

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mika Westerberg commit d2b3c353595a855794f8b9df5b5bdbe8deb0c413 upstream. Guenter Roeck reported an interrupt storm on a prototype system which is based on Cyan Chromebook. The root cause

[PATCH 4.14 58/74] KVM: arm/arm64: Fix HYP unmapping going off limits

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 7839c672e58bf62da8f2f0197fefb442c02ba1dd upstream. When we unmap the HYP memory, we try to be clever and unmap one PGD at a time. If we start with a

[PATCH 4.14 58/74] KVM: arm/arm64: Fix HYP unmapping going off limits

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 7839c672e58bf62da8f2f0197fefb442c02ba1dd upstream. When we unmap the HYP memory, we try to be clever and unmap one PGD at a time. If we start with a non-PGD aligned

[PATCH 4.14 65/74] powerpc/perf: Dereference BHRB entries safely

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ravi Bangoria commit f41d84dddc66b164ac16acf3f584c276146f1c48 upstream. It's theoretically possible that branch instructions recorded in BHRB (Branch History

[PATCH 4.14 65/74] powerpc/perf: Dereference BHRB entries safely

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ravi Bangoria commit f41d84dddc66b164ac16acf3f584c276146f1c48 upstream. It's theoretically possible that branch instructions recorded in BHRB (Branch History Rolling Buffer) entries have

[PATCH 4.14 32/74] x86/cpu_entry_area: Prevent wraparound in setup_cpu_entry_area_ptes() on 32bit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit f6c4fd506cb626e4346aa81688f255e593a7c5a0 upstream. The loop which populates the CPU entry area PMDs can wrap around on 32bit machines when the

[PATCH 4.14 64/74] clk: sunxi: sun9i-mmc: Implement reset callback for reset controls

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 61d2f2a05765a5f57149efbd93e3e81a83cbc2c1 upstream. Our MMC host driver now issues a reset, instead of just deasserting the reset control, since commit

[PATCH 4.14 64/74] clk: sunxi: sun9i-mmc: Implement reset callback for reset controls

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 61d2f2a05765a5f57149efbd93e3e81a83cbc2c1 upstream. Our MMC host driver now issues a reset, instead of just deasserting the reset control, since commit c34eda69ad4c ("mmc:

[PATCH 4.14 32/74] x86/cpu_entry_area: Prevent wraparound in setup_cpu_entry_area_ptes() on 32bit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit f6c4fd506cb626e4346aa81688f255e593a7c5a0 upstream. The loop which populates the CPU entry area PMDs can wrap around on 32bit machines when the number of CPUs is small.

[PATCH 4.14 66/74] drm/i915: Flush pending GTT writes before unbinding

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit 2797c4a11f373b2545c2398ccb02e362ee66a142 upstream. >From the shrinker paths, we want to relinquish the GPU and GGTT access to the object,

[PATCH 4.14 66/74] drm/i915: Flush pending GTT writes before unbinding

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit 2797c4a11f373b2545c2398ccb02e362ee66a142 upstream. >From the shrinker paths, we want to relinquish the GPU and GGTT access to the object, releasing the backing storage

[PATCH 4.14 69/74] libnvdimm, btt: Fix an incompatibility in the log layout

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vishal Verma commit 24e3a7fb60a9187e5df90e5fa655ffc94b9c4f77 upstream. Due to a spec misinterpretation, the Linux implementation of the BTT log area had different

[PATCH 4.14 69/74] libnvdimm, btt: Fix an incompatibility in the log layout

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vishal Verma commit 24e3a7fb60a9187e5df90e5fa655ffc94b9c4f77 upstream. Due to a spec misinterpretation, the Linux implementation of the BTT log area had different padding scheme from other

[PATCH 4.14 70/74] libnvdimm, pfn: fix start_pad handling for aligned namespaces

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 19deaa217bc04e83b59b5e8c8229eb0e53ad9efc upstream. The alignment checks at pfn driver startup fail to properly account for the 'start_pad' in the

[PATCH 4.14 70/74] libnvdimm, pfn: fix start_pad handling for aligned namespaces

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 19deaa217bc04e83b59b5e8c8229eb0e53ad9efc upstream. The alignment checks at pfn driver startup fail to properly account for the 'start_pad' in the case where the namespace

[PATCH 4.14 71/74] net: mvneta: clear interface link status on port disable

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yelena Krivosheev commit 4423c18e466afdfb02a36ee8b9f901d144b3c607 upstream. When port connect to PHY in polling mode (with poll interval 1 sec), port and phy link status

[PATCH 4.14 71/74] net: mvneta: clear interface link status on port disable

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yelena Krivosheev commit 4423c18e466afdfb02a36ee8b9f901d144b3c607 upstream. When port connect to PHY in polling mode (with poll interval 1 sec), port and phy link status must be synchronize

[PATCH 4.14 46/74] ALSA: usb-audio: Fix the missing ctl name suffix at parsing SU

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 5a15f289ee87eaf33f13f08a4909ec99d837ec5f upstream. The commit 89b89d121ffc ("ALSA: usb-audio: Add check return value for usb_string()") added the check of

[PATCH 4.14 46/74] ALSA: usb-audio: Fix the missing ctl name suffix at parsing SU

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 5a15f289ee87eaf33f13f08a4909ec99d837ec5f upstream. The commit 89b89d121ffc ("ALSA: usb-audio: Add check return value for usb_string()") added the check of the return value

[PATCH 4.14 74/74] Revert "ipmi_si: fix memory leak on new_smi"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: John Einar Reitan This reverts commit c97e41076a298dbc4e910c33048e553658388eed, which incorrectly was taken from upstream c0a32fe13cd323ca9420500b16fd69589c9ba91e. The

[PATCH 4.14 47/74] PCI / PM: Force devices to D0 in pci_pm_thaw_noirq()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 5839ee7389e893a31e4e3c9cf17b50d14103c902 upstream. It is incorrect to call pci_restore_state() for devices in low-power states (D1-D3), as

[PATCH 4.14 47/74] PCI / PM: Force devices to D0 in pci_pm_thaw_noirq()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 5839ee7389e893a31e4e3c9cf17b50d14103c902 upstream. It is incorrect to call pci_restore_state() for devices in low-power states (D1-D3), as that involves the

[PATCH 4.14 74/74] Revert "ipmi_si: fix memory leak on new_smi"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: John Einar Reitan This reverts commit c97e41076a298dbc4e910c33048e553658388eed, which incorrectly was taken from upstream c0a32fe13cd323ca9420500b16fd69589c9ba91e. The referenced memory leak

[PATCH 4.14 50/74] parisc: Align os_hpmc_size on word boundary

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 0ed9d3de5f8f97e6efd5ca0e3377cab5f0451ead upstream. The os_hpmc_size variable sometimes wasn't aligned at word boundary and thus triggered the unaligned

[PATCH 4.14 50/74] parisc: Align os_hpmc_size on word boundary

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 0ed9d3de5f8f97e6efd5ca0e3377cab5f0451ead upstream. The os_hpmc_size variable sometimes wasn't aligned at word boundary and thus triggered the unaligned fault handler at

[PATCH 4.14 49/74] block-throttle: avoid double charge

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Shaohua Li commit 111be883981748acc9a56e855c8336404a8e787c upstream. If a bio is throttled and split after throttling, the bio could be resubmited and enters the throttling

[PATCH 4.14 73/74] net: mvneta: eliminate wrong call to handle rx descriptor error

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yelena Krivosheev commit 2eecb2e04abb62ef8ea7b43e1a46bdb5b99d1bf8 upstream. There are few reasons in mvneta_rx_swbm() function when received packet is dropped.

[PATCH 4.14 49/74] block-throttle: avoid double charge

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Shaohua Li commit 111be883981748acc9a56e855c8336404a8e787c upstream. If a bio is throttled and split after throttling, the bio could be resubmited and enters the throttling again. This will

[PATCH 4.14 73/74] net: mvneta: eliminate wrong call to handle rx descriptor error

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yelena Krivosheev commit 2eecb2e04abb62ef8ea7b43e1a46bdb5b99d1bf8 upstream. There are few reasons in mvneta_rx_swbm() function when received packet is dropped. mvneta_rx_error() should be

[PATCH 4.14 52/74] parisc: Hide Diva-built-in serial aux and graphics card

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit bcf3f1752a622f1372d3252d0fea8855d89812e7 upstream. Diva GSP card has built-in serial AUX port and ATI graphic card which simply don't work and which both

[PATCH 4.14 51/74] parisc: Fix indenting in puts()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 203c110b39a89b48156c7450504e454fedb7f7f6 upstream. Static analysis tools complain that we intended to have curly braces around this indent block. In this

[PATCH 4.14 52/74] parisc: Hide Diva-built-in serial aux and graphics card

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit bcf3f1752a622f1372d3252d0fea8855d89812e7 upstream. Diva GSP card has built-in serial AUX port and ATI graphic card which simply don't work and which both don't have

[PATCH 4.14 51/74] parisc: Fix indenting in puts()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 203c110b39a89b48156c7450504e454fedb7f7f6 upstream. Static analysis tools complain that we intended to have curly braces around this indent block. In this case this

[PATCH 4.14 43/74] ALSA: hda/realtek - Fix Dell AIO LineOut issue

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit 9226665159f0367ad08bc7d5dd194aeadb90316f upstream. Dell AIO had LineOut jack. Add LineOut verb into this patch. [ Additional notes: the ALC274

Re: v4.14.9 BUG, regression

On Tue, Dec 26, 2017 at 03:00:55AM +0100, Petr Janecek wrote: > Hi, >the machine started dying reliably shortly after boot after upgrading > to 4.14.9 from 4.14.8. Debian stretch, xfs on md raid10, btrfs. > > > [ 230.855352] BUG: unable to handle kernel paging request at 00010001 >

[PATCH 4.14 43/74] ALSA: hda/realtek - Fix Dell AIO LineOut issue

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit 9226665159f0367ad08bc7d5dd194aeadb90316f upstream. Dell AIO had LineOut jack. Add LineOut verb into this patch. [ Additional notes: the ALC274 codec seems requiring the

Re: v4.14.9 BUG, regression

On Tue, Dec 26, 2017 at 03:00:55AM +0100, Petr Janecek wrote: > Hi, >the machine started dying reliably shortly after boot after upgrading > to 4.14.9 from 4.14.8. Debian stretch, xfs on md raid10, btrfs. > > > [ 230.855352] BUG: unable to handle kernel paging request at 00010001 >

[PATCH 4.14 48/74] block: unalign call_single_data in struct request

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jens Axboe commit 4ccafe032005e9b96acbef2e389a4de5b1254add upstream. A previous change blindly added massive alignment to the call_single_data structure in struct request.

[PATCH 4.14 48/74] block: unalign call_single_data in struct request

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jens Axboe commit 4ccafe032005e9b96acbef2e389a4de5b1254add upstream. A previous change blindly added massive alignment to the call_single_data structure in struct request. This ballooned it

[PATCH 4.14 67/74] drm/sun4i: Fix error path handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maxime Ripard commit 92411f6d7f1afcc95e54295d40e96a75385212ec upstream. The commit 4c7f16d14a33 ("drm/sun4i: Fix TCON clock and regmap initialization

[PATCH 4.14 63/74] kvm: x86: fix RSM when PCID is non-zero

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit fae1a3e775cca8c3a9e0eb34443b310871a15a92 upstream. rsm_load_state_64() and rsm_enter_protected_mode() load CR3, then CR4 & ~PCIDE, then CR0, then

[PATCH 4.14 67/74] drm/sun4i: Fix error path handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maxime Ripard commit 92411f6d7f1afcc95e54295d40e96a75385212ec upstream. The commit 4c7f16d14a33 ("drm/sun4i: Fix TCON clock and regmap initialization sequence") moved a bunch of logic around,

[PATCH 4.14 63/74] kvm: x86: fix RSM when PCID is non-zero

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit fae1a3e775cca8c3a9e0eb34443b310871a15a92 upstream. rsm_load_state_64() and rsm_enter_protected_mode() load CR3, then CR4 & ~PCIDE, then CR0, then CR4. However, setting

[PATCH 4.14 72/74] net: mvneta: use proper rxq_number in loop on rx queues

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yelena Krivosheev commit ca5902a6547f662419689ca28b3c29a772446caa upstream. When adding the RX queue association with each CPU, a typo was made in the

[PATCH 4.14 68/74] libnvdimm, dax: fix 1GB-aligned namespaces vs physical misalignment

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 41fce90f26333c4fa82e8e43b9ace86c4e8a0120 upstream. The following namespace configuration attempt: # ndctl create-namespace -e namespace0.0

[PATCH 4.14 72/74] net: mvneta: use proper rxq_number in loop on rx queues

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yelena Krivosheev commit ca5902a6547f662419689ca28b3c29a772446caa upstream. When adding the RX queue association with each CPU, a typo was made in the mvneta_cleanup_rxqs() function. This

[PATCH 4.14 68/74] libnvdimm, dax: fix 1GB-aligned namespaces vs physical misalignment

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 41fce90f26333c4fa82e8e43b9ace86c4e8a0120 upstream. The following namespace configuration attempt: # ndctl create-namespace -e namespace0.0 -m devdax -a 1G -f

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