[PATCH 4.18 073/235] arm64: fix possible spectre-v1 write in ptrace_hbp_set_event()

4.18-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

[PATCH 4.18 072/235] wan/fsl_ucc_hdlc: use IS_ERR_VALUE() to check return value of qe_muram_alloc

4.18-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.18 039/235] media: videobuf2-core: check for q->error in vb2_core_qbuf()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil [ Upstream commit b509d733d337417bcb7fa4a35be3b9a49332b724 ] The vb2_core_qbuf() function didn't check if q->error was set. It is checked in __buf_prepare(), but that function

[PATCH 4.18 079/235] arm64: dts: qcom: db410c: Fix Bluetooth LED trigger

4.18-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'

[PATCH 4.18 091/235] iommu/ipmmu-vmsa: IMUCTRn.TTSEL needs a special usage on R-Car Gen3

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda [ Upstream commit 2ae86955703e9e6a119af4bbe27f6b6dd7a43131 ] The TTSEL bit of IMUCTRn register of R-Car Gen3 needs to be set unused MMU context number even if uTLBs are

[PATCH 4.18 093/235] crypto: sharah - Unregister correct algorithms for SAHARA 3

4.18-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

[PATCH 4.18 045/235] perf test: Fix subtest number when showing results

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Richter [ Upstream commit 9ef0112442bdddef5fb55adf20b3a5464b33de75 ] Perf test 40 for example has several subtests numbered 1-4 when displaying the start of the subtest. When the

[PATCH 4.18 048/235] perf tests: Fix record+probe_libc_inet_pton.sh for powerpc64

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sandipan Das [ Upstream commit 3eae52f842329a95f8549124079518231c0daba8 ] For powerpc64, this test currently fails due to a mismatch in the expected output. This can be observed on a

[PATCH 4.18 044/235] media: ov5645: Supported external clock is 24MHz

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Todor Tomov [ Upstream commit 4adb0a0432f489c5eb802b33dae7737f69e6fd7a ] The external clock frequency was set to 23.88MHz by mistake because of a platform which cannot get closer to 24MHz.

[PATCH 4.18 123/235] usb: Avoid use-after-free by flushing endpoints early in usb_set_interface()

4.18-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

[PATCH 4.18 089/235] regulator: qcom_spmi: Use correct regmap when checking for error

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Niklas Cassel [ Upstream commit 85046a15529606466bc778e1205f4cab8e3724d1 ] Since we have just assigned saw_regmap, and since the error message refers to saw_regmap, it feels safe to assume

[PATCH 4.18 136/235] cifs: integer overflow in in SMB2_ioctl()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 2d204ee9d671327915260071c19350d84344e096 upstream. The "le32_to_cpu(rsp->OutputOffset) + *plen" addition can overflow and wrap around to a smaller value which looks like

[PATCH 4.18 135/235] CIFS: fix wrapping bugs in num_entries()

4.18-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

[PATCH 4.18 134/235] cifs: prevent integer overflow in nxt_dir_entry()

4.18-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.18 088/235] drm/amd/pp: Set Max clock level to display by default

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rex Zhu [ Upstream commit 97e8f102f5a9123d30258e196c6c1ea29cf52e83 ] avoid the error in dmesg: [drm:dm_pp_get_static_clocks] *ERROR* DM_PPLIB: invalid powerlevel state: 0! Reviewed-by: Alex

[PATCH 4.18 133/235] Revert "cdc-acm: implement put_char() and flush_chars()"

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit df3aa13c7bbb307e172c37f193f9a7aa058d4739 upstream. This reverts commit a81cf9799ad7299b03a4dff020d9685f9ac5f3e0. The patch causes a regression, which I cannot find the

[PATCH 4.18 137/235] xtensa: ISS: dont allocate memory in platform_setup

4.18-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

[PATCH 4.18 132/235] usb: cdc-wdm: Fix a sleep-in-atomic-context bug in service_outstanding_interrupt()

4.18-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

[PATCH 4.18 139/235] perf tools: Fix maps__find_symbol_by_name()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 03db8b583d1c3c84963e08e2abf6c79081da5c31 upstream. Commit 1c5aae7710bb ("perf machine: Create maps for x86 PTI entry trampolines") revealed a problem with

[PATCH 4.18 138/235] perf/core: Force USER_DS when recording user stack data

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Yabin Cui commit 02e184476eff848273826c1d6617bb37e5bcc7ad upstream. Perf can record user stack data in response to a synchronous request, such as a tracepoint firing. If this happens under

[PATCH 4.18 143/235] NFSv4.1 fix infinite loop on I/O.

4.18-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

[PATCH 4.18 124/235] usb: host: u132-hcd: Fix a sleep-in-atomic-context bug in u132_get_frame()

4.18-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

[PATCH 4.18 140/235] of: fix phandle cache creation for DTs with no phandles

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rob Herring commit e54192b48da75f025ae4b277925eaf6aca1d13bd upstream. With commit 0b3ce78e90fc ("of: cache phandle nodes to reduce cost of of_find_node_by_phandle()"), a G3 PowerMac fails to

[PATCH 4.18 144/235] of: add helper to lookup compatible child node

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 36156f9241cb0f9e37d998052873ca7501ad4b36 upstream. Add of_get_compatible_child() helper that can be used to lookup compatible child nodes. Several drivers currently use

[PATCH 4.18 040/235] IB/rxe: Drop QP0 silently

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Zhu Yanjun [ Upstream commit 536ca245c512aedfd84cde072d7b3ca14b6e1792 ] According to "Annex A16: RDMA over Converged Ethernet (RoCE)": A16.4.3 MANAGEMENT INTERFACES As defined in the base

Re: [PATCH 06/10] irqchip/gic-v3-its: Allow use of pre-programmed LPI tables

On 21/09/18 20:59, Marc Zyngier wrote: In order to cope with kexec and GICv3, let's try and spot when we're booting with LPIs already enabled, and the tables already programmed into the redistributors. This code is currently guarded by a predicate that is always false, meaning this is not

[PATCH 4.18 085/235] KVM: arm/arm64: Fix vgic init race

4.18-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

[PATCH v3 2/4] mm: move is_kernel_rodata() to asm-generic/sections.h

Export this routine so that we can use it later in devm_kstrdup_const() and devm_kfree_const(). Signed-off-by: Bartosz Golaszewski Reviewed-by: Bjorn Andersson --- include/asm-generic/sections.h | 14 ++ mm/util.c | 7 --- 2 files changed, 14

Re: [PATCH] tools/memory-model: Model smp_mb__after_unlock_lock()

On Mon, Sep 24, 2018 at 12:44:49PM +0200, Andrea Parri wrote: > From the header comment for smp_mb__after_unlock_lock(): > > "Place this after a lock-acquisition primitive to guarantee that >an UNLOCK+LOCK pair acts as a full barrier. This guarantee applies >if the UNLOCK and LOCK are

Re: [PATCH 02/10] irqchip/gic-v3-its: Consolidate LPI_PENDBASE_SZ usage

On 24/09/18 11:54, Suzuki K Poulose wrote: On 24/09/18 11:50, Julien Thierry wrote: Hi, On 24/09/18 11:33, Suzuki K Poulose wrote: Hi Marc, On 21/09/18 20:59, Marc Zyngier wrote: LPI_PENDING_SZ is always used in conjunction with a max(). Let's factor this in the definition of the

[PATCH v9 1/5] dt-bindings: add binding for i.MX8MQ CCM

From: Lucas Stach This adds the binding for the i.MX8MQ Clock Controller Module. Signed-off-by: Lucas Stach Signed-off-by: Abel Vesa Reviewed-by: Rob Herring --- .../devicetree/bindings/clock/imx8mq-clock.txt | 20 ++ include/dt-bindings/clock/imx8mq-clock.h | 395

[PATCH 3.18 008/105] mm/fadvise.c: fix signed overflow UBSAN complaint

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin [ Upstream commit a718e28f538441a3b6612da9ff226973376cdf0f ] Signed integer overflow is undefined according to the C standard. The overflow in ksys_fadvise64_64() is

[PATCH 3.18 000/105] 3.18.123-stable review

This is the start of the stable review cycle for the 3.18.123 release. There are 105 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 Sep 26 11:30:30 UTC 2018. Anything

[PATCH 3.18 005/105] reiserfs: change j_timestamp type to time64_t

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 8b73ce6a4bae4fe12bcb2c361c0da4183c2e1b6f ] This uses the deprecated time_t type but is write-only, and could be removed, but as Jeff explains, having a

[PATCH 3.18 006/105] fat: validate ->i_start before using

3.18-stable review patch. If anyone has any objections, please let me know. -- From: OGAWA Hirofumi [ Upstream commit 0afa9626667c3659ef8bd82d42a11e39fedf235c ] On corrupted FATfs may have invalid ->i_start. To handle it, this checks ->i_start before using, and return proper

[PATCH 3.18 004/105] fork: dont copy inconsistent signal handler state to child

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn [ Upstream commit 06e62a46bbba20aa5286102016a04214bb446141 ] Before this change, if a multithreaded process forks while one of its threads is changing a signal handler using

[PATCH 3.18 040/105] scsi: target: fix __transport_register_session locking

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mike Christie [ Upstream commit 6a64f6e1591322beb8ce16e952a53582caf2a15c ] When __transport_register_session is called from transport_register_session irqs will already have been disabled, so

[PATCH 3.18 007/105] scripts: modpost: check memory allocation results

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit 1f3aa9002dc6a0d59a4b599b4fc8f01cf43ef014 ] Fix missing error check for memory allocation functions in scripts/mod/modpost.c. Fixes kernel bugzilla #200319:

[PATCH 3.18 031/105] Fixes: Commit 86af955d02bb ("mm: numa: avoid waiting on freed migrated pages")

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chas Williams Commit 86af955d02bb ("mm: numa: avoid waiting on freed migrated pages") was an incomplete backport of the upstream commit. It is necessary to always reset page_nid before

[PATCH 3.18 041/105] md/raid5: fix data corruption of replacements after originals dropped

3.18-stable review patch. If anyone has any objections, please let me know. -- From: BingJing Chang [ Upstream commit d63e2fc804c46e50eee825c5d3a7228e07048b47 ] During raid5 replacement, the stripes can be marked with R5_NeedReplace flag. Data can be read from being-replaced

[PATCH 3.18 003/105] hfs: prevent crash on exit from failed search

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "Ernesto A. Fernández" [ Upstream commit dc2572791d3a41bab94400af2b6bca9d71ccd303 ] hfs_find_exit() expects fd->bnode to be NULL after a search has failed. hfs_brec_insert() may instead set

[PATCH 3.18 009/105] ipvs: fix race between ip_vs_conn_new() and ip_vs_del_dest()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tan Hu [ Upstream commit a53b42c11815d2357e31a9403ae3950517525894 ] We came across infinite loop in ipvs when using ipvs in docker env. When ipvs receives new packets and cannot find an ipvs

[PATCH 3.18 046/105] MIPS: Fix ISA virt/bus conversion for non-zero PHYS_OFFSET

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Burton [ Upstream commit 0494d7ffdcebc6935410ea0719b24ab626675351 ] isa_virt_to_bus() & isa_bus_to_virt() claim to treat ISA bus addresses as being identical to physical addresses, but

Re: [PATCH 0/2] gpiolib: Fix issues introduced by fast bitmap processing path

Hi Janusz, On 2018-09-24 13:08, Janusz Krzysztofik wrote: > 2018-09-24 11:43 GMT+02:00, Marek Szyprowski : >> On 2018-09-24 01:53, Janusz Krzysztofik wrote: >>> While investigating possible reasons of GPIO fast bitmap processing >>> related boot hang on Samsung Snow Chromebook, reported by Marek

[PATCH 3.18 002/105] hfsplus: dont return 0 when fill_super() failed

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa [ Upstream commit 7464726cb5998846306ed0a7d6714afb2e37b25d ] syzbot is reporting NULL pointer dereference at mount_fs() [1]. This is because hfsplus_fill_super() is by error

[PATCH 3.18 029/105] irda: Only insert new objects into the global database via setsockopt

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tyler Hicks The irda_setsockopt() function conditionally allocates memory for a new self->ias_object or, in some cases, reuses the existing self->ias_object. Existing objects were incorrectly

[PATCH 3.18 026/105] debugobjects: Make stack check warning more informative

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Joel Fernandes (Google) commit fc91a3c4c27acdca0bc13af6fbb68c35cfd519f2 upstream. While debugging an issue debugobject tracking warned about an annotation issue of an object on stack. It

[PATCH 3.18 027/105] kbuild: make missing $DEPMOD a Warning instead of an Error

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap commit 914b087ff9e0e9a399a4927fa30793064afc0178 upstream. When $DEPMOD is not found, only print a warning instead of exiting with an error message and error status: Warning:

[PATCH 3.18 042/105] uio: potential double frees if __uio_register_device() fails

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit f019f07ecf6a6b8bd6d7853bce70925d90af02d1 ] The uio_unregister_device() function assumes that if "info->uio_dev" is non-NULL that means "info" is fully

[PATCH 3.18 043/105] tty: rocket: Fix possible buffer overwrite on register_PCI

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 0419056ec8fd01ddf5460d2dba0491aad22657dd ] If number of isa and pci boards exceed NUM_BOARDS on the path rp_init()->init_PCI()->register_PCI() then buffer

[PATCH 3.18 045/105] ath10k: prevent active scans on potential unusable channels

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sven Eckelmann [ Upstream commit 3f259111583801013cb605bb4414aa529adccf1c ] The QCA4019 hw1.0 firmware 10.4-3.2.1-00050 and 10.4-3.5.3-00053 (and most likely all other) seem to ignore the

[PATCH 3.18 044/105] macintosh/via-pmu: Add missing mmio accessors

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain [ Upstream commit 576d5290d678a651b9f36050fc1717e0573aca13 ] Add missing in_8() accessors to init_pmu() and pmu_sr_intr(). This fixes several sparse warnings:

[PATCH 3.18 028/105] irda: Fix memory leak caused by repeated binds of irda socket

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tyler Hicks The irda_bind() function allocates memory for self->ias_obj without checking to see if the socket is already bound. A userspace process could repeatedly bind the socket, have each

[PATCH 3.18 105/105] USB: serial: ti_usb_3410_5052: fix array underflow in completion handler

3.18-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

[PATCH 3.18 103/105] drm/panel: type promotion bug in s6e8aa0_read_mtp_id()

3.18-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 <

Re: [PATCH crypto-next 06/23] x86/fpu: Remove VLA usage of skcipher

On Wed, 19 Sep 2018 at 04:11, Kees Cook wrote: > > In the quest to remove all stack VLA usage from the kernel[1], this > replaces struct crypto_skcipher and SKCIPHER_REQUEST_ON_STACK() usage > with struct crypto_sync_skcipher and SYNC_SKCIPHER_REQUEST_ON_STACK(), > which uses a fixed stack size.

[PATCH 3.18 102/105] ALSA: pcm: Fix snd_interval_refine first/last with open min/max

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Timo Wischer [ Upstream commit ff2d6acdf6f13d9f8fdcd890844c6d7535ac1f10 ] Without this commit the following intervals [x y), (x y) were be replaced to (y-1 y) by snd_interval_refine_last().

[PATCH 3.18 104/105] IB/nes: Fix a compiler warning

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit 4c5743bc4fe3233cecc1c184a773c79c8ee45bbe ] Avoid that the following compiler warning is reported when building with W=1:

[PATCH 3.18 047/105] ata: libahci: Correct setting of DEVSLP register

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Pandruvada [ Upstream commit 2dbb3ec29a6c069035857a2fc4c24e80e5dfe3cc ] We have seen that on some platforms, SATA device never show any DEVSLP residency. This prevent power gating of

[PATCH 3.18 077/105] s390/qeth: reset layer2 attribute on layer switch

3.18-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 3.18 078/105] platform/x86: toshiba_acpi: Fix defined but not used build warnings

3.18-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

[PATCH 3.18 058/105] MIPS: WARN_ON invalid DMA cache maintenance, not BUG_ON

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Burton [ Upstream commit d4da0e97baea8768b3d66ccef3967bebd50dfc3b ] If a driver causes DMA cache maintenance with a zero length then we currently BUG and kill the kernel. As this is a

[PATCH 3.18 101/105] rtc: bq4802: add error handling for devm_ioremap

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Zhouyang Jia [ Upstream commit 7874b919866ba91bac253fa219d3d4c82bb944df ] When devm_ioremap fails, the lack of error-handling code may cause unexpected results. This patch adds

[PATCH 3.18 075/105] mac80211: restrict delayed tailroom needed decrement

3.18-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

[PATCH 3.18 079/105] RDMA/cma: Protect cma dev list with lock

3.18-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

[PATCH 4.9 018/111] mtd/maps: fix solutionengine.c printk format warnings

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit 1d25e3eeed1d987404e2d2e451eebac8c15cecc1 ] Fix 2 printk format warnings (this driver is currently only used by arch/sh/) by using "%pap" instead of "%lx". Fixes

[PATCH 4.9 002/111] rds: fix two RCU related problems

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit cc4dfb7f70a344f24c1c71e298deea0771dadcb2 ] When a rds sock is bound, it is inserted into the bind_hash_table which is protected by RCU. But when releasing rds sock,

[PATCH 4.9 014/111] dmaengine: pl330: fix irq race with terminate_all

4.9-stable review patch. If anyone has any objections, please let me know. -- From: John Keeping [ Upstream commit e49756544a21f5625b379b3871d27d8500764670 ] In pl330_update() when checking if a channel has been aborted, the channel's lock is not taken, only the overall

[PATCH 4.9 016/111] media: videobuf2-core: check for q->error in vb2_core_qbuf()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil [ Upstream commit b509d733d337417bcb7fa4a35be3b9a49332b724 ] The vb2_core_qbuf() function didn't check if q->error was set. It is checked in __buf_prepare(), but that function

[PATCH 4.9 013/111] media: tw686x: Fix oops on buffer alloc failure

4.9-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

[PATCH 4.9 017/111] IB/rxe: Drop QP0 silently

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Zhu Yanjun [ Upstream commit 536ca245c512aedfd84cde072d7b3ca14b6e1792 ] According to "Annex A16: RDMA over Converged Ethernet (RoCE)": A16.4.3 MANAGEMENT INTERFACES As defined in the base

[PATCH 4.9 019/111] perf test: Fix subtest number when showing results

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Richter [ Upstream commit 9ef0112442bdddef5fb55adf20b3a5464b33de75 ] Perf test 40 for example has several subtests numbered 1-4 when displaying the start of the subtest. When the

[PATCH 4.9 024/111] perf powerpc: Fix callchain ip filtering when return address is in a register

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sandipan Das [ Upstream commit 9068533e4f470daf2b0f29c71d865990acd8826e ] For powerpc64, perf will filter out the second entry in the callchain, i.e. the LR value, if the return address of the

[PATCH 4.9 020/111] gfs2: Dont reject a supposedly full bitmap if we have blocks reserved

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bob Peterson [ Upstream commit e79e0e1428188b24c3b57309ffa54a33c4ae40c4 ] Before this patch, you could get into situations like this: 1. Process 1 searches for X free blocks, finds them,

[PATCH 4.9 012/111] kbuild: add .DELETE_ON_ERROR special target

4.9-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

Re: [PATCH v4 2/3] pinctrl: renesas: Renesas RZ/N1 pinctrl driver

Hi Phil, On Wed, Sep 19, 2018 at 4:24 PM Phil Edworthy wrote: > This provides a pinctrl driver for the Renesas RZ/N1 device family. > > Based on a patch originally written by Michel Pollet at Renesas. > > Signed-off-by: Phil Edworthy Thanks for your patch! > --- /dev/null > +++

[PATCH 4.9 023/111] fbdev/via: fix defined but not used warning

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

r8169 hang on 4.18

Hi, Stable kernel has stability problems on r8169 that were not present in 4.17.3: [0.00] Linux version 4.18.8 (kbuild@lofw) (gcc version 7.3.0 (Gentoo 7.3.0-r3 p1.4)) #70 SMP PREEMPT Mon Sep 17 17:56:57 CEST 2018 [0.00] Command line: BOOT_IMAGE=/boot/linux-4.18.8

[PATCH 4.9 021/111] fbdev: omapfb: off by one in omapfb_register_client()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 5ec1ec35b2979b59d0b33381e7c9aac17e159d16 ] The omapfb_register_client[] array has OMAPFB_PLANE_NUM elements so the > should be >= or we are one element beyond

[PATCH 4.9 015/111] MIPS: ath79: fix system restart

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau [ Upstream commit f8a7bfe1cb2c1ebfa07775c9c8ac0ad3ba8e5ff5 ] This patch disables irq on reboot to fix hang issues that were observed due to pending interrupts. Signed-off-by:

[PATCH 4.9 025/111] video: fbdev: pxafb: clear allocated memory for video modes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Mack [ Upstream commit b951d80aaf224b1f774e10def672f5e37488e4ee ] When parsing the video modes from DT properties, make sure to zero out memory before using it. This is important

[PATCH 4.9 022/111] video: goldfishfb: fix memory leak on driver remove

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 5958fde72d04e7b8c6de3669d1f794a90997e3eb ] goldfish_fb_probe() allocates memory for fb, but goldfish_fb_remove() does not have deallocation of fb, which leads

Re: KASAN: use-after-free Read in fuse_dev_do_read

On 22.09.2018 22:30, syzbot wrote: > syzbot has found a reproducer for the following crash on: > > HEAD commit:    10dc890d4228 Merge tag 'pinctrl-v4.19-3' of git://git.kern.. > git tree:   upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=1631cfbe40 > kernel config: 

[PATCH 4.9 072/111] NFSv4.1 fix infinite loop on I/O.

4.9-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

[PATCH 4.9 094/111] rcu: Fix grace-period hangs due to race with CPU offline

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Paul E. McKenney" [ Upstream commit 1e64b15a4b102e1cd059d4d798b7a78f93341333 ] Without special fail-safe quiescent-state-propagation checks, grace-period hangs can result from the following

[PATCH 4.9 073/111] binfmt_elf: Respect error return from `regset->active

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Maciej W. Rozycki" [ Upstream commit 2f819db565e82e5f73cd42b39925098986693378 ] The regset API documented in defines -ENODEV as the result of the `->active' handler to be used where the

[PATCH 4.9 102/111] pinctrl: qcom: spmi-gpio: Fix pmic_gpio_config_get() to be compliant

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Douglas Anderson [ Upstream commit 1cf86bc21257a330e3af51f2a4e885f1a705f6a5 ] If you do this on an sdm845 board: grep "" /sys/kernel/debug/pinctrl/*spmi:pmic*/pinconf-groups ...it looks

[PATCH 4.9 097/111] ALSA: pcm: Fix snd_interval_refine first/last with open min/max

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Timo Wischer [ Upstream commit ff2d6acdf6f13d9f8fdcd890844c6d7535ac1f10 ] Without this commit the following intervals [x y), (x y) were be replaced to (y-1 y) by snd_interval_refine_last().

[PATCH 4.9 101/111] gpiolib: Respect error code of ->get_direction()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko [ Upstream commit 36b312792b97933dc07abe074f50941199bd357c ] In case we try to lock GPIO pin as IRQ when something going wrong we print a misleading message. Correct this by

[PATCH 4.9 100/111] IB/nes: Fix a compiler warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit 4c5743bc4fe3233cecc1c184a773c79c8ee45bbe ] Avoid that the following compiler warning is reported when building with W=1:

[PATCH 4.9 095/111] drm/amdkfd: Fix error codes in kfd_get_process

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Wei Lu [ Upstream commit e47cb828eb3fca3e8999a0b9aa053dda18552071 ] Return ERR_PTR(-EINVAL) if kfd_get_process fails to find the process. This fixes kernel oopses when a child process calls

[PATCH 4.9 103/111] mei: bus: type promotion bug in mei_nfc_if_version()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit b40b3e9358fbafff6a4ba0f4b9658f6617146f9c upstream. We accidentally removed the check for negative returns without considering the issue of type promotion. The

[PATCH 4.9 105/111] e1000e: Remove Other from EIAC

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Poirier commit 745d0bd3af99ccc8c5f5822f808cd133eadad6ac upstream. It was reported that emulated e1000e devices in vmware esxi 6.5 Build 7526125 do not link up after commit

[PATCH 4.9 088/111] coresight: Handle errors in finding input/output ports

4.9-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

[PATCH 4.9 092/111] mfd: 88pm860x-i2c: switch to i2c_lock_bus(..., I2C_LOCK_SEGMENT)

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Rosin [ Upstream commit 8c8f74f327a76604a499fad8c54c15e1c0ee8051 ] Locking the root adapter for __i2c_transfer will deadlock if the device sits behind a mux-locked I2C mux. Switch to the

[PATCH 4.9 091/111] gpiolib: Mark gpio_suffixes array with __maybe_unused

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko [ Upstream commit b23ec59926faf05b0c43680d05671c484e810ac4 ] Since we put static variable to a header file it's copied to each module that includes the header. But not all of

[PATCH 4.9 090/111] gpio: pxa: Fix potential NULL dereference

4.9-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

[PATCH 4.9 089/111] coresight: tpiu: Fix disabling timeouts

4.9-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(): ... [

[PATCH 4.9 087/111] parport: sunbpp: fix error return code

4.9-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.

[PATCH 4.9 085/111] mmc: sdhci: do not try to use 3.3V signaling if not supported

4.9-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

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