Re: [PATCH] ARM: omap2: set CONFIG_LIRC=y in defconfig

* Arnd Bergmann [180226 20:42]: > The CONFIG_LIRC symbol has changed from 'tristate' to 'bool, so we now > get a warning for omap2plus_defconfig: > > arch/arm/configs/omap2plus_defconfig:322:warning: symbol value 'm' invalid > for LIRC > > This changes the file to mark the

Re: [PATCH] ARM: omap2: set CONFIG_LIRC=y in defconfig

* Arnd Bergmann [180226 20:42]: > The CONFIG_LIRC symbol has changed from 'tristate' to 'bool, so we now > get a warning for omap2plus_defconfig: > > arch/arm/configs/omap2plus_defconfig:322:warning: symbol value 'm' invalid > for LIRC > > This changes the file to mark the symbol as built-in

Re: [LKP] [lkp-robot] [mm, mlock, vmscan] 9c4e6b1a70: stress-ng.hdd.ops_per_sec -7.9% regression

On Sun, Feb 25, 2018 at 8:56 PM, Ye Xiaolong wrote: > On 02/26, Ye Xiaolong wrote: >>Hi, Shakeel >> >>On 02/25, Shakeel Butt wrote: >>>On Sun, Feb 25, 2018 at 6:44 AM, kernel test robot >>> wrote: Greeting, FYI, we noticed a -7.9%

Re: [LKP] [lkp-robot] [mm, mlock, vmscan] 9c4e6b1a70: stress-ng.hdd.ops_per_sec -7.9% regression

On Sun, Feb 25, 2018 at 8:56 PM, Ye Xiaolong wrote: > On 02/26, Ye Xiaolong wrote: >>Hi, Shakeel >> >>On 02/25, Shakeel Butt wrote: >>>On Sun, Feb 25, 2018 at 6:44 AM, kernel test robot >>> wrote: Greeting, FYI, we noticed a -7.9% regression of stress-ng.hdd.ops_per_sec due to

Re: [RESEND][PATCH v4 1/3] i2c: piix4: Fix port selection for AMD Family 16h Model 30h

Hi Tobin On 26/02/18 18:58, Tobin C. Harding wrote: > On Mon, Feb 26, 2018 at 10:28:43AM +1000, Andrew Cooks wrote: >> Family 16h Model 30h SMBus controller needs the same port selection fix >> as described and fixed in commit 0fe16195f891 ("i2c: piix4: Fix SMBus port >> selection for AMD Family

Re: [RESEND][PATCH v4 1/3] i2c: piix4: Fix port selection for AMD Family 16h Model 30h

Hi Tobin On 26/02/18 18:58, Tobin C. Harding wrote: > On Mon, Feb 26, 2018 at 10:28:43AM +1000, Andrew Cooks wrote: >> Family 16h Model 30h SMBus controller needs the same port selection fix >> as described and fixed in commit 0fe16195f891 ("i2c: piix4: Fix SMBus port >> selection for AMD Family

[PATCH 2/2] proc: test /proc/self/syscall

Read from /proc/self/syscall should yield read system call and correct args in the output as current is reading /proc/self/syscall. Signed-off-by: Alexey Dobriyan --- tools/testing/selftests/proc/.gitignore |3 + tools/testing/selftests/proc/Makefile

[PATCH 2/2] proc: test /proc/self/syscall

Read from /proc/self/syscall should yield read system call and correct args in the output as current is reading /proc/self/syscall. Signed-off-by: Alexey Dobriyan --- tools/testing/selftests/proc/.gitignore |3 + tools/testing/selftests/proc/Makefile|1

[PATCH 1/2] proc: test /proc/self/wchan

This patch starts testing /proc. Many more tests to come (I promise). Read from /proc/self/wchan should always return "0" as current is in TASK_RUNNING state while reading /proc/self/wchan. Signed-off-by: Alexey Dobriyan --- tools/testing/selftests/Makefile

[PATCH 1/2] proc: test /proc/self/wchan

This patch starts testing /proc. Many more tests to come (I promise). Read from /proc/self/wchan should always return "0" as current is in TASK_RUNNING state while reading /proc/self/wchan. Signed-off-by: Alexey Dobriyan --- tools/testing/selftests/Makefile |1 +

Re: [PATCH 4.14 00/54] 4.14.23-stable review

On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote: > Tony L/Greg > > On 02/26/2018 02:21 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.23 release. > > There are 54 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH 4.14 00/54] 4.14.23-stable review

On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote: > Tony L/Greg > > On 02/26/2018 02:21 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.23 release. > > There are 54 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH v2 0/3] Support qcom pinctrl protected pins

On 02/23/2018 10:54 AM, Bjorn Andersson wrote: I haven't found the time to review the reuse of the irq valid mask or the effort needed to replace this, other than that I think the series looks good. So is that an ACK? -- Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm

Re: [PATCH v2 0/3] Support qcom pinctrl protected pins

On 02/23/2018 10:54 AM, Bjorn Andersson wrote: I haven't found the time to review the reuse of the irq valid mask or the effort needed to replace this, other than that I think the series looks good. So is that an ACK? -- Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm

[PATCH v4] rtc: ac100: Fix ac100 determine rate bug

This patch fixes a bug, that prevents the Allwinner A83T and the A80 from a successful boot. The bug is there since v4.16-rc1 and appeared after the clk branch was merged. You can find the shortend trace below: Unable to handle kernel NULL pointer dereference at virtual address pgd =

[PATCH v4] rtc: ac100: Fix ac100 determine rate bug

This patch fixes a bug, that prevents the Allwinner A83T and the A80 from a successful boot. The bug is there since v4.16-rc1 and appeared after the clk branch was merged. You can find the shortend trace below: Unable to handle kernel NULL pointer dereference at virtual address pgd =

Re: [PATCH v12 3/3] mm, x86, powerpc: display pkey in smaps only if arch supports pkeys

On 02/21/2018 03:52 PM, Ram Pai wrote: > Currently the architecture specific code is expected to > display the protection keys in smap for a given vma. > This can lead to redundant code and possibly to divergent > formats in which the key gets displayed. > > This patch changes the

Re: [PATCH v12 3/3] mm, x86, powerpc: display pkey in smaps only if arch supports pkeys

On 02/21/2018 03:52 PM, Ram Pai wrote: > Currently the architecture specific code is expected to > display the protection keys in smap for a given vma. > This can lead to redundant code and possibly to divergent > formats in which the key gets displayed. > > This patch changes the

[RFC PATCH] Take mmap_min_addr into account while choosing unmapped address for x86-64.

It prevent situation when vm_unmapped_area chose address between PAGE_SIZE and mmap_min_addr range. In this case mmap will fail with EPERM without a good reason. As test-case of such situation we may hard-code address between PAGE_SIZE and 65536 inside unmapped_area_topdown function.

Re: [PATCH v12 2/3] mm, powerpc, x86: introduce an additional vma bit for powerpc pkey

On 02/21/2018 03:52 PM, Ram Pai wrote: > diff --git a/include/linux/mm.h b/include/linux/mm.h > index ad207ad..d534f46 100644 > --- a/include/linux/mm.h > +++ b/include/linux/mm.h > @@ -231,9 +231,10 @@ extern int overcommit_kbytes_handler(struct ctl_table *, > int, void __user *, > #ifdef

[RFC PATCH] Take mmap_min_addr into account while choosing unmapped address for x86-64.

It prevent situation when vm_unmapped_area chose address between PAGE_SIZE and mmap_min_addr range. In this case mmap will fail with EPERM without a good reason. As test-case of such situation we may hard-code address between PAGE_SIZE and 65536 inside unmapped_area_topdown function.

Re: [PATCH v12 2/3] mm, powerpc, x86: introduce an additional vma bit for powerpc pkey

On 02/21/2018 03:52 PM, Ram Pai wrote: > diff --git a/include/linux/mm.h b/include/linux/mm.h > index ad207ad..d534f46 100644 > --- a/include/linux/mm.h > +++ b/include/linux/mm.h > @@ -231,9 +231,10 @@ extern int overcommit_kbytes_handler(struct ctl_table *, > int, void __user *, > #ifdef

Re: [PATCH v12 1/3] mm, powerpc, x86: define VM_PKEY_BITx bits if CONFIG_ARCH_HAS_PKEYS is enabled

On 02/21/2018 03:52 PM, Ram Pai wrote: > VM_PKEY_BITx are defined only if CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS > is enabled. Powerpc also needs these bits. Hence lets define the > VM_PKEY_BITx bits for any architecture that enables > CONFIG_ARCH_HAS_PKEYS. Your fixed version looks fine to me.

[PATCH 3.16] staging: usbip stub_rx fix static checker warning on unnecessary checks

Upstream commit 10c901209306 ("usbip: stub_rx: fix static checker warning on unnecessary checks") Back-port fix for static checker warning on unnecessary checks smatch warnings: drivers/staging/usbip/stub_rx.c:360 get_pipe() warn: impossible condition '(pdu->u.cmd_submit.transfer_buffer_length >

Re: [PATCH v12 1/3] mm, powerpc, x86: define VM_PKEY_BITx bits if CONFIG_ARCH_HAS_PKEYS is enabled

On 02/21/2018 03:52 PM, Ram Pai wrote: > VM_PKEY_BITx are defined only if CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS > is enabled. Powerpc also needs these bits. Hence lets define the > VM_PKEY_BITx bits for any architecture that enables > CONFIG_ARCH_HAS_PKEYS. Your fixed version looks fine to me.

[PATCH 3.16] staging: usbip stub_rx fix static checker warning on unnecessary checks

Upstream commit 10c901209306 ("usbip: stub_rx: fix static checker warning on unnecessary checks") Back-port fix for static checker warning on unnecessary checks smatch warnings: drivers/staging/usbip/stub_rx.c:360 get_pipe() warn: impossible condition '(pdu->u.cmd_submit.transfer_buffer_length >

[PATCH 3.18 10/13] arm64: Disable unhandled signal log messages by default

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Weiser commit 5ee39a71fd89ab7240c5339d04161c44a8e03269 upstream. aarch64 unhandled signal kernel messages are very verbose, suggesting them to be more of a

[PATCH 3.18 10/13] arm64: Disable unhandled signal log messages by default

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Weiser commit 5ee39a71fd89ab7240c5339d04161c44a8e03269 upstream. aarch64 unhandled signal kernel messages are very verbose, suggesting them to be more of a debugging aid:

[PATCH 3.18 05/13] cfg80211: fix cfg80211_beacon_dup

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit bee92d06157fc39d5d7836a061c7d41289a55797 upstream. gcc-8 warns about some obviously incorrect code: net/mac80211/cfg.c: In function 'cfg80211_beacon_dup':

[PATCH 3.18 05/13] cfg80211: fix cfg80211_beacon_dup

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit bee92d06157fc39d5d7836a061c7d41289a55797 upstream. gcc-8 warns about some obviously incorrect code: net/mac80211/cfg.c: In function 'cfg80211_beacon_dup':

[PATCH 3.18 02/13] PCI: keystone: Fix interrupt-controller-node lookup

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

[PATCH 3.18 02/13] PCI: keystone: Fix interrupt-controller-node lookup

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

[PATCH 3.18 06/13] iio: buffer: check if a buffer has been set up when poll is called

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Windfeldt-Prytz commit 4cd140bda6494543f1c1b0ccceceaa44b676eef6 upstream. If no iio buffer has been set up and poll is called return 0. Without this check

[PATCH 3.18 06/13] iio: buffer: check if a buffer has been set up when poll is called

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Windfeldt-Prytz commit 4cd140bda6494543f1c1b0ccceceaa44b676eef6 upstream. If no iio buffer has been set up and poll is called return 0. Without this check there will be a null pointer

[PATCH 3.18 04/13] scsi: ibmvfc: fix misdefined reserved field in ibmvfc_fcp_rsp_info

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tyrel Datwyler commit c39813652700f3df552b6557530f1e5f782dbe2f upstream. The fcp_rsp_info structure as defined in the FC spec has an initial 3 bytes reserved field.

[PATCH 3.18 04/13] scsi: ibmvfc: fix misdefined reserved field in ibmvfc_fcp_rsp_info

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tyrel Datwyler commit c39813652700f3df552b6557530f1e5f782dbe2f upstream. The fcp_rsp_info structure as defined in the FC spec has an initial 3 bytes reserved field. The ibmvfc driver

[PATCH 3.18 03/13] xtensa: fix high memory/reserved memory collision

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit 6ac5a11dc674bc5016ea716e8082fff61f524dc1 upstream. Xtensa memory initialization code frees high memory pages without checking whether they are in the

[PATCH 3.18 09/13] irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 21ec30c0ef5234fb1039cc7c7737d885bf875a9e upstream. A DMB instruction can be used to ensure the relative order of only memory accesses before

[PATCH 3.18 03/13] xtensa: fix high memory/reserved memory collision

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit 6ac5a11dc674bc5016ea716e8082fff61f524dc1 upstream. Xtensa memory initialization code frees high memory pages without checking whether they are in the reserved memory

[PATCH 3.18 09/13] irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 21ec30c0ef5234fb1039cc7c7737d885bf875a9e upstream. A DMB instruction can be used to ensure the relative order of only memory accesses before and after the barrier.

[PATCH 3.18 13/13] ASN.1: fix out-of-bounds read when parsing indefinite length item

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit e0058f3a874ebb48b25be7ff79bc3b4e59929f90 upstream. In asn1_ber_decoder(), indefinitely-sized ASN.1 items were being passed to the action functions

[PATCH 3.18 13/13] ASN.1: fix out-of-bounds read when parsing indefinite length item

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit e0058f3a874ebb48b25be7ff79bc3b4e59929f90 upstream. In asn1_ber_decoder(), indefinitely-sized ASN.1 items were being passed to the action functions before their lengths

[PATCH 4.4 01/22] netfilter: drop outermost socket lock in getsockopt()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni commit 01ea306f2ac2baff98d472da719193e738759d93 upstream. The Syzbot reported a possible deadlock in the netfilter area caused by rtnl lock, xt lock and socket

[PATCH 3.18 07/13] iio: adis_lib: Initialize trigger before requesting interrupt

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen commit f027e0b3a774e10302207e91d304bbf99e3a8b36 upstream. The adis_probe_trigger() creates a new IIO trigger and requests an interrupt associated with the

[PATCH 4.4 01/22] netfilter: drop outermost socket lock in getsockopt()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni commit 01ea306f2ac2baff98d472da719193e738759d93 upstream. The Syzbot reported a possible deadlock in the netfilter area caused by rtnl lock, xt lock and socket lock being acquired

[PATCH 3.18 07/13] iio: adis_lib: Initialize trigger before requesting interrupt

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen commit f027e0b3a774e10302207e91d304bbf99e3a8b36 upstream. The adis_probe_trigger() creates a new IIO trigger and requests an interrupt associated with the trigger. The

[PATCH 4.4 11/22] x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 85c615eb5bc5fab6c7190d146bc59fac289e upstream. GCC-8 shows a warning for the x86 oprofile code that copies per-CPU data from CPU 0 to all other CPUs,

[PATCH 4.4 11/22] x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 85c615eb5bc5fab6c7190d146bc59fac289e upstream. GCC-8 shows a warning for the x86 oprofile code that copies per-CPU data from CPU 0 to all other CPUs, which when

[PATCH 4.4 12/22] irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 21ec30c0ef5234fb1039cc7c7737d885bf875a9e upstream. A DMB instruction can be used to ensure the relative order of only memory accesses before

[PATCH 4.4 12/22] irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 21ec30c0ef5234fb1039cc7c7737d885bf875a9e upstream. A DMB instruction can be used to ensure the relative order of only memory accesses before and after the barrier.

[PATCH 4.4 13/22] usb: ohci: Proper handling of ed_rm_list to handle race condition between usb_kill_urb() and finish_unlinks()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: AMAN DEEP commit 46408ea558df13b110e0866b99624384a33bdeba upstream. There is a race condition between finish_unlinks->finish_urb() function and usb_kill_urb() in ohci

[PATCH 4.4 13/22] usb: ohci: Proper handling of ed_rm_list to handle race condition between usb_kill_urb() and finish_unlinks()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: AMAN DEEP commit 46408ea558df13b110e0866b99624384a33bdeba upstream. There is a race condition between finish_unlinks->finish_urb() function and usb_kill_urb() in ohci controller case. The

[PATCH 4.4 14/22] arm64: Disable unhandled signal log messages by default

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Weiser commit 5ee39a71fd89ab7240c5339d04161c44a8e03269 upstream. aarch64 unhandled signal kernel messages are very verbose, suggesting them to be more of a

[PATCH 4.4 14/22] arm64: Disable unhandled signal log messages by default

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Weiser commit 5ee39a71fd89ab7240c5339d04161c44a8e03269 upstream. aarch64 unhandled signal kernel messages are very verbose, suggesting them to be more of a debugging aid: sigsegv[33]:

[PATCH 4.4 17/22] usb: dwc3: gadget: Set maxpacket size for ep0 IN

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thinh Nguyen commit 6180026341e852a250e1f97ebdcf71684a3c81b9 upstream. There are 2 control endpoint structures for DWC3. However, the driver only updates the OUT

[PATCH 4.4 17/22] usb: dwc3: gadget: Set maxpacket size for ep0 IN

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thinh Nguyen commit 6180026341e852a250e1f97ebdcf71684a3c81b9 upstream. There are 2 control endpoint structures for DWC3. However, the driver only updates the OUT direction control endpoint

[PATCH 4.9 01/39] netfilter: drop outermost socket lock in getsockopt()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni commit 01ea306f2ac2baff98d472da719193e738759d93 upstream. The Syzbot reported a possible deadlock in the netfilter area caused by rtnl lock, xt lock and socket

[PATCH 4.9 01/39] netfilter: drop outermost socket lock in getsockopt()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni commit 01ea306f2ac2baff98d472da719193e738759d93 upstream. The Syzbot reported a possible deadlock in the netfilter area caused by rtnl lock, xt lock and socket lock being acquired

[PATCH 4.4 16/22] drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit 06998a756a3865817b87a129a7e5d5bb66dc1ec3 upstream. Similar to commit e10aec652f31 ("drm/edid: Add 6 bpc quirk for display AEO model 0."), the

[PATCH 4.4 16/22] drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit 06998a756a3865817b87a129a7e5d5bb66dc1ec3 upstream. Similar to commit e10aec652f31 ("drm/edid: Add 6 bpc quirk for display AEO model 0."), the EDID reports "DFP 1.x

Re: [PATCH 3/4] i2c: xlp9xx: report SMBus block read functionality

On Thu, Jan 18, 2018 at 05:39:23AM +, George Cherian wrote: > From: Dmitry Bazhenov > > Report SMBus block read functionality which is actually supported. > > Signed-off-by: Dmitry Bazhenov Applied to for-next but squashed it with

Re: [PATCH 3/4] i2c: xlp9xx: report SMBus block read functionality

On Thu, Jan 18, 2018 at 05:39:23AM +, George Cherian wrote: > From: Dmitry Bazhenov > > Report SMBus block read functionality which is actually supported. > > Signed-off-by: Dmitry Bazhenov Applied to for-next but squashed it with patch 2 because I'd think you also want that fix before

[PATCH 4.9 11/39] irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 21ec30c0ef5234fb1039cc7c7737d885bf875a9e upstream. A DMB instruction can be used to ensure the relative order of only memory accesses before

[PATCH 4.9 11/39] irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 21ec30c0ef5234fb1039cc7c7737d885bf875a9e upstream. A DMB instruction can be used to ensure the relative order of only memory accesses before and after the barrier.

[PATCH 4.9 13/39] ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and io_watchdog_func()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shigeru Yoshida commit b2685bdacdaab065c172b97b55ab46c6be77a037 upstream. Running io_watchdog_func() while ohci_urb_enqueue() is running can cause a race

[PATCH 4.9 14/39] usb: ohci: Proper handling of ed_rm_list to handle race condition between usb_kill_urb() and finish_unlinks()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: AMAN DEEP commit 46408ea558df13b110e0866b99624384a33bdeba upstream. There is a race condition between finish_unlinks->finish_urb() function and usb_kill_urb() in ohci

[PATCH 4.9 13/39] ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and io_watchdog_func()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shigeru Yoshida commit b2685bdacdaab065c172b97b55ab46c6be77a037 upstream. Running io_watchdog_func() while ohci_urb_enqueue() is running can cause a race condition where ohci->prev_frame_no is

[PATCH 4.9 14/39] usb: ohci: Proper handling of ed_rm_list to handle race condition between usb_kill_urb() and finish_unlinks()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: AMAN DEEP commit 46408ea558df13b110e0866b99624384a33bdeba upstream. There is a race condition between finish_unlinks->finish_urb() function and usb_kill_urb() in ohci controller case. The

[PATCH 4.9 17/39] drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit 06998a756a3865817b87a129a7e5d5bb66dc1ec3 upstream. Similar to commit e10aec652f31 ("drm/edid: Add 6 bpc quirk for display AEO model 0."), the

[PATCH 4.9 15/39] arm64: Disable unhandled signal log messages by default

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Weiser commit 5ee39a71fd89ab7240c5339d04161c44a8e03269 upstream. aarch64 unhandled signal kernel messages are very verbose, suggesting them to be more of a

[PATCH 4.9 17/39] drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit 06998a756a3865817b87a129a7e5d5bb66dc1ec3 upstream. Similar to commit e10aec652f31 ("drm/edid: Add 6 bpc quirk for display AEO model 0."), the EDID reports "DFP 1.x

[PATCH 4.9 15/39] arm64: Disable unhandled signal log messages by default

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Weiser commit 5ee39a71fd89ab7240c5339d04161c44a8e03269 upstream. aarch64 unhandled signal kernel messages are very verbose, suggesting them to be more of a debugging aid: sigsegv[33]:

[PATCH 4.9 19/39] usb: ldusb: add PIDs for new CASSY devices supported by this driver

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Karsten Koop commit 52ad2bd8918158266fc88a05f95429b56b6a33c5 upstream. This patch adds support for new CASSY devices to the ldusb driver. The PIDs are also added to the

[PATCH 4.9 19/39] usb: ldusb: add PIDs for new CASSY devices supported by this driver

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Karsten Koop commit 52ad2bd8918158266fc88a05f95429b56b6a33c5 upstream. This patch adds support for new CASSY devices to the ldusb driver. The PIDs are also added to the ignore list in

[PATCH 4.9 16/39] Add delay-init quirk for Corsair K70 RGB keyboards

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Stocker commit 7a1646d922577b5b48c0d222e03831141664bb59 upstream. Following on from this patch: https://lkml.org/lkml/2017/11/3/516, Corsair K70 RGB keyboards

[PATCH 4.9 16/39] Add delay-init quirk for Corsair K70 RGB keyboards

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Stocker commit 7a1646d922577b5b48c0d222e03831141664bb59 upstream. Following on from this patch: https://lkml.org/lkml/2017/11/3/516, Corsair K70 RGB keyboards also require the DELAY_INIT

[PATCH 4.9 21/39] usb: gadget: f_fs: Process all descriptors during bind

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Pham commit 6cf439e0d37463e42784271179c8a308fd7493c6 upstream. During _ffs_func_bind(), the received descriptors are evaluated to prepare for binding with the gadget

[PATCH 4.9 21/39] usb: gadget: f_fs: Process all descriptors during bind

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Pham commit 6cf439e0d37463e42784271179c8a308fd7493c6 upstream. During _ffs_func_bind(), the received descriptors are evaluated to prepare for binding with the gadget in order to allocate

[PATCH 4.9 27/39] binder: add missing binder_unlock()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers When commit 4be5a2810489 ("binder: check for binder_thread allocation failure in binder_poll()") was applied to 4.4-stable and 4.9-stable it was forgotten to

[PATCH 4.9 27/39] binder: add missing binder_unlock()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers When commit 4be5a2810489 ("binder: check for binder_thread allocation failure in binder_poll()") was applied to 4.4-stable and 4.9-stable it was forgotten to release the global

[PATCH 4.9 25/39] drm/amdgpu: Avoid leaking PM domain on driver unbind (v2)

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 458d876eb869d5a88b53074c6c271b8b9adc0f07 upstream. We only support vga_switcheroo and runtime pm on PX/HG systems so forcing runpm to 1 doesn't

[PATCH 4.9 25/39] drm/amdgpu: Avoid leaking PM domain on driver unbind (v2)

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 458d876eb869d5a88b53074c6c271b8b9adc0f07 upstream. We only support vga_switcheroo and runtime pm on PX/HG systems so forcing runpm to 1 doesn't do anything useful anyway.

[PATCH 4.9 26/39] drm/amdgpu: add new device to use atpx quirk

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit 6e59de2048eb375a9bfcd39461ef841cd2a78962 upstream. The affected system (0x0813) is pretty similar to another one (0x0812), it also needs to

[PATCH 4.9 26/39] drm/amdgpu: add new device to use atpx quirk

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit 6e59de2048eb375a9bfcd39461ef841cd2a78962 upstream. The affected system (0x0813) is pretty similar to another one (0x0812), it also needs to use ATPX power control.

[PATCH 4.9 29/39] mm: avoid spurious bad pmd warning messages

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ross Zwisler commit d0f0931de936a0a468d7e59284d39581c16d3a73 upstream. When the pmd_devmap() checks were added by 5c7fb56e5e3f ("mm, dax: dax-pmd vs thp-pmd vs

[PATCH 4.9 29/39] mm: avoid spurious bad pmd warning messages

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ross Zwisler commit d0f0931de936a0a468d7e59284d39581c16d3a73 upstream. When the pmd_devmap() checks were added by 5c7fb56e5e3f ("mm, dax: dax-pmd vs thp-pmd vs hugetlbfs-pmd") to add better

[PATCH 4.9 30/39] fs/dax.c: fix inefficiency in dax_writeback_mapping_range()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 1eb643d02b21412e603b42cdd96010a2ac31c05f upstream. dax_writeback_mapping_range() fails to update iteration index when searching radix tree for entries needing

[PATCH 4.9 30/39] fs/dax.c: fix inefficiency in dax_writeback_mapping_range()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 1eb643d02b21412e603b42cdd96010a2ac31c05f upstream. dax_writeback_mapping_range() fails to update iteration index when searching radix tree for entries needing cache flushing.

[PATCH 4.9 03/39] scsi: ibmvfc: fix misdefined reserved field in ibmvfc_fcp_rsp_info

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tyrel Datwyler commit c39813652700f3df552b6557530f1e5f782dbe2f upstream. The fcp_rsp_info structure as defined in the FC spec has an initial 3 bytes reserved field.

[PATCH 4.9 03/39] scsi: ibmvfc: fix misdefined reserved field in ibmvfc_fcp_rsp_info

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tyrel Datwyler commit c39813652700f3df552b6557530f1e5f782dbe2f upstream. The fcp_rsp_info structure as defined in the FC spec has an initial 3 bytes reserved field. The ibmvfc driver

Re: [PATCH 4.14 00/54] 4.14.23-stable review

Tony L/Greg On 02/26/2018 02:21 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.23 release. > There are 54 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. >

Re: [PATCH 4.14 00/54] 4.14.23-stable review

Tony L/Greg On 02/26/2018 02:21 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.23 release. > There are 54 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. >

[PATCH 4.9 31/39] libnvdimm: fix integer overflow static analysis warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 58738c495e15badd2015e19ff41f1f1ed55200bc upstream. Dan reports: The patch 62232e45f4a2: "libnvdimm: control (ioctl) messages for

[PATCH 4.9 31/39] libnvdimm: fix integer overflow static analysis warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 58738c495e15badd2015e19ff41f1f1ed55200bc upstream. Dan reports: The patch 62232e45f4a2: "libnvdimm: control (ioctl) messages for nvdimm_bus and nvdimm devices" from

[PATCH 4.9 32/39] device-dax: implement ->split() to catch invalid munmap attempts

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 9702cffdbf2129516db679e4467db81e1cd287da upstream. Similar to how device-dax enforces that the 'address', 'offset', and 'len' parameters to mmap()

[PATCH 4.9 32/39] device-dax: implement ->split() to catch invalid munmap attempts

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 9702cffdbf2129516db679e4467db81e1cd287da upstream. Similar to how device-dax enforces that the 'address', 'offset', and 'len' parameters to mmap() be aligned to the

[PATCH 4.9 05/39] X.509: fix BUG_ON() when hash algorithm is unsupported

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 437499eea4291ae9621e8763a41df027c110a1ef upstream. The X.509 parser mishandles the case where the certificate's signature's hash algorithm is not

[PATCH 4.9 05/39] X.509: fix BUG_ON() when hash algorithm is unsupported

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 437499eea4291ae9621e8763a41df027c110a1ef upstream. The X.509 parser mishandles the case where the certificate's signature's hash algorithm is not available in the crypto

[PATCH 4.9 33/39] mm: introduce get_user_pages_longterm

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 2bb6d2837083de722bfdc369cb0d76ce188dd9b4 upstream. Patch series "introduce get_user_pages_longterm()", v2. Here is a new get_user_pages api for

[PATCH 4.9 34/39] v4l2: disable filesystem-dax mapping support

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit b70131de648c2b997d22f4653934438013f407a1 upstream. V4L2 memory registrations are incompatible with filesystem-dax that needs the ability to revoke

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