[PATCH 4.18 149/235] audit: fix use-after-free in audit_add_watch

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

[PATCH 4.18 148/235] arm64: dts: uniphier: Add missing cooling device properties for CPUs

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

[PATCH 4.18 152/235] bpf: fix rcu annotations in compute_effective_progs()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Roman Gushchin [ Upstream commit 3960f4fd6585608e8cc285d9665821985494e147 ] The progs local variable in compute_effective_progs() is marked as __rcu, which is not correct. This is a local

[PATCH 4.18 154/235] Bluetooth: Use lock_sock_nested in bt_accept_enqueue

4.18-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.18 151/235] vfs: fix freeze protection in mnt_want_write_file() for overlayfs

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

[PATCH 4.18 153/235] spi: dw: fix possible race condition

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexandre Belloni [ Upstream commit 66b19d762378785d1568b5650935205edfeb0503 ] It is possible to get an interrupt as soon as it is requested. dw_spi_irq does

[PATCH 4.18 146/235] binfmt_elf: Respect error return from `regset->active

4.18-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.18 145/235] mmc: meson-mx-sdio: fix OF child-node lookup

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit c483a5cc9d09f4ceaa9abb106f863cc89cb643d9 upstream. Use the new of_get_compatible_child() helper to lookup the slot child node instead of using of_find_compatible_node(),

Re: [PATCH v6 0/3] Harden spectrev2 userspace-userspace protection

On Mon, 24 Sep 2018, Jiri Kosina wrote: > On Sat, 22 Sep 2018, Thomas Gleixner wrote: > > > Lunch and coffee indeed made brain work better. The simple solution was way > > too obvious. > > Ah, cool, I like it a lot. > > Do you want me to fold this into v7, or are you on it already? Please do

Re: [PATCH net-next] tcp: expose sk_state in tcp_retransmit_skb tracepoint

On Mon, Sep 24, 2018 at 5:42 AM, Eric Dumazet wrote: > > > On 09/23/2018 12:49 PM, Yafang Shao wrote: >> With sk_state, we can know whether this connection is in SYN_SENT state >> or ESTBLISHED state. >> The reason to distinguish between these two scenario is that the >> retransmission in

[PATCH 4.18 142/235] NFSv4: Fix a tracepoint Oops in initiate_file_draining()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 2a534a7473bf4e7f1c12805113f80c795fc8e89a upstream. Now that the value of 'ino' can be NULL or an ERR_PTR(), we need to change the test in the tracepoint. Fixes:

[PATCH 4.18 158/235] PM / devfreq: use put_device() instead of kfree()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Arvind Yadav [ Upstream commit 2d803dc8f7a5f622ac47c3b650834ada3a2659b9 ] Never directly free @dev after calling device_register() or device_unregister(), even if device_register() returned

[PATCH 4.9 074/111] audit: fix use-after-free in audit_add_watch

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

[PATCH 4.14 117/173] MIPS: loongson64: cs5536: Fix PCI_OHCI_INT_REG reads

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paul Burton [ Upstream commit cd87668d601f622e0ebcfea4f78d116d5f572f4d ] The PCI_OHCI_INT_REG case in pci_ohci_read_reg() contains the following if statement: if ((lo & 0x0f00) ==

Re: [PATCH 5/6] fsmount: do not use legacy MS_ flags

On Mon, Sep 24, 2018 at 01:37:45PM +0100, David Howells wrote: > Christian Brauner wrote: > > > I have thought a little more about splitting up the mount flags into > > sensible sets. I think the following four sets make sense: > > > > enum { > > MOUNT_ATTR_PROPAGATION = 1, > >

RE: [PATCH v7 2/7] edac: synps: Add platform specific structures for ddrc controller

Hi Boris, Thanks for the review. > -Original Message- > From: Borislav Petkov [mailto:b...@alien8.de] > Sent: Friday, September 21, 2018 2:46 PM > To: Manish Narani > Cc: robh...@kernel.org; mark.rutl...@arm.com; mche...@kernel.org; > Michal Simek ; leoyang...@nxp.com; >

[PATCH 14/14] dt-bindings: serial: lantiq: Add optional properties for CCF

Clocks and clock-names are updated in device tree binding. Reviewed-by: Rob Herring Signed-off-by: Songjun Wu --- Documentation/devicetree/bindings/serial/lantiq_asc.txt | 15 +++ 1 file changed, 15 insertions(+) diff --git

[PATCH 13/14] serial: lantiq: Change init_lqasc to static declaration

init_lqasc() is only used internally, change to static declaration. Signed-off-by: Songjun Wu --- drivers/tty/serial/lantiq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/serial/lantiq.c b/drivers/tty/serial/lantiq.c index ba0c70b16bda..e052b69ceb98 100644

[PATCH 03/14] serial: lantiq: Get serial id from dts

Get serial id from dts, also keep backward compatible when dts is not updated. Signed-off-by: Songjun Wu --- drivers/tty/serial/lantiq.c | 19 +++ 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/drivers/tty/serial/lantiq.c b/drivers/tty/serial/lantiq.c index

[PATCH v4] block/loop: Serialize ioctl operations.

On 2018/09/24 7:03, Ming Lei wrote: > On Sat, Sep 22, 2018 at 09:39:02PM +0900, Tetsuo Handa wrote: >> Hello, Ming Lei. >> >> I'd like to hear your comment on this patch regarding the ordering of >> stopping kernel thread. >> >> > In order to enforce this strategy, this patch inversed >> >

RE: [PATCH v7 4/7] edac: synopsys: Add macro defines for ZynqMP DDRC

Hi Boris, Thanks for the review. > -Original Message- > From: Borislav Petkov [mailto:b...@alien8.de] > Sent: Monday, September 24, 2018 2:52 PM > To: Manish Narani > Cc: robh...@kernel.org; mark.rutl...@arm.com; mche...@kernel.org; > Michal Simek ; leoyang...@nxp.com; >

Re: [RFC/PATCH 2/5] device property: introduce notion of subnodes for legacy boards

Hi Linus, On Fri, Sep 21, 2018 at 08:36:53AM -0700, Linus Walleij wrote: > On Thu, Sep 20, 2018 at 6:53 AM Heikki Krogerus > wrote: > > > The child nodes will change the purpose of the build-in property > > support. Originally the goal was just to support adding of build-in > > device

[PATCH 08/14] serial: lantiq: Replace clk_enable/clk_disable with clk generic API

The clk driver has introduced new clock APIs that replace the existing clk_enable and clk_disable. - clk_enable() APIs is replaced with clk_prepare_enable() - clk_disable() API is replaced with clk_disable_unprepare() Signed-off-by: Songjun Wu --- drivers/tty/serial/lantiq.c | 6 +++--- 1 file

Re: [PATCH v10 10/26] KVM: s390: interfaces to clear CRYCB masks

On Wed, 12 Sep 2018 15:43:00 -0400 Tony Krowiak wrote: > From: Tony Krowiak > > Introduces two new KVM interface to clear the APM, AQM and ADM masks in > the guest's CRYCB. The VCPUs are taken out of SIE to ensure the VCPUs do > not get out of sync. Hm, that patch description does not quite

[PATCH 4.4 15/70] perf powerpc: Fix callchain ip filtering when return address is in a register

4.4-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.4 14/70] fbdev/via: fix defined but not used warning

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

[PATCH 4.4 13/70] video: goldfishfb: fix memory leak on driver remove

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

[PATCH 4.4 19/70] powerpc/powernv: opal_put_chars partial write fix

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin [ Upstream commit bd90284cc6c1c9e8e48c8eadd0c79574fcce0b81 ] The intention here is to consume and discard the remaining buffer upon error. This works if there has not been a

[PATCH 4.4 17/70] ARM: exynos: Clear global variable on init error path

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski [ Upstream commit cd4806911cee3901bc2b5eb95603cf1958720b57 ] For most of Exynos SoCs, Power Management Unit (PMU) address space is mapped into global variable

[PATCH 4.4 12/70] fbdev: omapfb: off by one in omapfb_register_client()

4.4-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.4 23/70] arm64: dts: qcom: db410c: Fix Bluetooth LED trigger

4.4-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.4 28/70] xen-netfront: fix warn message as irq device name has /

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

[PATCH 4.4 18/70] perf powerpc: Fix callchain ip filtering

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sandipan Das [ Upstream commit c715fcfda5a08edabaa15508742be926b7ee51db ] For powerpc64, redundant entries in the callchain are filtered out by determining the state of the return address and

[PATCH 4.4 02/70] ALSA: msnd: Fix the default sample sizes

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

[PATCH 4.4 25/70] s390/qeth: reset layer2 attribute on layer switch

4.4-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.4 22/70] xen-netfront: fix queue name setting

4.4-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:

[PATCH 4.4 20/70] MIPS: jz4740: Bump zload address

4.4-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.4 21/70] mac80211: restrict delayed tailroom needed decrement

4.4-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 4.4 24/70] s390/qeth: fix race in used-buffer accounting

4.4-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.4 26/70] platform/x86: toshiba_acpi: Fix defined but not used build warnings

4.4-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 4.4 10/70] media: videobuf2-core: check for q->error in vb2_core_qbuf()

4.4-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.4 11/70] mtd/maps: fix solutionengine.c printk format warnings

4.4-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.4 01/70] iommu/arm-smmu-v3: sync the OVACKFLG to PRIQ consumer register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miao Zhong [ Upstream commit 0d535967ac658966c6ade8f82b5799092f7d5441 ] When PRI queue occurs overflow, driver should update the OVACKFLG to the PRIQ consumer register, otherwise subsequent

[PATCH 4.4 16/70] fbdev: Distinguish between interlaced and progressive modes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Fredrik Noring [ Upstream commit 1ba0a59cea41ea05fda92daaf2a2958a2246b9cf ] I discovered the problem when developing a frame buffer driver for the PlayStation 2 (not yet merged), using the

[PATCH 4.4 03/70] ALSA: usb-audio: Fix multiple definitions in AU0828_DEVICE() macro

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai [ Upstream commit bd1cd0eb2ce9141100628d476ead4de485501b29 ] AU0828_DEVICE() macro in quirks-table.h uses USB_DEVICE_VENDOR_SPEC() for expanding idVendor and idProduct fields.

[PATCH 4.4 27/70] crypto: sharah - Unregister correct algorithms for SAHARA 3

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

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

On Mon, 2018-09-24 at 13:00 +0100, David Howells wrote: > Lubomir Rintel wrote: > > > 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

Re: [PATCH v4] remoteproc: qcom: Introduce Non-PAS ADSP PIL driver

Hi Rohit, Thanks for the quick turnaround, the patches look fine. Reviewed-by: Sibi Sankar Tested-by: Sibi Sankar On 2018-09-24 16:37, Rohit kumar wrote: This adds Non PAS ADSP PIL driver for Qualcomm Technologies Inc SoCs. Added initial support for SDM845 with ADSP bootup and shutdown

[PATCH 4.9 106/111] Partial revert "e1000e: Avoid receiver overrun interrupt bursts"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Poirier commit 1f0ea19722ef9dfa229a9540f70b8d1c34a98a6a upstream. This partially reverts commit 4aea7a5c5e940c1723add439f4088844cd26196d. We keep the fix for the first part of the

[PATCH 4.9 108/111] e1000e: Avoid missed interrupts following ICR read

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Poirier commit 116f4a640b3197401bc93b8adc6c35040308ceff upstream. The 82574 specification update errata 12 states that interrupts may be missed if ICR is read while INT_ASSERTED is

[PATCH 4.9 104/111] MIPS: VDSO: Match data page cache colouring when D$ aliases

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paul Burton commit 0f02cfbc3d9e413d450d8d0fd660077c23f67eff upstream. When a system suffers from dcache aliasing a user program may observe stale VDSO data from an aliased cache line. Notably

[PATCH 4.9 107/111] e1000e: Fix queue interrupt re-raising in Other interrupt

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Poirier commit 361a954e6a7215de11a6179ad9bdc07d7e394b04 upstream. Restores the ICS write for Rx/Tx queue interrupts which was present before commit 16ecba59bc33 ("e1000e: Do not read

[PATCH 4.9 109/111] Revert "e1000e: Separate signaling for link check/link up"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Poirier commit 3016e0a0c91246e55418825ba9aae271be267522 upstream. This reverts commit 19110cfbb34d4af0cdfe14cd243f3b09dc95b013. This reverts commit

Re: [PATCH 0/3] fuse: Solve request_find() bottleneck

2 weeks passed, so ping. Miklos, any reaction on this? Thanks, Kirill On 11.09.2018 13:11, Kirill Tkhai wrote: > Hi, > > We noticed the performance bottle neck in FUSE running our > Virtuozzo storage over rdma. On some types of workload > we observe 20% of time spent in request_find() in

[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

[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

[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

[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

[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

[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

[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*

[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

[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

[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

[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

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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

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

[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

[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

[PATCH 4.18 066/235] staging: bcm2835-camera: fix timeout handling in wait_for_completion_timeout

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

[PATCH 4.18 064/235] powerpc/powernv: opal_put_chars partial write fix

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin [ Upstream commit bd90284cc6c1c9e8e48c8eadd0c79574fcce0b81 ] The intention here is to consume and discard the remaining buffer upon error. This works if there has not been a

[PATCH 4.18 068/235] ASoC: rt5514: Fix the issue of the delay volume applied

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

[PATCH 4.18 067/235] staging: bcm2835-camera: handle wait_for_completion_timeout return properly

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

[PATCH 4.18 065/235] perf script: Show correct offsets for DWARF-based unwinding

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sandipan Das [ Upstream commit 2a9d5050dc84fa2060f08a52f632976923e0fa7e ] When perf/data is recorded with the dwarf call-graph option, the callchain shown by 'perf script' still shows the

[PATCH 4.18 078/235] xen-netfront: fix queue name setting

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

[PATCH 4.18 074/235] reset: imx7: Fix always writing bits as 0

4.18-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.18 075/235] efi/arm: preserve early mapping of UEFI memory map longer for BGRT

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

[PATCH 4.18 043/235] mtd/maps: fix solutionengine.c printk format warnings

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

[PATCH 4.18 077/235] nfp: avoid buffer leak when FW communication fails

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

[PATCH 4.18 046/235] gfs2: Dont reject a supposedly full bitmap if we have blocks reserved

4.18-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.18 076/235] ALSA: usb-audio: Generic DSD detection for Thesycon-based implementations

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Yue Wang [ Upstream commit 1ea0358ecb848058b35b6da13d7f4c08610a73a8 ] Thesycon provides solutions to XMOS chips, and has its own device vendor id. In this patch, we use generic method to

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