[PATCH v3 2/6] soc/fsl/guts: Add compatible string for LX2160A

Adding compatible string "lx2160a-dcfg" to initialize guts driver for lx2160 Signed-off-by: Vabhav Sharma --- drivers/soc/fsl/guts.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/soc/fsl/guts.c b/drivers/soc/fsl/guts.c index 302e0c8..5e1e633 100644 --- a/drivers/soc/fsl/guts.c +++

[PATCH 4.14 049/173] staging: bcm2835-camera: fix timeout handling in wait_for_completion_timeout

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire [ Upstream commit b7afce51d95726a619743aaad8870db66dfa1479 ] wait_for_completion_timeout returns unsigned long not int so a variable of proper type is introduced. Further the

[PATCH 4.14 051/173] ASoC: rt5514: Fix the issue of the delay volume applied

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Oder Chiou [ Upstream commit d96f8bd28cd0bae3e6702ae90df593628ef6906f ] The patch fixes the issue of the delay volume applied. Signed-off-by: Oder Chiou Signed-off-by: Mark Brown Signed-off

[PATCH 4.14 055/173] wan/fsl_ucc_hdlc: use IS_ERR_VALUE() to check return value of qe_muram_alloc

4.14-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing [ Upstream commit fd800f646402c0f85547166b59ca065175928b7b ] qe_muram_alloc return a unsigned long integer,which should not compared with zero. check it using IS_ERR_VALUE() to fix

[PATCH 4.14 050/173] staging: bcm2835-camera: handle wait_for_completion_timeout return properly

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire [ Upstream commit 5b70084f6cbcd53f615433f9d216e01bd71de0bb ] wait_for_completion_timeout returns unsigned long not int so a variable of proper type is introduced. Further the

[PATCH 4.14 052/173] MIPS: jz4740: Bump zload address

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paul Cercueil [ Upstream commit c6ea7e9747318e5a6774995f4f8e3e0f7c0fa8ba ] Having the zload address at 0x8060. means the size of the uncompressed kernel cannot be bigger than around 6 MiB,

[PATCH 4.14 054/173] Smack: Fix handling of IPv4 traffic received by PF_INET6 sockets

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Piotr Sawicki [ Upstream commit 129a99890936766f4b69b9da7ed88366313a9210 ] A socket which has sk_family set to PF_INET6 is able to receive not only IPv6 but also IPv4 traffic (IPv4-mapped IPv6

[PATCH 4.14 056/173] arm64: fix possible spectre-v1 write in ptrace_hbp_set_event()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mark Rutland [ Upstream commit 14d6e289a89780377f8bb09de8926d3c62d763cd ] It's possible for userspace to control idx. Sanitize idx when using it as an array index, to inhibit the potential spe

[PATCH 4.14 053/173] mac80211: restrict delayed tailroom needed decrement

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Manikanta Pubbisetty [ Upstream commit 133bf90dbb8b873286f8ec2e81ba26e863114b8c ] As explained in ieee80211_delayed_tailroom_dec(), during roam, keys of the old AP will be destroyed and new ke

[PATCH 4.14 023/173] clk: clk-fixed-factor: Clear OF_POPULATED flag in case of failure

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rajan Vaja [ Upstream commit f6dab4233d6b64d719109040503b567f71fbfa01 ] Fixed factor clock has two initializations at of_clk_init() time and during platform driver probe. Before of_clk_init()

[PATCH 4.14 021/173] clk: imx6ul: fix missing of_node_put()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire [ Upstream commit 11177e7a7aaef95935592072985526ebf0a3df43 ] of_find_compatible_node() is returning a device node with refcount incremented and must be explicitly decremented

[PATCH 4.14 020/173] gfs2: Special-case rindex for gfs2_grow

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher [ Upstream commit 776125785a87ff05d49938bd5b9f336f2a05bff6 ] To speed up the common case of appending to a file, gfs2_write_alloc_required presumes that writing beyond the

[PATCH 4.14 057/173] reset: imx7: Fix always writing bits as 0

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leonard Crestez [ Upstream commit 26fce0557fa639fb7bbc33e31a57cff7df25c3a0 ] Right now the only user of reset-imx7 is pci-imx6 and the reset_control_assert and deassert calls on pciephy_reset

[PATCH 4.14 016/173] ALSA: msnd: Fix the default sample sizes

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai [ Upstream commit 7c500f9ea139d0c9b80fdea5a9c911db3166ea54 ] The default sample sizes set by msnd driver are bogus; it sets ALSA PCM format, not the actual bit width. Signed-off-

[PATCH 4.14 059/173] nfp: avoid buffer leak when FW communication fails

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jakub Kicinski [ Upstream commit 07300f774fec9519663a597987a4083225588be4 ] After device is stopped we reset the rings by moving all free buffers to positions [0, cnt - 2], and clear the posit

[PATCH 4.14 068/173] i2c: aspeed: Fix initial values of master and slave state

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jae Hyun Yoo [ Upstream commit 517fde0eb5a8f46c54ba6e2c36e32563b23cb14f ] This patch changes the order of enum aspeed_i2c_master_state and enum aspeed_i2c_slave_state defines to make their ini

[PATCH 4.14 025/173] media: tw686x: Fix oops on buffer alloc failure

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Ha?asa [ Upstream commit 5a1a2f63d840dc2631505b607e11ff65ac1b7d3c ] The error path currently calls tw686x_video_free() which requires vc->dev to be initialized, causing a NULL derefe

[PATCH 4.14 022/173] clk: core: Potentially free connection id

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mikko Perttunen [ Upstream commit 365f7a89c881e84f1ebc925f65f899d5d7ce547e ] Patch "clk: core: Copy connection id" made it so that the connector id 'con_id' is kstrdup_const()ed to cater to dr

[PATCH 4.14 024/173] kbuild: add .DELETE_ON_ERROR special target

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Masahiro Yamada [ Upstream commit 9c2af1c7377a8a6ef86e5cabf80978f3dbbb25c0 ] If Make gets a fatal signal while a shell is executing, it may delete the target file that the recipe was supposed

[PATCH 4.14 070/173] crypto: sharah - Unregister correct algorithms for SAHARA 3

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Müller [ Upstream commit 0e7d4d932ffc23f75efb31a8c2ac2396c1b81c55 ] This patch fixes two typos related to unregistering algorithms supported by SAHARAH 3. In sahara_register_algs the w

[PATCH 4.14 069/173] dmaengine: mv_xor_v2: kill the tasklets upon exit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hanna Hawa [ Upstream commit 8bbafed8dd5cfa81071b50ead5cb60367fdef3a9 ] The mv_xor_v2 driver uses a tasklet, initialized during the probe() routine. However, it forgets to cleanup the tasklet

[PATCH 4.14 082/173] Tools: hv: Fix a bug in the key delete code

4.14-stable review patch. If anyone has any objections, please let me know. -- From: K. Y. Srinivasan commit 86503bd35dec0ce363e9fdbf5299927422ed3899 upstream. Fix a bug in the key delete code - the num_records range from 0 to num_records-1. Signed-off-by: K. Y. Srinivasan R

[PATCH 4.14 071/173] x86/pti: Check the return value of pti_user_pagetable_walk_p4d()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jiang Biao [ Upstream commit b2b7d986a89b6c94b1331a909de1217214fb08c1 ] pti_user_pagetable_walk_p4d() can return NULL, so the return value should be checked to prevent a NULL pointer dereferen

[PATCH 4.14 078/173] IB/ipoib: Avoid a race condition between start_xmit and cm_rep_handler

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Aaron Knister commit 816e846c2eb9129a3e0afa5f920c8bbc71efecaa upstream. Inside of start_xmit() the call to check if the connection is up and the queueing of the packets for later transmission

[PATCH 4.14 079/173] s390/crypto: Fix return code checking in cbc_paes_crypt()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ingo Franzki commit b81126e01a8c6048249955feea46c8217ebefa91 upstream. The return code of cpacf_kmc() is less than the number of bytes to process in case of an error, not greater. The crypt ro

[PATCH 4.14 077/173] xen/netfront: fix waiting for xenbus state change

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Juergen Gross commit 8edfe2e992b75aee3da9316e9697c531194c2f53 upstream. Commit 822fb18a82aba ("xen-netfront: wait xenbus state change when load module manually") added a new wait queue to wait

[PATCH 4.14 076/173] pstore: Fix incorrect persistent ram buffer mapping

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bin Yang commit 831b624df1b420c8f9281ed1307a8db23afb72df upstream. persistent_ram_vmap() returns the page start vaddr. persistent_ram_iomap() supports non-page-aligned mapping. persistent_ram

[PATCH 4.14 060/173] xen-netfront: fix queue name setting

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov [ Upstream commit 2d408c0d4574b01b9ed45e02516888bf925e11a9 ] Commit f599c64fdf7d ("xen-netfront: Fix race between device setup and open") changed the initialization order: xen

[PATCH 4.14 083/173] misc: hmc6352: fix potential Spectre v1

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit de916736dddbd6061472969f667b14204aa9 upstream. val is indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre variant 1 vul

[PATCH 4.14 072/173] x86/pti: Check the return value of pti_user_pagetable_walk_pmd()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jiang Biao [ Upstream commit 8c934e01a7ce685d98e970880f5941d79272c654 ] pti_user_pagetable_walk_pmd() can return NULL, so the return value should be checked to prevent a NULL pointer dereferen

[PATCH 4.14 075/173] RDMA/cma: Protect cma dev list with lock

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Parav Pandit commit 954a8e3aea87e896e320cf648c1a5bbe47de443e upstream. When AF_IB addresses are used during rdma_resolve_addr() a lock is not held. A cma device can get removed while list trav

[PATCH 4.14 084/173] xhci: Fix use after free for URB cancellation on a reallocated endpoint

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 4937213ba7fafa13f30496b3965ffe93970d8b53 upstream. Make sure the cancelled URB is on the current endpoint ring. If the endpoint ring has been reallocated since the URB wa

Re: [PATCH v10 13/26] s390: vfio-ap: zeroize the AP queues

On 09/24/2018 01:36 PM, Cornelia Huck wrote: > On Wed, 12 Sep 2018 15:43:03 -0400 > Tony Krowiak wrote: > >> From: Tony Krowiak >> >> Let's call PAPQ(ZAPQ) to zeroize a queue for each queue configured >> for a mediated matrix device when it is released. >> >> Zeroizing a queue resets the queu

[PATCH 4.14 074/173] xen-netfront: fix warn message as irq device name has /

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Xiao Liang [ Upstream commit 21f2706b20100bb3db378461ab9b8e2035309b5b ] There is a call trace generated after commit 2d408c0d4574b01b9ed45e02516888bf925e11a9( xen-netfront: fix queue name set

[PATCH 4.14 080/173] mmc: omap_hsmmc: fix wakeirq handling on removal

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Kemnade commit 3c398f3c3bef21961eaaeb93227fa66d440dc83d upstream. after unbinding mmc I get things like this: [ 185.294067] mmc1: card 0001 removed [ 185.305206] omap_hsmmc 480b4000.

[PATCH 4.14 073/173] x86/mm/pti: Add an overflow check to pti_clone_pmds()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Joerg Roedel [ Upstream commit 935232ce28dfabff1171e5a7113b2d865fa9ee63 ] The addr counter will overflow if the last PMD of the address space is cloned, resulting in an endless loop. Check fo

[PATCH 4.14 061/173] arm64: dts: qcom: db410c: Fix Bluetooth LED trigger

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Loic Poulain [ Upstream commit e53db018315b7660bb7000a29e79faff2496c2c2 ] Current LED trigger, 'bt', is not known/used by any existing driver. Fix this by renaming it to 'bluetooth-power' trig

[PATCH 4.14 085/173] usb: Dont die twice if PCI xhci host is not responding in resume

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit f3dc41c5d22b2ca14a0802a65d8cdc33a3882d4e upstream. usb_hc_died() should only be called once, and with the primary HCD as parameter. It will mark both primary and secondary

[PATCH 4.14 088/173] USB: Add quirk to support DJI CineSSD

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tim Anderson commit f45681f9becaa65111ed0a691ccf080a0cd5feb8 upstream. This device does not correctly handle the LPM operations. Also, the device cannot handle ATA pass-through commands and l

[PATCH 4.14 087/173] mei: bus: need to unlink client before freeing

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tomas Winkler commit 34f1166afd67f9f48a08c52f36180048908506a4 upstream. In case a client fails to connect in mei_cldev_enable(), the caller won't call the mei_cldev_disable leaving the client

[PATCH 4.14 086/173] mei: ignore not found client in the enumeration

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Usyskin commit 8d2d8935d30cc2acc57a3196dc10dfa8d5cbcdab upstream. Some of the ME clients are available only for BIOS operation and are removed during hand off to an OS. However the r

[PATCH 4.14 092/173] USB: add quirk for WORLDE Controller KS49 or Prodipe MIDI 49C USB controller

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maxence Duprès commit 9b83a1c301ad6d24988a128c69b42cbaaf537d82 upstream. WORLDE Controller KS49 or Prodipe MIDI 49C USB controller cause a -EPROTO error, a communication restart and loop again

[PATCH 4.14 089/173] usb: uas: add support for more quirk flags

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 42d1c6d4a06a77b3ab206a919b9050c3080f3a71 upstream. The hope that UAS devices would be less broken than old style storage devices has turned out to be unfounded. Make UAS s

[PATCH 4.14 090/173] usb: Avoid use-after-free by flushing endpoints early in usb_set_interface()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit f9a5b4f58b280c1d26255376713c132f93837621 upstream. The steps taken by usb core to set a new interface is very different from what is done on the xHC host side. xHC hardwa

[PATCH 4.14 094/173] USB: net2280: Fix erroneous synchronization change

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit dec3c23c9aa1815f07d98ae0375b4cbc10971e13 upstream. Commit f16443a034c7 ("USB: gadgetfs, dummy-hcd, net2280: fix locking for callbacks") was based on a serious misunderstandin

[PATCH 4.14 093/173] usb: gadget: udc: renesas_usb3: fix maxpacket size of ep0

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit dfe1a51d2a36647f74cbad478801efa7cf394376 upstream. This patch fixes an issue that maxpacket size of ep0 is incorrect for SuperSpeed. Otherwise, CDC NCM class with Supe

[PATCH 4.14 091/173] usb: host: u132-hcd: Fix a sleep-in-atomic-context bug in u132_get_frame()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai commit 6d4f268fa132742fe96dad22307c68d237356d88 upstream. i_usX2Y_subs_startup in usbusx2yaudio.c is a completion handler function for the USB driver. So it should not sleep, but it

[PATCH 4.14 095/173] USB: serial: io_ti: fix array underflow in completion handler

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 691a03cfe8ca483f9c48153b869d354e4ae3abef upstream. As reported by Dan Carpenter, a malicious USB device could set port_number to a negative value and we would underflow the

[PATCH 4.14 096/173] usb: misc: uss720: Fix two sleep-in-atomic-context bugs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai commit bc8acc214d3f1cafebcbcd101a695bbac716595d upstream. async_complete() in uss720.c is a completion handler function for the USB driver. So it should not sleep, but it is can sle

[PATCH 4.14 097/173] USB: serial: ti_usb_3410_5052: fix array underflow in completion handler

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 5dfdd24eb3d39d815bc952ae98128e967c9bba49 upstream. Similarly to a recently reported bug in io_ti, a malicious USB device could set port_number to a negative value and we wo

[PATCH 4.14 062/173] ARM: dts: qcom: msm8974-hammerhead: increase load on l20 for sdhci

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bhushan Shah [ Upstream commit 03864e57770a9541e7ff3990bacf2d9a2fffcd5d ] The kernel would not boot on the hammerhead hardware due to the following error: mmc0: Timeout waiting for hardware i

[PATCH 4.14 098/173] USB: yurex: Fix buffer over-read in yurex_write()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 7e10f14ebface44a48275c8d6dc1caae3668d5a9 upstream. If the written data starts with a digit, yurex_write() tries to parse it as an integer using simple_strtoull(). This re

[PATCH 4.14 063/173] s390/qeth: fix race in used-buffer accounting

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit a702349a4099cd5a7bab0904689d8e0bf8dcd622 ] By updating q->used_buffers only _after_ do_QDIO() has completed, there is a potential race against the buffer's TX

[PATCH 4.14 101/173] cifs: prevent integer overflow in nxt_dir_entry()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 8ad8aa353524d89fa2e09522f3078166ff78ec42 upstream. The "old_entry + le32_to_cpu(pDirInfo->NextEntryOffset)" can wrap around so I have added a check for integer overflow.

[PATCH 4.14 067/173] drivers/base: stop new probing during shutdown

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Pingfan Liu [ Upstream commit 3297c8fc65af5d40501ea7cddff1b195cae57e4e ] There is a race window in device_shutdown(), which may cause -1. parent device shut down before child or -2. no shutdow

[PATCH 0/2] KEYS: Revert and replace incorrect UAPI fix

Hi James, Here's a pair of fixes that need to go upstream asap, please: (1) Revert an incorrect fix to the keyrings UAPI for a C++ reserved word used as a struct member name. This change being reverted breaks existing userspace code and is thus incorrect. Further, *neither* na

[PATCH 4.14 064/173] s390/qeth: reset layer2 attribute on layer switch

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 70551dc46ffa3555a0b5f3545b0cd87ab67fd002 ] After the subdriver's remove() routine has completed, the card's layer mode is undetermined again. Reflect this in

[PATCH 4.14 099/173] usb: cdc-wdm: Fix a sleep-in-atomic-context bug in service_outstanding_interrupt()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai commit 6e22e3af7bb3a7b9dc53cb4687659f6e63fca427 upstream. wdm_in_callback() is a completion handler function for the USB driver. So it should not sleep. But it calls service_outstan

[PATCH 4.14 065/173] platform/x86: toshiba_acpi: Fix defined but not used build warnings

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit c2e2a618eb7104e18fdcf739d4d911563812a81c ] Fix a build warning in toshiba_acpi.c when CONFIG_PROC_FS is not enabled by marking the unused function as __maybe_unu

[PATCH 4.14 058/173] efi/arm: preserve early mapping of UEFI memory map longer for BGRT

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel [ Upstream commit 3ea86495aef2f6de26b7cb1599ba350dd6a0c521 ] The BGRT code validates the contents of the table against the UEFI memory map, and so it expects it to be mapped whe

[PATCH 4.14 115/173] KVM: PPC: Book3S HV: Add of_node_put() in success path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire [ Upstream commit 51eaa08f029c7343df846325d7cf047be8b96e81 ] The call to of_find_compatible_node() is returning a pointer with incremented refcount so it must be explicitly d

[PATCH 4.14 114/173] evm: Dont deadlock if a crypto algorithm is unavailable

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Matthew Garrett [ Upstream commit e2861fa71641c6414831d628a1f4f793b6562580 ] When EVM attempts to appraise a file signed with a crypto algorithm the kernel doesn't have support for, it will ca

[PATCH 2/2] keys: Fix the use of the C++ keyword "private" in uapi/linux/keyctl.h

The keyctl_dh_params struct in uapi/linux/keyctl.h contains the symbol "private" which means that the header file will cause compilation failure if #included in to a C++ program. Further, the patch that added the same struct to the keyutils package named the symbol "priv", not "private". The prev

[PATCH 4.14 113/173] Bluetooth: Use lock_sock_nested in bt_accept_enqueue

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Philipp Puschmann [ Upstream commit b71c69c26b4916d11b8d403d8e667bbd191f1b8f ] Fixes this warning that was provoked by a pairing: [60258.016221] WARNING: possible recursive locking detected [

[PATCH 4.14 116/173] security: check for kstrdup() failure in lsm_append()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers [ Upstream commit 87ea58433208d17295e200d56be5e2a4fe4ce7d6 ] lsm_append() should return -ENOMEM if memory allocation failed. Fixes: d69dece5f5b6 ("LSM: Add /sys/kernel/security/l

[PATCH 4.14 111/173] mtdchar: fix overflows in adjustment of `count`

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn [ Upstream commit 6c6bc9ea84d0008024606bf5ba10519e20d851bf ] The first checks in mtdchar_read() and mtdchar_write() attempt to limit `count` such that `*ppos + count <= mtd->size`. H

[PATCH 1/2] Revert "uapi/linux/keyctl.h: don't use C++ reserved keyword as a struct member name"

From: Lubomir Rintel This changes UAPI, breaking iwd and libell: ell/key.c: In function 'kernel_dh_compute': ell/key.c:205:38: error: 'struct keyctl_dh_params' has no member named 'private'; did you mean 'dh_private'? struct keyctl_dh_params params = { .private = private,

[PATCH 4.14 066/173] KVM: arm/arm64: Fix vgic init race

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christoffer Dall [ Upstream commit 1d47191de7e15900f8fbfe7cccd7c6e1c2d7c31a ] The vgic_init function can race with kvm_arch_vcpu_create() which does not hold kvm_lock() and we therefore have n

[PATCH 4.14 112/173] vfs: fix freeze protection in mnt_want_write_file() for overlayfs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi [ Upstream commit a6795a585929d94ca3e931bc8518f8deb8bbe627 ] The underlying real file used by overlayfs still contains the overlay path. This results in mnt_want_write_file() ca

[PATCH 4.14 110/173] audit: fix use-after-free in audit_add_watch

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ronny Chevalier [ Upstream commit baa2a4fdd525c8c4b0f704d20457195b29437839 ] audit_add_watch stores locally krule->watch without taking a reference on watch. Then, it calls audit_add_to_parent

[PATCH 4.14 081/173] ipmi: Fix I2C client removal in the SSIF driver

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Corey Minyard commit 0745dde62835be7e2afe62fcdb482fcad79cb743 upstream. The SSIF driver was removing any client that came in through the platform interface, but it should only remove clients t

[PATCH 4.14 118/173] configfs: fix registered group removal

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mike Christie [ Upstream commit cc57c07343bd071cdf1915a91a24ab7d40c9b590 ] This patch fixes a bug where configfs_register_group had added a group in a tree, and userspace has done a rmdir on a

[PATCH 4.14 121/173] sched/core: Use smp_mb() in wake_woken_function()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andrea Parri [ Upstream commit 76e079fefc8f62bd9b2cd2950814d1ee806e31a5 ] wake_woken_function() synchronizes with wait_woken() as follows: [wait_woken] [wake_woken_fun

[PATCH 4.14 102/173] CIFS: fix wrapping bugs in num_entries()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 56446f218af1133c802dad8e9e116f07f381846c upstream. The problem is that "entryptr + next_offset" and "entryptr + len + size" can wrap. I ended up changing the type of "ent

[PATCH 4.14 120/173] pinctrl: pinmux: Return selector to the pinctrl driver

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren [ Upstream commit f913cfce4ee49a3382a9ff95696f49a46e56e974 ] We must return the selector from pinmux_generic_add_function() so pin controller device drivers can remove the right

[PATCH 4.14 119/173] pinctrl: rza1: Fix selector use for groups and functions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren [ Upstream commit dc4003d260594aa300028c3c5d040c5719abd19b ] We must use a mutex around the generic_add functions and save the function and group selector in case we need to remo

[PATCH 4.14 127/173] gpu: ipu-v3: csi: pass back mbus_code_to_bus_cfg error codes

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Enrico Scholz [ Upstream commit d36d0e6309dd8137cf438cbb680e72eb63c81425 ] mbus_code_to_bus_cfg() can fail on unknown mbus codes; pass back the error to the caller. Signed-off-by: Enrico Scho

[PATCH 4.14 128/173] tty: fix termios input-speed encoding when using BOTHER

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold [ Upstream commit 1cee38f0363a88db374e50b232ca17b9a4c12fa0 ] When the termios CIBAUD bits are left unset (i.e. B0), we use the same output and input speed and should leave CIBAUD

[PATCH 4.14 126/173] liquidio: fix hang when re-binding VF host drv after running DPDK VF driver

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rick Farrington [ Upstream commit ac13d6d8eaded15c67265eafc32f439ea3a0ac4a ] When configuring SLI_PKTn_OUTPUT_CONTROL, VF driver was assuming that IPTR mode was disabled by reset, which was no

[PATCH 4.14 123/173] ARM: hisi: handle of_iomap and fix missing of_node_put

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire [ Upstream commit d396cb185c0337aae5664b250cdd9a73f6eb1503 ] Relying on an unchecked of_iomap() which can return NULL is problematic here, an explicit check seems mandatory.

[PATCH 4.14 129/173] tty: fix termios input-speed encoding

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold [ Upstream commit fada18c48d774b9e837928ecdce6a5d5fdd11ee7 ] Make sure to clear the CIBAUD bits before OR-ing the new mask when encoding the termios input baud rate. This could o

[PATCH 4.14 125/173] ARM: hisi: check of_iomap and fix missing of_node_put

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire [ Upstream commit 81646a3d39ef14749301374a3a0b8311384cd412 ] of_find_compatible_node() returns a device node with refcount incremented and thus needs an explicit of_node_put(

[PATCH 4.14 122/173] efi/esrt: Only call efi_mem_reserve() for boot services memory

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel [ Upstream commit 61f0d55569463a1af897117ff47d202b0ccb2e24 ] The following commit: 7e1550b8f208 ("efi: Drop type and attribute checks in efi_mem_desc_lookup()") refactored t

[PATCH 4.14 124/173] ARM: hisi: fix error handling and missing of_node_put

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire [ Upstream commit 9f30b5ae0585ca5234fe979294b8f897299dec99 ] of_iomap() can return NULL which seems critical here and thus should be explicitly flagged so that the cause of s

[PATCH 4.14 103/173] xtensa: ISS: dont allocate memory in platform_setup

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit ef439d49e0bfb26cd5f03c88b4cb7cc9073ed30c upstream. Memory allocator is not initialized at that point yet, use static array instead. Cc: sta...@vger.kernel.org Signed-off-b

[PATCH 4.14 134/173] drm/nouveau/debugfs: Wake up GPU before doing any reclocking

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Karol Herbst [ Upstream commit eaeb9010bb4bcdc20e58254fa42f3fe730a7f908 ] Fixes various reclocking related issues on prime systems. Signed-off-by: Karol Herbst Signed-off-by: Martin Peres S

[PATCH 4.14 136/173] parport: sunbpp: fix error return code

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Julia Lawall [ Upstream commit faa1a47388b33623e4d504c23569188907b039a0 ] Return an error code on failure. Change leading spaces to tab on the first if. Problem found using Coccinelle. Sign

[PATCH 4.14 133/173] drm/nouveau: Fix runtime PM leak in drm_open()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul [ Upstream commit 922a8c82fafdec99688bbaea6c5889f562a42cdc ] Noticed this as I was skimming through, if we fail to allocate memory for cli we'll end up returning without dropping th

[PATCH 4.14 131/173] mmc: tegra: prevent HS200 on Tegra 3

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Agner [ Upstream commit 127407e36f4fe3a1d5e8b9998b479956ce83a7dc ] The stack assumes that SDHC controller which support SD3.0 (SDR104) do support HS200. This is not the case for Tegra 3

[PATCH 4.14 130/173] mmc: sdhci-of-esdhc: set proper dma mask for ls104x chips

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Laurentiu Tudor [ Upstream commit 5552d7ad596c3fea953f40fef74170ce0760c04d ] SDHCI controller in ls1043a and ls1046a generate 40-bit wide addresses when doing DMA. Make sure that the correspon

[PATCH 4.14 132/173] mmc: sdhci: do not try to use 3.3V signaling if not supported

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Agner [ Upstream commit 1b5190c2e74c47ebe4bcecf7a072358ad9f1feaa ] For eMMC devices it is valid to only support 1.8V signaling. When vqmmc is set to a fixed 1.8V regulator the stack tri

[PATCH 4.14 135/173] drm/nouveau: tegra: Detach from ARM DMA/IOMMU mapping

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thierry Reding [ Upstream commit b59fb482b52269977ee5de205308e5b236a03917 ] Depending on the kernel configuration, early ARM architecture setup code may have attached the GPU to a DMA/IOMMU ma

[PATCH 4.14 137/173] sched/fair: Fix util_avg of new tasks for asymmetric systems

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Quentin Perret [ Upstream commit 8fe5c5a937d0f4e84221631833a2718afde52285 ] When a new task wakes-up for the first time, its initial utilization is set to half of the spare capacity of its CPU

[PATCH 4.14 138/173] coresight: Handle errors in finding input/output ports

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Suzuki K Poulose [ Upstream commit fe470f5f7f684ed15bc49b6183a64237547910ff ] If we fail to find the input / output port for a LINK component while enabling a path, we should fail gracefully r

[PATCH 4.14 139/173] coresight: tpiu: Fix disabling timeouts

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Robin Murphy [ Upstream commit ccff2dfaceaca4517432f5c149594215fe9098cc ] Probing the TPIU driver under UBSan triggers an out-of-bounds shift warning in coresight_timeout(): ... [5.677530

[PATCH 4.14 140/173] coresight: ETM: Add support for Arm Cortex-A73 and Cortex-A35

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Suzuki K Poulose [ Upstream commit 5cedd22370a0a460b663c06de1fc10b4ba3c5d0b ] Add ETM PIDs of the Arm cortex-A CPUs to the white list of ETMs. While at it add a helper macro to make it easier

[PATCH 4.14 106/173] NFSv4.1 fix infinite loop on I/O.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 994b15b983a72e1148a173b61e5b279219bb45ae upstream. The previous fix broke recovery of delegated stateids because it assumes that if we did not mark the delegation as sus

[PATCH 4.14 109/173] arm64: dts: uniphier: Add missing cooling device properties for CPUs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar [ Upstream commit af0e09d0c6762e486b0eb5cc4737396964c34fad ] The cooling device properties, like "#cooling-cells" and "dynamic-power-coefficient", should either be present for all

[PATCH 4.14 142/173] gpio: pxa: Fix potential NULL dereference

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun [ Upstream commit 9506755633d0b32ef76f67c345000178e9b0dfc4 ] platform_get_resource() may fail and return NULL, so we should better check it's return value to avoid a NULL pointer d

[PATCH 4.14 152/173] drm/panel: type promotion bug in s6e8aa0_read_mtp_id()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit cd0e0ca69109d025b1a1b6609f70682db62138b0 ] The ARRAY_SIZE() macro is type size_t. If s6e8aa0_dcs_read() returns a negative error code, then "ret < ARRAY_SIZE(i

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