[PATCH 4.16 47/72] drm/nouveau/ttm: dont dereference nvbo::cli, it can outlive client

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 0d5a03c3d9254813ca76d7886ff9ed76a0aea545 upstream. Potentially responsible for some random OOPSes. Signed-off-by: Ben Skeggs Cc: sta...@vger.kernel.org [v4.15+] Signed-off-

Re: [PATCH] efi/x86: Clean up the eboot code a bit

On 14 May 2018 at 08:58, Ingo Molnar wrote: > > * Ard Biesheuvel wrote: > >> On 14 May 2018 at 08:43, Ingo Molnar wrote: >> > >> > So I looked at arch/x86/boot/compressed/eboot.c to improve a printk >> > message and >> > ended up with the cleanups below. >> > >> > Only build tested. >> > >> > T

[PATCH 4.16 52/72] PCI / PM: Always check PME wakeup capability for runtime wakeup support

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Kai Heng Feng commit 8feaec33b9868582654cd3d5355225dcb79aeca6 upstream. USB controller ASM1042 stops working after commit de3ef1eb1cd0 (PM / core: Drop run_wake flag from struct dev_pm_info).

[PATCH 4.16 56/72] Revert "Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174"

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 544a591668813583021474fa5c7ff4942244d654 upstream. Commit f44cb4b19ed4 ("Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174") is causing bluetooth to no longer work for

[PATCH 4.16 51/72] atm: zatm: Fix potential Spectre v1

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 2be147f7459db5bbf292e0a6f135037b55e20b39 upstream. pool can be indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre variant

[PATCH 4.16 62/72] nvme: Fix sync controller reset return

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Charles Machalow commit 4e50d9ebaeaa3c6761d2b513ef7039510c8cf213 upstream. If a controller reset is requested while the device has no namespaces, we were incorrectly returning ENETRESET. This

[PATCH 4.16 59/72] thermal: exynos: Reading temperature makes sense only when TMU is turned on

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit 88fc6f73fddf64eb507b04f7b2bd01d7291db514 upstream. When thermal sensor is not yet enabled, reading temperature might return random value. This might even result in stop

[PATCH 4.16 54/72] cpufreq: schedutil: Avoid using invalid next_freq

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 97739501f207efe33145b918817f305b822987f8 upstream. If the next_freq field of struct sugov_policy is set to UINT_MAX, it shouldn't be used for updating the CPU frequenc

[PATCH 4.16 36/72] can: kvaser_usb: Increase correct stats counter in kvaser_usb_rx_can_msg()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Jimmy Assarsson commit 6ee00865ffe4e8c8ba4a68d26db53c7ec09bbb89 upstream. Increase rx_dropped, if alloc_can_skb() fails, not tx_dropped. Signed-off-by: Jimmy Assarsson Cc: linux-stable Sign

[PATCH 4.16 39/72] mtd: rawnand: marvell: pass ms delay to wait_op

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Chris Packham commit b76401fc4ba720f0f38f7b1f9d54d5c2308bc18d upstream. marvell_nfc_wait_op() expects the delay to be expressed in milliseconds but nand_sdr_timings uses picoseconds. Use PSEC_

[PATCH 4.16 31/72] z3fold: fix reclaim lock-ups

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Wool commit 6098d7e136692f9c6e23ae362c62ec822343e4d5 upstream. Do not try to optimize in-page object layout while the page is under reclaim. This fixes lock-ups on reclaim and improves

[PATCH 4.16 37/72] can: hi311x: Acquire SPI lock on ->do_get_berr_counter

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 5cec9425b41dcf834c3d48776900d6acb7e96f38 upstream. hi3110_get_berr_counter() may run concurrently to the rest of the driver but neglects to acquire the lock protecting acce

[PATCH 4.16 63/72] smb3: directory sync should not return an error

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Steve French commit 6e70c267e68d77679534dcf4aaf84e66f2cf1425 upstream. As with NFS, which ignores sync on directory handles, fsync on a directory handle is a noop for CIFS/SMB3. Do not return

[PATCH 4.16 40/72] mtd: rawnand: marvell: fix command xtype in BCH write hook

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Miquel Raynal commit a2ee41fd953e7c3ff6c55a3038c80354d191a318 upstream. One layout supported by the Marvell NAND controller supports NAND pages of 2048 bytes, all handled in one single chunk w

Re: [PATCH 17/17] efi/libstub/arm64: handle randomized TEXT_OFFSET

On 14 May 2018 at 09:00, Ingo Molnar wrote: > > * Ard Biesheuvel wrote: > >> On 14 May 2018 at 08:47, Ingo Molnar wrote: >> > >> > * Ard Biesheuvel wrote: >> > >> >> From: Mark Rutland >> >> >> >> When CONFIG_RANDOMIZE_TEXT_OFFSET is selected, TEXT_OFFSET is an >> >> arbitrary multiple of PAGE

[PATCH 4.16 38/72] can: hi311x: Work around TX complete interrupt erratum

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 32bee8f48fa048a3198109de50e51c092507ff52 upstream. When sending packets as fast as possible using "cangen -g 0 -i -x", the HI-3110 occasionally latches the interrupt pin hi

Re: [PATCH 12/17] efi: fix efi_pci_io_protocol32 prototype for mixed mode

On 14 May 2018 at 08:57, Ingo Molnar wrote: > > * Ard Biesheuvel wrote: > >> Mixed mode allows a kernel built for x86_64 to interact with 32-bit >> EFI firmware, but requires us to define all struct definitions carefully >> when it comes to pointer sizes. efi_pci_io_protocol32 currently uses a >>

[PATCH 4.16 34/72] ceph: fix rsize/wsize capping in ceph_direct_read_write()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 3a15b38fd2efc1d648cb33186bf71e9138c93491 upstream. rsize/wsize cap should be applied before ceph_osdc_new_request() is called. Otherwise, if the size is limited by the cap

[PATCH 4.16 61/72] nvme: add quirk to force medium priority for SQ creation

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Jens Axboe commit 9abd68ef454c824bfd18629033367b4382b5f390 upstream. Some P3100 drives have a bug where they think WRRU (weighted round robin) is always enabled, even though the host doesn't s

[PATCH 4.16 58/72] Bluetooth: btusb: Only check needs_reset_resume DMI table for QCA rome chipsets

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit fc54910280eb38bde923cdf0898e74687d8e6989 upstream. Jeremy Cline correctly points out in rhbz#1514836 that a device where the QCA rome chipset needs the USB_QUIRK_RESET_RES

[PATCH 4.16 57/72] Bluetooth: btusb: Add Dell XPS 13 9360 to btusb_needs_reset_resume_table

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 596b07a9a22656493726edf1739569102bd3e136 upstream. The Dell XPS 13 9360 uses a QCA Rome chip which needs to be reset (and have its firmware reloaded) for bluetooth to work

Re: [PATCH 17/17] efi/libstub/arm64: handle randomized TEXT_OFFSET

* Ard Biesheuvel wrote: > On 14 May 2018 at 08:47, Ingo Molnar wrote: > > > > * Ard Biesheuvel wrote: > > > >> From: Mark Rutland > >> > >> When CONFIG_RANDOMIZE_TEXT_OFFSET is selected, TEXT_OFFSET is an > >> arbitrary multiple of PAGE_SIZE in the interval [0, 2MB). > >> > >> The EFI stub do

[PATCH 4.16 60/72] thermal: exynos: Propagate error value from tmu_read()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit c8da6cdef57b459ac0fd5d9d348f8460a575ae90 upstream. tmu_read() in case of Exynos4210 might return error for out of bound values. Current code ignores such value, what le

[PATCH 4.16 50/72] net: atm: Fix potential Spectre v1

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit acf784bd0ce257fe43da7ca266f7a10b837479d2 upstream. ioc_data.dev_num can be controlled by user-space, hence leading to a potential exploitation of the Spectre variant

[PATCH 4.16 53/72] PCI / PM: Check device_may_wakeup() in pci_enable_wake()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit cfcadfaad7251d8b640713724b388164d75465b2 upstream. Commit 0847684cfc5f0 (PCI / PM: Simplify device wakeup settings code) went too far and dropped the device_may_wakeup

[PATCH 4.16 33/72] mm, oom: fix concurrent munlock and oom reaper unmap, v3

4.16-stable review patch. If anyone has any objections, please let me know. -- From: David Rientjes commit 27ae357fa82be5ab73b2ef8d39dcb8ca2563483a upstream. Since exit_mmap() is done without the protection of mm->mmap_sem, it is possible for the oom reaper to concurrently ope

[PATCH 4.16 46/72] drm/nouveau: Fix deadlock in nv50_mstm_register_connector()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul commit 352672db857290ab5b0e2b6a99c414f92bee024c upstream. Currently; we're grabbing all of the modesetting locks before adding MST connectors to fbdev. This isn't actually necessary

[PATCH 4.16 41/72] mtd: rawnand: Make sure we wait tWB before polling the STATUS reg

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit 3057fcef385348fe85173f1b0c824d89f1176f72 upstream. NAND chips require a bit of time to take the NAND operation into account and set the BUSY bit in the STATUS reg. Make

[PATCH 4.16 07/72] netlink: fix uninit-value in netlink_sendmsg

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 6091f09c2f79730d895149bcfe3d66140288cd0e upstream. syzbot reported : BUG: KMSAN: uninit-value in ffs arch/x86/include/asm/bitops.h:432 [inline] BUG: KMSAN: uninit-value in

[PATCH 4.16 00/72] 4.16.9-stable review

This is the start of the stable review cycle for the 4.16.9 release. There are 72 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed May 16 06:47:58 UTC 2018. Anything receive

[PATCH 4.16 08/72] net: fix rtnh_ok()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit b1993a2de12c9e75c35729e2ffbc3a92d50c0d31 upstream. syzbot reported : BUG: KMSAN: uninit-value in rtnh_ok include/net/nexthop.h:11 [inline] BUG: KMSAN: uninit-value in fib_

[PATCH 4.16 05/72] rds: tcp: must use spin_lock_irq* and not spin_lock_bh with rds_tcp_conn_lock

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Sowmini Varadhan commit 53d0e83f9329aa51dcc205b514dbee05cb4df309 upstream. rds_tcp_connection allocation/free management has the potential to be called from __rds_conn_create after IRQs have b

[PATCH 4.16 30/72] tracing: Fix regex_match_front() to not over compare the test string

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit dc432c3d7f9bceb3de6f5b44fb9c657c9810ed6d upstream. The regex match function regex_match_front() in the tracing filter logic, was fixed to test just the pattern l

[PATCH 4.16 03/72] clk: ti: fix flag space conflict with clkctrl clocks

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Tero Kristo commit 269bd202bc0fd04e841cb123867fd3f49e04ace9 upstream. The introduction of support for CLK_SET_RATE_PARENT flag for clkctrl clocks used a generic clock flag, which causes a conf

Allwinner A64: Issue on external rtc clock to wifi chip

Hi Maxime and All, We are trying to bring-up AP6330 Wifi chip for A64 board. We noticed to have an external rtc clock has driven from wifi chip. So the devicetree is configured according to this as below. / { wifi_pwrseq: wifi-pwrseq { compatible = "mmc-pwrseq-simple";

Re: [PATCH] efi/x86: Clean up the eboot code a bit

* Ard Biesheuvel wrote: > On 14 May 2018 at 08:43, Ingo Molnar wrote: > > > > So I looked at arch/x86/boot/compressed/eboot.c to improve a printk message > > and > > ended up with the cleanups below. > > > > Only build tested. > > > > Thanks, > > > > Ingo > > > > => > >

[PATCH 4.16 25/72] gpio: fix aspeed_gpio unmask irq

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Govert Overgaauw commit f241632fd087d3d9fbd5450f4d8c8604badd8348 upstream. The unmask function disables all interrupts in a bank when unmasking an interrupt. Only disable the given interrupt.

[PATCH 4.16 24/72] gpioib: do not free unrequested descriptors

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Timur Tabi commit ab3dbcf78f60f46d6a0ad63b1f4b690b7a427140 upstream. If the main loop in linehandle_create() encounters an error, it unwinds completely by freeing all previously requested GPIO

[PATCH 4.4 54/56] perf/x86/msr: Fix possible Spectre-v1 indexing in the MSR driver

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 06ce6e9b6d6c09d4129c6e24a1314a395d816c10 upstream. > arch/x86/events/msr.c:178 msr_event_init() warn: potential spectre issue > 'msr' (local cap) Userspace controls @att

[PATCH 4.4 55/56] perf/core: Fix possible Spectre-v1 indexing for ->aux_pages[]

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 4411ec1d1993e8dbff2898390e3fed280d88e446 upstream. > kernel/events/ring_buffer.c:871 perf_mmap_to_page() warn: potential spectre > issue 'rb->aux_pages' Userspace contro

[PATCH 4.4 56/56] perf/x86: Fix possible Spectre-v1 indexing for x86_pmu::event_map()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 46b1b577229a091b137831becaa0fae8690ee15a upstream. > arch/x86/events/intel/cstate.c:307 cstate_pmu_event_init() warn: potential > spectre issue 'pkg_msr' (local cap) > ar

[PATCH 4.4 53/56] perf/x86/cstate: Fix possible Spectre-v1 indexing for pkg_msr

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit a5f81290ce475489fa2551c01a07470c1a4c932e upstream. > arch/x86/events/intel/cstate.c:307 cstate_pmu_event_init() warn: potential > spectre issue 'pkg_msr' (local cap) Use

[PATCH 4.4 52/56] perf/x86: Fix possible Spectre-v1 indexing for hw_perf_event cache_*

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit ef9ee4ad38445a30909c48998624861716f2a994 upstream. > arch/x86/events/core.c:319 set_ext_hw_attr() warn: potential spectre issue > 'hw_cache_event_ids[cache_type]' (local

[PATCH 4.16 20/72] bdi: wake up concurrent wb_shutdown() callers.

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit 8236b0ae31c837d2b3a2565c5f8d77f637e824cc upstream. syzbot is reporting hung tasks at wait_on_bit(WB_shutting_down) in wb_shutdown() [1]. This seems to be because commit 531

[PATCH 4.16 21/72] bdi: Fix use after free bug in debugfs_remove()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit f53823c18131e755905b4f654196fd2cc3953f6e upstream. syzbot is reporting use after free bug in debugfs_remove() [1]. This is because fault injection made memory allocation f

Re: [PATCH 2/3] hwmon: (ibmpowernv): Add support to read 64 bit sensors

Guenter Roeck writes: > On Mon, May 07, 2018 at 03:55:37PM +0530, Shilpasri G Bhat wrote: >> The firmware has supported for reading sensor values of size u32. >> This patch adds support to use newer firmware functions which allows >> to read the sensors of size u64. >> >> Signed-off-by: Shilpasr

[PATCH 4.16 19/72] tcp: fix TCP_REPAIR_QUEUE bound checking

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit bf2acc943a45d2b2e8a9f1a5ddff6b6e43cc69d9 upstream. syzbot is able to produce a nasty WARN_ON() in tcp_verify_left_out() with following C-repro : socket(PF_INET, SOCK_STREA

[PATCH 4.16 11/72] dccp: initialize ireq->ir_mark

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit b855ff827476adbdc2259e9895681d82b7b26065 upstream. syzbot reported an uninit-value read of skb->mark in iptable_mangle_hook() Thanks to the nice report, I tracked the prob

Re: Is read barrier missed in kfifo?

On Fri, May 11, 2018 at 09:20:53AM -0700, Paul E. McKenney wrote: > On Fri, May 11, 2018 at 10:32:42AM +0200, Peter Zijlstra wrote: > > On Fri, May 11, 2018 at 03:25:18PM +0800, Xiao Guangrong wrote: > > > > > > Hi, > > > > > > Currently, there is no read barrier between reading the index > > > (

[PATCH 4.16 17/72] perf: Remove superfluous allocation error check

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Olsa commit bfb3d7b8b906b66551424d7636182126e1d134c8 upstream. If the get_callchain_buffers fails to allocate the buffer it will decrease the nr_callchain_events right away. There's no p

[PATCH 4.16 14/72] inetpeer: fix uninit-value in inet_getpeer

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit b6a37e5e25414df4b8e9140a5c6f5ee0ec6f3b90 upstream. syzbot/KMSAN reported that p->dtime was read while it was not yet initialized in : delta = (__u32)jiffies - p->d

Re: [PATCH v2] x86/io: Define readq()/writeq() to use 64-bit type

On Sun, 13 May 2018, Andy Shevchenko wrote: > On Sun, May 13, 2018 at 9:09 PM, Thomas Gleixner wrote: > > On Thu, 3 May 2018, Andy Shevchenko wrote: > >> #ifdef CONFIG_X86_64 > >> > >> -build_mmio_read(readq, "q", unsigned long, "=r", :"memory") > >> -build_mmio_read(__readq, "q", unsigned long,

[PATCH 4.16 12/72] ipv4: fix uninit-value in ip_route_output_key_hash_rcu()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit d0ea2b12500543535be3f54e17920fffc9bb45f6 upstream. syzbot complained that res.type could be used while not initialized. Using RTN_UNSPEC as initial value seems better than

[PATCH 4.14 26/62] rfkill: gpio: fix memory leak in probe error path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 4bf01ca21e2e0e4561d1a03c48c3d740418702db upstream. Make sure to free the rfkill device in case registration fails during probe. Fixes: 5e7ca3937fbe ("net: rfkill: gpio: co

[PATCH 4.16 10/72] net: fix uninit-value in __hw_addr_add_ex()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 77d36398d99f2565c0a8d43a86fd520a82e64bb8 upstream. syzbot complained : BUG: KMSAN: uninit-value in memcmp+0x119/0x180 lib/string.c:861 CPU: 0 PID: 3 Comm: kworker/0:0 Not

[PATCH 4.14 34/62] can: kvaser_usb: Increase correct stats counter in kvaser_usb_rx_can_msg()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jimmy Assarsson commit 6ee00865ffe4e8c8ba4a68d26db53c7ec09bbb89 upstream. Increase rx_dropped, if alloc_can_skb() fails, not tx_dropped. Signed-off-by: Jimmy Assarsson Cc: linux-stable Sign

[PATCH 4.16 13/72] soreuseport: initialise timewait reuseport field

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 3099a52918937ab86ec47038ad80d377ba16c531 upstream. syzbot reported an uninit-value in inet_csk_bind_conflict() [1] It turns out we never propagated sk->sk_reuseport into t

[PATCH 4.14 33/62] ceph: fix rsize/wsize capping in ceph_direct_read_write()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 3a15b38fd2efc1d648cb33186bf71e9138c93491 upstream. rsize/wsize cap should be applied before ceph_osdc_new_request() is called. Otherwise, if the size is limited by the cap

Re: [PATCH 12/17] efi: fix efi_pci_io_protocol32 prototype for mixed mode

* Ard Biesheuvel wrote: > Mixed mode allows a kernel built for x86_64 to interact with 32-bit > EFI firmware, but requires us to define all struct definitions carefully > when it comes to pointer sizes. efi_pci_io_protocol32 currently uses a > void* for the 'romimage' field, which will be interp

[PATCH 4.14 31/62] mm: sections are not offlined during memory hotremove

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Tatashin commit 27227c733852f71008e9bf165950bb2edaed3a90 upstream. Memory hotplug and hotremove operate with per-block granularity. If the machine has a large amount of memory (more tha

[PATCH 4.14 51/62] thermal: exynos: Propagate error value from tmu_read()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit c8da6cdef57b459ac0fd5d9d348f8460a575ae90 upstream. tmu_read() in case of Exynos4210 might return error for out of bound values. Current code ignores such value, what le

[PATCH 4.14 49/62] Bluetooth: btusb: Only check needs_reset_resume DMI table for QCA rome chipsets

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit fc54910280eb38bde923cdf0898e74687d8e6989 upstream. Jeremy Cline correctly points out in rhbz#1514836 that a device where the QCA rome chipset needs the USB_QUIRK_RESET_RES

[PATCH 4.14 52/62] nvme: add quirk to force medium priority for SQ creation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jens Axboe commit 9abd68ef454c824bfd18629033367b4382b5f390 upstream. Some P3100 drives have a bug where they think WRRU (weighted round robin) is always enabled, even though the host doesn't s

[PATCH 4.14 50/62] thermal: exynos: Reading temperature makes sense only when TMU is turned on

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit 88fc6f73fddf64eb507b04f7b2bd01d7291db514 upstream. When thermal sensor is not yet enabled, reading temperature might return random value. This might even result in stop

[PATCH 4.14 47/62] Revert "Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 544a591668813583021474fa5c7ff4942244d654 upstream. Commit f44cb4b19ed4 ("Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174") is causing bluetooth to no longer work for

[PATCH 4.14 48/62] Bluetooth: btusb: Add Dell XPS 13 9360 to btusb_needs_reset_resume_table

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 596b07a9a22656493726edf1739569102bd3e136 upstream. The Dell XPS 13 9360 uses a QCA Rome chip which needs to be reset (and have its firmware reloaded) for bluetooth to work

[PATCH 4.14 46/62] cpufreq: schedutil: Avoid using invalid next_freq

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 97739501f207efe33145b918817f305b822987f8 upstream. If the next_freq field of struct sugov_policy is set to UINT_MAX, it shouldn't be used for updating the CPU frequenc

Re: reply: [PATCH v3 1/2] PCI: kirin: Add MSI support

On Mon, May 14, 2018 at 4:11 AM, songxiaowei wrote: >> > + int ret; >> > + >> > + if (IS_ENABLED(CONFIG_PCI_MSI)) { >> >> > + pci->pp.msi_irq = platform_get_irq(pdev, 0); >> > + if (pci->pp.msi_irq < 0) { >> > + dev_err(&pdev->dev, "fa

[PATCH 4.9 32/36] perf/x86: Fix possible Spectre-v1 indexing for hw_perf_event cache_*

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit ef9ee4ad38445a30909c48998624861716f2a994 upstream. > arch/x86/events/core.c:319 set_ext_hw_attr() warn: potential spectre issue > 'hw_cache_event_ids[cache_type]' (local

[PATCH 4.16 65/72] sched/core: Fix possible Spectre-v1 indexing for sched_prio_to_weight[]

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 7281c8dec8a87685cb54d503d8cceef5a0fc2fdd upstream. > kernel/sched/core.c:6921 cpu_weight_nice_write_s64() warn: potential spectre > issue 'sched_prio_to_weight' Userspa

[PATCH 4.14 59/62] perf/core: Fix possible Spectre-v1 indexing for ->aux_pages[]

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 4411ec1d1993e8dbff2898390e3fed280d88e446 upstream. > kernel/events/ring_buffer.c:871 perf_mmap_to_page() warn: potential spectre > issue 'rb->aux_pages' Userspace contr

[PATCH 4.14 54/62] sched/autogroup: Fix possible Spectre-v1 indexing for sched_prio_to_weight[]

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 354d7793070611b4df5a79fbb0f12752d0ed0cc5 upstream. > kernel/sched/autogroup.c:230 proc_sched_autogroup_set_nice() warn: potential > spectre issue 'sched_prio_to_weight'

[PATCH 4.9 36/36] perf/x86: Fix possible Spectre-v1 indexing for x86_pmu::event_map()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 46b1b577229a091b137831becaa0fae8690ee15a upstream. > arch/x86/events/intel/cstate.c:307 cstate_pmu_event_init() warn: potential > spectre issue 'pkg_msr' (local cap) > ar

[PATCH 4.16 68/72] perf/x86: Fix possible Spectre-v1 indexing for hw_perf_event cache_*

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit ef9ee4ad38445a30909c48998624861716f2a994 upstream. > arch/x86/events/core.c:319 set_ext_hw_attr() warn: potential spectre issue > 'hw_cache_event_ids[cache_type]' (local

[PATCH 4.14 57/62] perf/x86/cstate: Fix possible Spectre-v1 indexing for pkg_msr

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit a5f81290ce475489fa2551c01a07470c1a4c932e upstream. > arch/x86/events/intel/cstate.c:307 cstate_pmu_event_init() warn: potential > spectre issue 'pkg_msr' (local cap) Us

[PATCH 4.16 66/72] sched/autogroup: Fix possible Spectre-v1 indexing for sched_prio_to_weight[]

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 354d7793070611b4df5a79fbb0f12752d0ed0cc5 upstream. > kernel/sched/autogroup.c:230 proc_sched_autogroup_set_nice() warn: potential > spectre issue 'sched_prio_to_weight'

[PATCH 4.16 69/72] perf/x86/cstate: Fix possible Spectre-v1 indexing for pkg_msr

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit a5f81290ce475489fa2551c01a07470c1a4c932e upstream. > arch/x86/events/intel/cstate.c:307 cstate_pmu_event_init() warn: potential > spectre issue 'pkg_msr' (local cap) Us

[PATCH 4.9 33/36] perf/x86/cstate: Fix possible Spectre-v1 indexing for pkg_msr

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit a5f81290ce475489fa2551c01a07470c1a4c932e upstream. > arch/x86/events/intel/cstate.c:307 cstate_pmu_event_init() warn: potential > spectre issue 'pkg_msr' (local cap) Use

[PATCH 4.14 60/62] perf/x86: Fix possible Spectre-v1 indexing for x86_pmu::event_map()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 46b1b577229a091b137831becaa0fae8690ee15a upstream. > arch/x86/events/intel/cstate.c:307 cstate_pmu_event_init() warn: potential > spectre issue 'pkg_msr' (local cap) > a

[PATCH 4.9 35/36] perf/core: Fix possible Spectre-v1 indexing for ->aux_pages[]

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 4411ec1d1993e8dbff2898390e3fed280d88e446 upstream. > kernel/events/ring_buffer.c:871 perf_mmap_to_page() warn: potential spectre > issue 'rb->aux_pages' Userspace contro

[PATCH 4.16 70/72] perf/x86/msr: Fix possible Spectre-v1 indexing in the MSR driver

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 06ce6e9b6d6c09d4129c6e24a1314a395d816c10 upstream. > arch/x86/events/msr.c:178 msr_event_init() warn: potential spectre issue > 'msr' (local cap) Userspace controls @at

[PATCH 4.16 72/72] perf/x86: Fix possible Spectre-v1 indexing for x86_pmu::event_map()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 46b1b577229a091b137831becaa0fae8690ee15a upstream. > arch/x86/events/intel/cstate.c:307 cstate_pmu_event_init() warn: potential > spectre issue 'pkg_msr' (local cap) > a

[PATCH 4.16 71/72] perf/core: Fix possible Spectre-v1 indexing for ->aux_pages[]

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 4411ec1d1993e8dbff2898390e3fed280d88e446 upstream. > kernel/events/ring_buffer.c:871 perf_mmap_to_page() warn: potential spectre > issue 'rb->aux_pages' Userspace contr

linux-next: Tree for May 14

Hi all, Changes since 20180511: New trees: btrfs-fixes vfs-fixes dma-mapping-fixes The f2fs tree gained a conflict against the vfs-fixes tree. The bpf-next tree gained a conflict against the bpf tree. The rcu tree gained a conflict against Linus' tree. The kselftest tree gaine

[PATCH 4.9 34/36] perf/x86/msr: Fix possible Spectre-v1 indexing in the MSR driver

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 06ce6e9b6d6c09d4129c6e24a1314a395d816c10 upstream. > arch/x86/events/msr.c:178 msr_event_init() warn: potential spectre issue > 'msr' (local cap) Userspace controls @att

[PATCH 4.14 58/62] perf/x86/msr: Fix possible Spectre-v1 indexing in the MSR driver

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 06ce6e9b6d6c09d4129c6e24a1314a395d816c10 upstream. > arch/x86/events/msr.c:178 msr_event_init() warn: potential spectre issue > 'msr' (local cap) Userspace controls @at

Re: [PATCH v2] usb: chipidea: Hook into mux framework to toggle usb switch

On 2018-04-18 07:48, yos...@codeaurora.org wrote: > On 2018-04-17 17:11, Peter Rosin wrote: >> On 2018-04-17 15:52, Yossi Mansharoff wrote: >>> On the db410c 96boards platform we have a TC7USB40MU on the board >>> to mux the D+/D- lines coming from the controller between a micro >>> usb "device" po

[PATCH 4.14 56/62] perf/x86: Fix possible Spectre-v1 indexing for hw_perf_event cache_*

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit ef9ee4ad38445a30909c48998624861716f2a994 upstream. > arch/x86/events/core.c:319 set_ext_hw_attr() warn: potential spectre issue > 'hw_cache_event_ids[cache_type]' (local

[PATCH 4.14 45/62] PCI / PM: Check device_may_wakeup() in pci_enable_wake()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit cfcadfaad7251d8b640713724b388164d75465b2 upstream. Commit 0847684cfc5f0 (PCI / PM: Simplify device wakeup settings code) went too far and dropped the device_may_wakeup

[PATCH 4.14 42/62] net: atm: Fix potential Spectre v1

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit acf784bd0ce257fe43da7ca266f7a10b837479d2 upstream. ioc_data.dev_num can be controlled by user-space, hence leading to a potential exploitation of the Spectre variant

[PATCH 4.14 36/62] can: hi311x: Work around TX complete interrupt erratum

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 32bee8f48fa048a3198109de50e51c092507ff52 upstream. When sending packets as fast as possible using "cangen -g 0 -i -x", the HI-3110 occasionally latches the interrupt pin hi

Re: [PATCH] m68k: Implement ndelay() as an inline function to force type checking/casting

Hi Boris, On Sun, 13 May 2018 16:02:12 +0200, Boris Brezillon wrote: > ndelay() is supposed to take an unsigned long, but if you define > ndelay() as a macro and the caller pass an unsigned long long instead > of an unsigned long, the unsigned long long to unsigned long cast is > not done and we

Re: commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073 seems to break with intel-ucode 20180425

On Sat, May 12, 2018 at 12:55:35PM +0200, Gabriel C wrote: > Hi Peter, > > after updating ucode to 20180425 on my laptop I always hit the > 'TSC_DEADLINE disabled' error and so early microcode update from > inird breaks. > > Also I'm able to late load the microcode from command line but > not fro

[PATCH 4.14 00/62] 4.14.41-stable review

This is the start of the stable review cycle for the 4.14.41 release. There are 62 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed May 16 06:47:52 UTC 2018. Anything receiv

[PATCH 4.14 05/62] netlink: fix uninit-value in netlink_sendmsg

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 6091f09c2f79730d895149bcfe3d66140288cd0e upstream. syzbot reported : BUG: KMSAN: uninit-value in ffs arch/x86/include/asm/bitops.h:432 [inline] BUG: KMSAN: uninit-value in

[PATCH 4.14 27/62] libata: Apply NOLPM quirk for SanDisk SD7UB3Q*G1001 SSDs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 184add2ca23ce5edcac0ab9c3b9be13f91e7b567 upstream. Richard Jones has reported that using med_power_with_dipm on a T450s with a Sandisk SD7UB3Q256G1001 SSD (firmware versio

[PATCH 4.14 06/62] net: fix rtnh_ok()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit b1993a2de12c9e75c35729e2ffbc3a92d50c0d31 upstream. syzbot reported : BUG: KMSAN: uninit-value in rtnh_ok include/net/nexthop.h:11 [inline] BUG: KMSAN: uninit-value in fib_

[PATCH 4.14 09/62] dccp: initialize ireq->ir_mark

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit b855ff827476adbdc2259e9895681d82b7b26065 upstream. syzbot reported an uninit-value read of skb->mark in iptable_mangle_hook() Thanks to the nice report, I tracked the prob

[PATCH 4.14 07/62] net: initialize skb->peeked when cloning

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit b13dda9f9aa7cac61c080c2e544d5f5d85e5 upstream. syzbot reported __skb_try_recv_from_queue() was using skb->peeked while it was potentially unitialized. We need to clear

[PATCH 4.14 04/62] crypto: af_alg - fix possible uninit-value in alg_bind()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit a466856e0b7ab269cdf9461886d007e88ff575b0 upstream. syzbot reported : BUG: KMSAN: uninit-value in alg_bind+0xe3/0xd90 crypto/af_alg.c:162 We need to check addr_len before

  1   2   3   4   5   6   7   8   9   10   >