[PATCH 4.15 030/163] ARM: dts: nomadik: add interrupt-parent for clcd

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit e8bfa0422469cdfc86be3f525f621b1d44d2481b upstream. The clcd device is lacking an interrupt-parent property, which makes the interrupt unusable and shows up as a warning wi

Re: [PATCH V4 1/5] perf/x86/intel: Fix event update for auto-reload

On Wed, Feb 21, 2018 at 08:43:47AM -0500, Liang, Kan wrote: > Right, I forgot that the drain_pebs_core() also has auto_reload support. > Sorry for that. > I will re-send all patches. No need, already collected the lot. Thanks!

[PATCH 4.15 009/163] kselftest: fix OOM in memory compaction test

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 4c1baad223906943b595a887305f2e8124821dad upstream. Running the compaction_test sometimes results in out-of-memory failures. When I debugged this, it turned out that the co

[PATCH 4.15 019/163] powerpc/radix: Remove trace_tlbie call from radix__flush_tlb_all

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Mahesh Salgaonkar commit 8d81296cfcce89013a714feb8d25004a156f8181 upstream. radix__flush_tlb_all() is called only in kexec path in real mode and any tracepoints at this stage will make kexec t

[PATCH 4.15 007/163] IB/core: Avoid a potential OOPs for an unused optional parameter

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Michael J. Ruhl commit 2ff124d597c2df8696169ce0006fc974c49a4569 upstream. The ev_file is an optional parameter for CQ creation. If the parameter is not passed, the ev_file pointer will be NULL

[PATCH 4.15 004/163] IB/mlx4: Fix incorrectly releasing steerable UD QPs when have only ETH ports

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein commit 852f6927594d0d3e8632c889b2ab38cbc46476ad upstream. Allocating steerable UD QPs depends on having at least one IB port, while releasing those QPs does not. As a result,

Re: [GIT PULL] arm64 spectre and meltdown mitigations for -stable

On Wed, Feb 21, 2018 at 01:43:34PM +, Ard Biesheuvel wrote: > On 21 February 2018 at 12:53, Greg KH wrote: > > On Fri, Feb 09, 2018 at 01:48:11PM +, Will Deacon wrote: > >> Hi Greg, > >> > >> I've put together a tag which includes all of the upstream arm64 spectre > >> and > >> meltdown m

[PATCH 4.15 002/163] IB/umad: Fix use of unprotected device pointer

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein commit f23a5350e43c810ca36b26d4ed4ecd9a08686f47 upstream. The ib_write_umad() is protected by taking the umad file mutex. However, it accesses file->port->ib_dev -- which is p

Re: [PATCH v5 1/3] sched: Stop nohz stats when decayed

On 02/21/2018 01:13 PM, Valentin Schneider wrote: > On 02/16/2018 01:44 PM, Vincent Guittot wrote: >> On 16 February 2018 at 13:13, Valentin Schneider >> wrote: >>> On 02/14/2018 03:26 PM, Vincent Guittot wrote: > BTW, with the current set on Peter's sched/testing, update_nohz_stats() > is called

[PATCH 4.15 016/163] mwifiex: resolve reset vs. remove()/shutdown() deadlocks

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit a64e7a79dd6030479caad603c8d78e6c9c14904f upstream. Commit b014e96d1abb ("PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()") resolves races between d

[PATCH v3] arm64: Add support for new control bits CTR_EL0.DIC and CTR_EL0.IDC

The DCache clean & ICache invalidation requirements for instructions to be data coherence are discoverable through new fields in CTR_EL0. The following two control bits DIC and IDC were defined for this purpose. No need to perform point of unification cache maintenance operations from software on s

[PATCH 4.15 010/163] RDMA/rxe: Fix a race condition related to the QP error state

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 6f301e06de4cf9ab7303f5acd43e64fcd4aa04be upstream. The following sequence: * Change queue pair state into IB_QPS_ERR. * Post a work request on the queue pair. Triggers

[PATCH 4.15 012/163] RDMA/rxe: Fix rxe_qp_cleanup()

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit bb3ffb7ad48a21e98a5c64eb21103a74fd9f03f6 upstream. rxe_qp_cleanup() can sleep so it must be run in thread context and not in atomic context. This patch avoids that the f

[PATCH 4.15 011/163] RDMA/rxe: Fix a race condition in rxe_requester()

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 65567e41219888feec72fee1de98ccf1efbbc16d upstream. The rxe driver works as follows: * The send queue, receive queue and completion queues are implemented as circular b

Re: [PATCH]sched: completion: use bool in try_wait_for_completion

On Wed, Feb 21, 2018 at 02:28:54PM +0100, Peter Zijlstra wrote: > On Wed, Feb 21, 2018 at 06:24:07PM +0530, gaurav jindal wrote: > > Variable ret in try_wait_for_completion can have only true/false values. > > Since > > the return type of the function is also bool, variable ret should have data >

[PATCH 4.14 152/167] x86/mm, mm/hwpoison: Dont unconditionally unmap kernel 1:1 pages

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit fd0e786d9d09024f67bd71ec094b110237dc3840 upstream. In the following commit: ce0fa3e56ad2 ("x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison pages")

[PATCH 1/2] ARM: irqchip: stm32: Optimizes and cleans up stm32-exti irq_domain

- allocates generic chip with handle_simple_irq which simplifies irq_domain_ops.alloc callback - removes ack register from generic chip which is not used for handle_simple_irq as acking is done in a chained handler - removes unneeded irq_domain_ops.xlate call

[PATCH 0/2] Optimizes, cleans up and enhances stm32-exti irq hierarchy

- optimizes and cleans up stm32-exti irq domain - optimizes and enhances stm32gpio irq chip Radoslaw Pietrzyk (2): ARM: irqchip: stm32: Optimizes and cleans up stm32-exti irq_domain ARM: pinctrl: stm32: Optimizes and enhances stm32gpio irqchip drivers/irqchip/irq-stm32-exti.c | 10 +

Re: [PATCH] kconfig: Print reverse dependencies in groups

On Wed, Feb 21, 2018 at 12:17 PM, Petr Vorel wrote: > Hi Masahiro, > >> > Signed-off-by: Masahiro Yamada >> Acked-by: Petr Vorel > Well, I'm not really the one to ack anything here, so please: > Reviewed-by: Petr Vorel > > Kind regards, > Petr Looks good to me too. Reviewed-by: Ulf Magnusson

[PATCH 4.14 143/167] ALSA: usb-audio: Fix UAC2 get_ctl request with a RANGE attribute

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill Marinushkin commit 447cae58cecd69392b74a4a42cd0ab9cabd816af upstream. The layout of the UAC2 Control request and response varies depending on the request type. With the current implemen

[PATCH 2/2] ARM: pinctrl: stm32: Optimizes and enhances stm32gpio irqchip

- removes unneeded irq_chip.irq_eoi callback - adds irq_chip.irq_set_wake callback for possible in the future GPIO wakeup Signed-off-by: Radoslaw Pietrzyk --- drivers/pinctrl/stm32/pinctrl-stm32.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers

[PATCH 4.14 151/167] usb: Move USB_UHCI_BIG_ENDIAN_* out of USB_SUPPORT

4.14-stable review patch. If anyone has any objections, please let me know. -- From: James Hogan commit ec897569ad7dbc6d595873a487c3fac23f463f76 upstream. Move the Kconfig symbols USB_UHCI_BIG_ENDIAN_MMIO and USB_UHCI_BIG_ENDIAN_DESC out of drivers/usb/host/Kconfig, which is c

[PATCH 4.14 148/167] ALSA: usb: add more device quirks for USB DSD devices

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Mack commit 7c74866baef1827e18f8269aec85030063520bd4 upstream. Add some more devices that need quirks to handle DSD modes correctly. Signed-off-by: Daniel Mack Reported-and-tested-by:

[PATCH 4.14 146/167] ALSA: hda/realtek: PCI quirk for Fujitsu U7x7

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jan-Marek Glogowski commit fdcc968a3b290407bcba9d4c90e2fba6d8d928f1 upstream. These laptops have a combined jack to attach headsets, the U727 on the left, the U757 on the right, but a headsets

[PATCH 4.14 167/167] ovl: hash directory inodes for fsnotify

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Amir Goldstein commit 31747eda41ef3c30c09c5c096b380bf54013746a upstream. fsnotify pins a watched directory inode in cache, but if directory dentry is released, new lookup will allocate a new d

Re: [PATCH 1/6] powerpc/mm/32: Use pfn_valid to check if pointer is in RAM

Hello Christophe, On Tue, Feb 20, 2018 at 06:45:09PM +0100, christophe leroy wrote: [...] > > - if (slab_is_available() && (p < virt_to_phys(high_memory)) && > > + if (slab_is_available() && pfn_valid(__phys_to_pfn(p)) && > > I'm not sure this is equivalent: > > high_memory = (void *) __va(m

[PATCH 4.14 163/167] mmc: sdhci-of-esdhc: disable SD clock for clock value 0

4.14-stable review patch. If anyone has any objections, please let me know. -- From: yangbo lu commit dd3f6983b4a468efca9e8caa0e2b4aa20946d801 upstream. SD clock should be disabled for clock value 0. It's not right to just return. This may cause failure of signal voltage switc

Re: metag build errors in mainline kernel

> Hmm.. ancient shelved toolchain. Perhaps this is the excuse we need to > say goodbye to arch/metag/... I too was wondering - that one day there will come a time when the toolkit will be too old and there will be no updates Graham

[PATCH 4.14 145/167] ALSA: hda/realtek - Enable Thinkpad Dock device for ALC298 platform

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit 61fcf8ece9b6b09450250c4ca40cc3b81a96a68d upstream. Thinkpad Dock device support for ALC298 platform. It need to use SSID for the quirk table. Because IdeaPad also has ALC29

[PATCH 4.14 162/167] media: r820t: fix r820t_write_reg for KASAN

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 16c3ada89cff9a8c2a0eea34ffa1aa20af3f6008 upstream. With CONFIG_KASAN, we get an overly long stack frame due to inlining the register access functions: drivers/media/tuner

[PATCH 4.14 160/167] arm: dts: mt2701: Add reset-cells

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Matthias Brugger commit ae72e95b5e4ded145bfc6926ad9457b74e3af41a upstream. The hifsys and ethsys needs the definition of the reset-cells property. Fix this. Reviewed-by: Rob Herring Signed-o

[PATCH 4.14 157/167] arm64: dts: msm8916: Add missing #phy-cells

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Andersson commit b0ab681285aa66064f2de5b74191c0cabba381ff upstream. Add a missing #phy-cells to the dsi-phy, to silence dtc warning. Cc: Archit Taneja Fixes: 305410ffd1b2 ("arm64: dts:

[PATCH 4.14 155/167] ARM: dts: exynos: fix RTC interrupt for exynos5410

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 5628a8ca14149ba4226e3bdce3a04c3b688435ad upstream. According to the comment added to exynos_dt_pmu_match[] in commit 8b283c025443 ("ARM: exynos4/5: convert pmu wakeup to s

[PATCH 4.14 154/167] Bluetooth: BT_HCIUART now depends on SERIAL_DEV_BUS

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 05e89fb576f580ac95e7a5d00bdb34830b09671a upstream. It is no longer possible to build BT_HCIUART into the kernel when SERIAL_DEV_BUS is a loadable module, even if none of t

[PATCH 4.14 144/167] ALSA: hda/realtek - Add headset mode support for Dell laptop

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit 40e2c4e5a7efcd50983aacbddd3c617e776018bf upstream. This platform had two Dmic and single Dmic. This update was for single Dmic. This commit was for two Dmic. Fixes: 75ee9

[PATCH 4.14 111/167] MIPS: Fix typo BIG_ENDIAN to CPU_BIG_ENDIAN

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Corentin Labbe commit 2e6522c565522a2e18409c315c49d78c8b74807b upstream. MIPS_GENERIC selects some options conditional on BIG_ENDIAN which does not exist. Replace BIG_ENDIAN with CPU_BIG_ENDI

Re: [PATCH 1/2] soc: qcom: rmtfs-mem: Add support for assigning memory to remote

Hi Bjorn, On 2/13/2018 7:07 AM, Bjorn Andersson wrote: On some platform the remote processor's memory map is not statically configured in TrustZone, so each memory region that is to be accessed by the remote needs a call into TrustZone to set up the remote's permissions. Implement this for the

[PATCH 4.14 141/167] mtd: nand: vf610: set correct ooblayout

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Agner commit ea56fb282368ea08c2a313af6b55cb597aec4db1 upstream. With commit 3cf32d180227 ("mtd: nand: vf610: switch to mtd_ooblayout_ops") the driver started to use the NAND cores defau

[PATCH 4.14 142/167] ALSA: hda - Fix headset mic detection problem for two Dell machines

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hui Wang commit 3f2f7c553d077be6a30cb96b2976a2c940bf5335 upstream. One of them has the codec of alc256 and the other one has the codec of alc289. Cc: Signed-off-by: Hui Wang Signed-off-by:

[PATCH 4.14 140/167] 9p/trans_virtio: discard zero-length reply

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kurz commit 26d99834f89e76514076d9cd06f61e56e6a509b8 upstream. When a 9p request is successfully flushed, the server is expected to just mark it as used without sending a 9p reply (ie, wi

[PATCH 4.14 139/167] Btrfs: fix unexpected -EEXIST when creating new inode

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo commit 900c9981680067573671ecc5cbfa7c5770be3a40 upstream. The highest objectid, which is assigned to new inode, is decided at the time of initializing fs roots. However, in cases where

[PATCH 4.14 136/167] Btrfs: fix extent state leak from tree log

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo commit 55237a5f2431a72435e3ed39e4306e973c0446b7 upstream. It's possible that btrfs_sync_log() bails out after one of the two btrfs_write_marked_extents() which convert extent state's st

[PATCH 4.14 131/167] target/iscsi: avoid NULL dereference in CHAP auth error path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Disseldorp commit ce512d79d0466a604793addb6b769d12ee326822 upstream. If chap_server_compute_md5() fails early, e.g. via CHAP_N mismatch, then crypto_free_shash() is called with a NULL po

[PATCH 4.14 134/167] Btrfs: fix deadlock in run_delalloc_nocow

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo commit e89166990f11c3f21e1649d760dd35f9e410321c upstream. @cur_offset is not set back to what it should be (@cow_start) if btrfs_next_leaf() returns something wrong, and the range [cow_

[PATCH 4.14 132/167] iscsi-target: make sure to wake up sleeping login worker

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit 1c130ae00b769a2e2df41bad3d6051ee8234b636 upstream. Mike Christie reports: Starting in 4.14 iscsi logins will fail around 50% of the time. Problem appears to be that

Re: [PATCH 2/2] perf, tools, stat: Reset ids counter when retrying events

Em Thu, Oct 05, 2017 at 07:00:29PM -0700, Andi Kleen escreveu: > From: Andi Kleen > > perf stat can retry opening events. After opening an file descriptor > it adds the ids to the ecsel. Each event keeps a running > count of ids. Ok, and that is done in perf_evlist__id_add() where we also add th

[PATCH 4.14 130/167] blk-wbt: account flush requests correctly

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jens Axboe commit 5235553d821433e1f4fa720fd025d2c4b7ee9994 upstream. Mikulas reported a workload that saw bad performance, and figured out what it was due to various other types of requests be

[PATCH 4.14 126/167] qxl: alloc & use shadow for dumb buffers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gerd Hoffmann commit 62676d10b483a2ff6e8b08c5e7c7d63a831343f5 upstream. This patch changes the way the primary surface is used for dumb framebuffers. Instead of configuring the bo itself as p

[PATCH 4.14 128/167] xprtrdma: Fix calculation of ri_max_send_sges

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chuck Lever commit 1179e2c27efe21167ec9d882b14becefba2ee990 upstream. Commit 16f906d66cd7 ("xprtrdma: Reduce required number of send SGEs") introduced the rpcrdma_ia::ri_max_send_sges field. T

[PATCH 4.14 107/167] ext4: save error to disk in __ext4_grp_locked_error()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Zhouyi Zhou commit 06f29cc81f0350261f59643a505010531130eea0 upstream. In the function __ext4_grp_locked_error(), __save_error_info() is called to save error info in super block block, but does

[PATCH 4.14 123/167] mpls, nospec: Sanitize array index in mpls_label_ok()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 3968523f855050b8195134da951b87c20bd66130 upstream. mpls_label_ok() validates that the 'platform_label' array index from a userspace netlink message payload is valid. Under

[PATCH 4.14 121/167] seq_file: fix incomplete reset on read from zero offset

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit cf5eebae2cd28d37581507668605f4d23cd7218d upstream. When resetting iterator on a zero offset we need to discard any data already in the buffer (count), and private state o

[PATCH 4.14 117/167] console/dummy: leave .con_font_get set to NULL

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Pitre commit 724ba8b30b044aa0d94b1cd374fc15806cdd6f18 upstream. When this method is set, the caller expects struct console_font fields to be properly initialized when it returns. Leave

Re: [PATCH v9 03/11] media: platform: Add Renesas CEU driver

On 02/21/18 13:29, Laurent Pinchart wrote: > Hi Hans, > > On Wednesday, 21 February 2018 14:03:24 EET Hans Verkuil wrote: >> On 02/19/18 17:59, Jacopo Mondi wrote: >>> Add driver for Renesas Capture Engine Unit (CEU). >>> >>> The CEU interface supports capturing 'data' (YUV422) and 'images' >>> (N

Re: [PATCH v2 01/21] lib/vsprintf: Print time and date in human readable format via %pt

On Wed, 2018-02-21 at 10:33 +0100, Geert Uytterhoeven wrote: > Hi Andy, > > On Tue, Feb 20, 2018 at 10:43 PM, Andy Shevchenko > wrote: > > There are users which print time and date represented by content of > > struct rtc_time in human readable format. > > > > Instead of open coding that each ti

[PATCH 4.14 118/167] rbd: whitelist RBD_FEATURE_OPERATIONS feature bit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit e573427a440fd67d3f522357d7ac901d59281948 upstream. This feature bit restricts older clients from performing certain maintenance operations against an image (e.g. clone, sna

[PATCH 4.14 115/167] PCI: keystone: Fix interrupt-controller-node lookup

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit eac56aa3bc8af3d9b9850345d0f2da9d83529134 upstream. Fix child-node lookup during initialisation which was using the wrong OF-helper and ended up searching the whole device t

Re: [PATCH v2 20/21] mk68/mac: Switch to use %ptR

On Wed, 2018-02-21 at 10:38 +0100, Geert Uytterhoeven wrote: > > + select PRINTK_PEXT_TIMEDATE > > Yeah, now you have to track whatever code uses the new %p extension... I don't like this. People had an opinion that 750+ bytes is way too much for tiny kernel configuration. -- Andy Shevch

[PATCH 4.14 068/167] selftests/x86: Clean up and document sscanf() usage

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit d8e92de8ef952bed88c56c7a44c02d8dcae0984e upstream. Replace a couple of magically connected buffer length literal constants with a common definition that makes their re

[PATCH 4.14 076/167] x86/speculation: Fix up array_index_nospec_mask() asm constraint

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit be3233fbfcb8f5acb6e3bcd0895c3ef9e100d470 upstream. Allow the compiler to handle @size as an immediate value or memory directly rather than allocating a register. Reported-

[PATCH 4.14 077/167] nospec: Move array_index_nospec() parameter checking into separate macro

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 8fa80c503b484ddc1abbd10c7cb2ab81f3824a50 upstream. For architectures providing their own implementation of array_index_mask_nospec() in asm/barrier.h, attempting to use WARN

[PATCH 4.14 073/167] objtool: Fix segfault in ignore_unreachable_insn()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit fe24e27128252c230a34a6c628da2bf1676781ea upstream. Peter Zijlstra's patch for converting WARN() to use UD2 triggered a bunch of false "unreachable instruction" warnings,

Re: [PATCH v2 01/21] lib/vsprintf: Print time and date in human readable format via %pt

> TBH, I don't see much consensus among developers on this topic. > I wouldn't like to send a new version until it would be a consensus. I would love to see the comments followed by an agreement from majority of people who are in Cc list here. -- Andy Shevchenko Intel Finland Oy

[PATCH] iio:dummy: Fix coding style in simple_dummy and evgen

This patch fixes the following checkpatch.pl warnings: drivers/iio/dummy/iio_simple_dummy.c:603: WARNING: Block comments should align the * on each line drivers/iio/dummy/iio_dummy_evgen.c:151: WARNING: Symbolic permissions 'S_IWUSR' are not preferred. Consider using octal permissions '0200'... dr

[PATCH 4.14 102/167] Revert "mmc: meson-gx: include tx phase in the tuning process"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jerome Brunet commit fe0e58048f005fdce315eb4d185e5c160be4ac01 upstream. This reverts commit 0a44697627d17a66d7dc98f17aeca07ca79c5c20. This commit was initially intended to fix problems with h

[PATCH 4.14 099/167] mbcache: initialize entry->e_referenced in mb_cache_entry_create()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Potapenko commit 3876bbe27d04b848750d5310a37d6b76b593f648 upstream. KMSAN reported use of uninitialized |entry->e_referenced| in a condition in mb_cache_shrink(): ==

[PATCH 4.14 071/167] selftests/x86: Do not rely on "int $0x80" in single_step_syscall.c

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 4105c69703cdeba76f384b901712c9397b04e9c2 upstream. On 64-bit builds, we should not rely on "int $0x80" working (it only does if CONFIG_IA32_EMULATION=y is enabled). To

[PATCH 4.14 095/167] arm64: Add missing Falkor part number for branch predictor hardening

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 16e574d762ac5512eb922ac0ac5eed360b7db9d8 upstream. References to CPU part number MIDR_QCOM_FALKOR were dropped from the mailing list patch due to mainline/arm64 branc

[PATCH 4.14 088/167] x86/cpu: Change type of x86_cache_size variable to unsigned int

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 24dbc6000f4b9b0ef5a9daecb161f1907733765a upstream. Currently, x86_cache_size is of type int, which makes no sense as we will never have a valid cache size equal or l

[PATCH 4.14 094/167] drm/ast: Load lut in crtc_commit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit 24b8ef699e8221d2b7f813adaab13eec053e1507 upstream. In the past the ast driver relied upon the fbdev emulation helpers to call ->load_lut at boot-up. But since commit b8e2

[PATCH 4.14 092/167] drm/qxl: unref cursor bo when finished with it

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ray Strode commit 16c6db3688734b27487a42d0c2a1062d0b2bad03 upstream. qxl_cursor_atomic_update allocs a bo for the cursor that it never frees up at the end of the function. This commit fixes t

[PATCH 4.14 089/167] x86/entry/64: Fix CR3 restore in paranoid_exit()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ingo Molnar commit e48657573481a5dff7cfdc3d57005c80aa816500 upstream. Josh Poimboeuf noticed the following bug: "The paranoid exit code only restores the saved CR3 when it switches back to

[PATCH 4.14 082/167] kmemcheck: rip it out

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Levin, Alexander (Sasha Levin) commit 4675ff05de2d76d167336b368bd07f3fef6ed5a6 upstream. Fix up makefiles, remove references, and git rm kmemcheck. Link: http://lkml.kernel.org/r/20171007030

[PATCH 4.14 070/167] selftests/x86: Do not rely on "int $0x80" in test_mremap_vdso.c

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 2cbc0d66de0480449c75636f55697c7ff3af61fc upstream. On 64-bit builds, we should not rely on "int $0x80" working (it only does if CONFIG_IA32_EMULATION=y is enabled). W

[PATCH 4.14 087/167] x86/spectre: Fix an error message

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 9de29eac8d2189424d81c0d840cd0469aa3d41c8 upstream. If i == ARRAY_SIZE(mitigation_options) then we accidentally print garbage from one space beyond the end of the mitigatio

[PATCH 4.14 083/167] kmemcheck: rip it out for real

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michal Hocko commit f335195adf043168ee69d78ea72ac3e30f0c57ce upstream. Commit 4675ff05de2d ("kmemcheck: rip it out") has removed the code but for some reason SPDX header stayed in place. This

[PATCH 4.14 084/167] x86/mm: Rename flush_tlb_single() and flush_tlb_one() to __flush_tlb_one_[user|kernel]()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 1299ef1d8870d2d9f09a5aadf2f8b2c887c2d033 upstream. flush_tlb_single() and flush_tlb_one() sound almost identical, but they really mean "flush one user translation" and "

[PATCH 4.14 086/167] x86/cpu: Rename cpu_data.x86_mask to cpu_data.x86_stepping

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jia Zhang commit b399151cb48db30ad1e0e93dd40d68c6d007b637 upstream. x86_mask is a confusing name which is hard to associate with the processor's stepping. Additionally, correct an indent issu

[PATCH 4.14 085/167] selftests/x86/mpx: Fix incorrect bounds with old _sigfault

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rui Wang commit 961888b1d76d84efc66a8f5604b06ac12ac2f978 upstream. For distributions with old userspace header files, the _sigfault structure is different. mpx-mini-test fails with the followi

[PATCH 4.14 079/167] kmemcheck: remove annotations

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Levin, Alexander (Sasha Levin) commit 4950276672fce5c241857540f8561c440663673d upstream. Patch series "kmemcheck: kill kmemcheck", v2. As discussed at LSF/MM, kill kmemcheck. KASan is a repl

[PATCH 4.14 040/167] x86/entry/64: Clear extra registers beyond syscall arguments, to reduce speculation attack surface

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 8e1eb3fa009aa7c0b944b3c8b26b07de0efb3200 upstream. At entry userspace may have (maliciously) populated the extra registers outside the syscall calling convention with arbit

[PATCH 4.14 036/167] x86/gpu: add CFL to early quirks

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lucas De Marchi commit 33aa69ed8aacd92dea12671e52eb3ca6ac2d7a49 upstream. CFL was missing from intel_early_ids[]. The PCI ID needs to be there to allow the memory region to be stolen, otherwis

[PATCH 4.14 038/167] x86/xen: init %gs very early to avoid page faults with stack protector

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Juergen Gross commit 4f277295e54c5b7340e48efea3fc5cc21a2872b7 upstream. When running as Xen pv guest %gs is initialized some time after C code is started. Depending on stack protector usage th

[PATCH 4.14 078/167] x86/speculation: Add dependency

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit ea00f301285ea2f07393678cd2b6057878320c9d upstream. Joe Konno reported a compile failure resulting from using an MSR without inclusion of , and while the current code buil

[PATCH 4.14 037/167] x86/kexec: Make kexec (mostly) work in 5-level paging mode

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 5bf30316991d5bcda046343ee77d823cf16fdd03 upstream. Currently kexec() will crash when switching into a 5-level paging enabled kernel. I missed that we need to change

[PATCH 4.14 035/167] drm/i915/kbl: Change a KBL pci id to GT2 from GT1.5

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Anuj Phogat commit 41693fd5237397d3c61b311af0fda1f6f39297c2 upstream. See Mesa commit 9c588ff Cc: Matt Turner Cc: Rodrigo Vivi Signed-off-by: Anuj Phogat Reviewed-by: Rodrigo Vivi Signed-

[PATCH 4.14 067/167] selftests/x86: Fix vDSO selftest segfault for vsyscall=none

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 198ee8e17502da2634f7366395db1d77630e0219 upstream. The vDSO selftest tries to execute a vsyscall unconditionally, even if it is not present on the test system (e.g. if

[PATCH 4.14 066/167] x86/entry/64: Remove the unused icebp macro

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit b498c261107461d5c42140dfddd05df83d8ca078 upstream. That macro was touched around 2.5.8 times, judging by the full history linux repo, but it was unused even then. Get ri

[PATCH 4.14 064/167] x86/entry/64: Indent PUSH_AND_CLEAR_REGS and POP_REGS properly

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 92816f571af81e9a71cc6f3dc8ce1e2fcdf7b6b8 upstream. ... same as the other macros in arch/x86/entry/calling.h Signed-off-by: Dominik Brodowski Cc: Andy Lutomirski Cc:

[PATCH 4.14 060/167] x86/entry/64: Interleave XOR register clearing with PUSH instructions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit f7bafa2b05ef25eda1d9179fd930b0330cf2b7d1 upstream. Same as is done for syscalls, interleave XOR with PUSH instructions for exceptions/interrupts, in order to minimize

[PATCH 4.14 034/167] drm/i915: add GT number to intel_device_info

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lionel Landwerlin commit 0890540e21cf1156b4cf960a4c1c734db4e816f9 upstream. Up to Coffeelake we could deduce this GT number from the device ID. This doesn't seem to be the case anymore. This c

Re: [PATCH v2 1/3] HID: add driver for Valve Steam Controller

On Tue, Feb 20, 2018 at 8:33 PM, Rodrigo Rivas Costa wrote: > There are two ways to connect the Steam Controller: directly to the USB > or with the USB wireless adapter. Both methods are similar, but the > wireless adapter can connect up to 4 devices at the same time. > > The wired device will ap

[PATCH 4.14 061/167] x86/entry/64: Introduce the PUSH_AND_CLEAN_REGS macro

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 3f01daecd545e818098d84fd1ad43e19a508d705 upstream. Those instances where ALLOC_PT_GPREGS_ON_STACK is called just before SAVE_AND_CLEAR_REGS can trivially be replaced b

[PATCH 4.14 059/167] x86/entry/64: Merge the POP_C_REGS and POP_EXTRA_REGS macros into a single POP_REGS macro

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 502af0d70843c2a9405d7ba1f79b4b0305aaf5f5 upstream. The two special, opencoded cases for POP_C_REGS can be handled by ASM macros. Signed-off-by: Dominik Brodowski Cc:

[PATCH 4.14 056/167] PM: cpuidle: Fix cpuidle_poll_state_init() prototype

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit d7212cfb05ba802bea4dd6c90d61cfe6366ea224 upstream. Commit f85942207516 (x86: PM: Make APM idle driver initialize polling state) made apm_init() call cpuidle_poll_state

[PATCH 4.14 055/167] PM / runtime: Update links_count also if !CONFIG_SRCU

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 433986c2c265d106d6a8e88006e0131fefc92b7b upstream. Commit baa8809f6097 (PM / runtime: Optimize the use of device links) added an invocation of pm_runtime_drop_link() to __d

Re: [PATCH v2 1/2] KVM: x86: Add a framework for supporting MSR-based features

On 2/21/2018 5:41 AM, Paolo Bonzini wrote: > On 16/02/2018 00:12, Tom Lendacky wrote: >> +static u32 msr_based_features[] = { >> +}; >> + >> +static unsigned int num_msr_based_features = ARRAY_SIZE(msr_based_features); >> + >> bool kvm_valid_efer(struct kvm_vcpu *vcpu, u64 efer) >> { >> if (

[PATCH 4.14 049/167] x86/speculation: Correct Speculation Control microcode blacklist again

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit d37fc6d360a404b208547ba112e7dabb6533c7fc upstream. Arjan points out that the Intel document only clears the 0xc2 microcode on *some* parts with CPUID 506E3 (INTEL_FAM6_S

[PATCH 4.14 048/167] x86/speculation: Update Speculation Control microcode blacklist

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit 1751342095f0d2b36fa8114d8e12c5688c455ac4 upstream. Intel have retroactively blessed the 0xc2 microcode on Skylake mobile and desktop parts, and the Gemini Lake 0x22 micr

Re: metag build errors in mainline kernel

On 02/21/2018 04:27 AM, James Hogan wrote: On Tue, Feb 20, 2018 at 03:44:43PM -0800, Guenter Roeck wrote: The following errors are seen when building the kernel with the latest available metag toolchain (4.2.4 (IMG-1.4.0.700)). Kernel version tested is (v4.16-rc2-64-gaf3e79d29555). metag:allmod

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