[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 cases where a driver

[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 dma access to a mapping

[PATCH 4.9 08/39] iio: buffer: check if a buffer has been set up when poll is called

4.9-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 4.9 36/39] libnvdimm, dax: fix 1GB-aligned namespaces vs physical misalignment

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 41fce90f26333c4fa82e8e43b9ace86c4e8a0120 upstream. The following namespace configuration attempt: # ndctl create-namespace -e namespace0.0 -m

[PATCH 4.9 08/39] iio: buffer: check if a buffer has been set up when poll is called

4.9-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 4.9 36/39] libnvdimm, dax: fix 1GB-aligned namespaces vs physical misalignment

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 41fce90f26333c4fa82e8e43b9ace86c4e8a0120 upstream. The following namespace configuration attempt: # ndctl create-namespace -e namespace0.0 -m devdax -a 1G -f

[PATCH 4.9 07/39] RDMA/uverbs: Protect from command mask overflow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 3f802b162dbf4a558ff98986449eddc717826209 upstream. The command number is not bounds checked against the command mask before it is shifted, resulting

[PATCH 4.9 07/39] RDMA/uverbs: Protect from command mask overflow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 3f802b162dbf4a558ff98986449eddc717826209 upstream. The command number is not bounds checked against the command mask before it is shifted, resulting in an ubsan hit.

[PATCH 4.9 39/39] x86/entry/64: Clear extra registers beyond syscall arguments, to reduce speculation attack surface

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 8e1eb3fa009aa7c0b944b3c8b26b07de0efb3200 upstream. At entry userspace may have (maliciously) populated the extra registers outside the syscall

Re: [PATCH] KVM: X86: Allow userspace to define the microcode version

On Mon, Feb 26, 2018 at 08:37:11PM +0100, Borislav Petkov wrote: > On Mon, Feb 26, 2018 at 09:39:12AM -0500, Konrad Rzeszutek Wilk wrote: > > diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c > > index d19e903214b4..87d044ce837f 100644 > > --- a/arch/x86/kernel/cpu/intel.c > >

[PATCH 4.9 39/39] x86/entry/64: Clear extra registers beyond syscall arguments, to reduce speculation attack surface

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 8e1eb3fa009aa7c0b944b3c8b26b07de0efb3200 upstream. At entry userspace may have (maliciously) populated the extra registers outside the syscall calling convention with

Re: [PATCH] KVM: X86: Allow userspace to define the microcode version

On Mon, Feb 26, 2018 at 08:37:11PM +0100, Borislav Petkov wrote: > On Mon, Feb 26, 2018 at 09:39:12AM -0500, Konrad Rzeszutek Wilk wrote: > > diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c > > index d19e903214b4..87d044ce837f 100644 > > --- a/arch/x86/kernel/cpu/intel.c > >

[PATCH 4.9 38/39] mm: fail get_vaddr_frames() for filesystem-dax mappings

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit b7f0554a56f21fb3e636a627450a9add030889be upstream. Until there is a solution to the dma-to-dax vs truncate problem it is not safe to allow V4L2,

Re: [PATCH] PCI: stop crashing in pci_release_resource v2

On Wed, Feb 21, 2018 at 10:07:15AM +0100, Christian König wrote: > Is it entirely possible that the BIOS wasn't able to assign resources to > a device. In this case don't crash in pci_release_resource() when we try > to resize the resource. > > v2: keep printing the info that we try to release

[PATCH 4.9 38/39] mm: fail get_vaddr_frames() for filesystem-dax mappings

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit b7f0554a56f21fb3e636a627450a9add030889be upstream. Until there is a solution to the dma-to-dax vs truncate problem it is not safe to allow V4L2, Exynos, and other frame

Re: [PATCH] PCI: stop crashing in pci_release_resource v2

On Wed, Feb 21, 2018 at 10:07:15AM +0100, Christian König wrote: > Is it entirely possible that the BIOS wasn't able to assign resources to > a device. In this case don't crash in pci_release_resource() when we try > to resize the resource. > > v2: keep printing the info that we try to release

Re: [PATCH v11 2/7] PCI/AER: factor out error reporting from AER

On Mon, Feb 26, 2018 at 11:02:50AM +0530, p...@codeaurora.org wrote: > On 2018-02-24 05:12, Bjorn Helgaas wrote: > > On Fri, Feb 23, 2018 at 01:53:59PM +0530, Oza Pawandeep wrote: > > > * handle_error_source - handle logging error into an event log > > > diff --git a/drivers/pci/pcie/pcie-err.c

Re: [PATCH v11 2/7] PCI/AER: factor out error reporting from AER

On Mon, Feb 26, 2018 at 11:02:50AM +0530, p...@codeaurora.org wrote: > On 2018-02-24 05:12, Bjorn Helgaas wrote: > > On Fri, Feb 23, 2018 at 01:53:59PM +0530, Oza Pawandeep wrote: > > > * handle_error_source - handle logging error into an event log > > > diff --git a/drivers/pci/pcie/pcie-err.c

Re: [PATCH 0/5] x86/boot/compressed/64: Prepare trampoline memory

On Mon, Feb 26, 2018 at 08:32:44PM +0100, Borislav Petkov wrote: > On Mon, Feb 26, 2018 at 09:04:46PM +0300, Kirill A. Shutemov wrote: > > Borislav, could you check which patch breaks boot for you (if any)? > > What is that ontop? tip/master from today or? I made it on top of tip/x86/mm, but

Re: [PATCH 0/5] x86/boot/compressed/64: Prepare trampoline memory

On Mon, Feb 26, 2018 at 08:32:44PM +0100, Borislav Petkov wrote: > On Mon, Feb 26, 2018 at 09:04:46PM +0300, Kirill A. Shutemov wrote: > > Borislav, could you check which patch breaks boot for you (if any)? > > What is that ontop? tip/master from today or? I made it on top of tip/x86/mm, but

[PATCH 4.14 12/54] X.509: fix NULL dereference when restricting key with unsupported_sig

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 4b34968e77ad09628cfb3c4a7daf2adc2cefc6e8 upstream. The asymmetric key type allows an X.509 certificate to be added even if its signature's hash

[PATCH 4.14 12/54] X.509: fix NULL dereference when restricting key with unsupported_sig

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 4b34968e77ad09628cfb3c4a7daf2adc2cefc6e8 upstream. The asymmetric key type allows an X.509 certificate to be added even if its signature's hash algorithm is not available

[PATCH 4.14 13/54] PKCS#7: fix certificate chain verification

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 971b42c038dc83e3327872d294fe7131bab152fc upstream. When pkcs7_verify_sig_chain() is building the certificate chain for a SignerInfo using the

[PATCH 4.14 13/54] PKCS#7: fix certificate chain verification

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 971b42c038dc83e3327872d294fe7131bab152fc upstream. When pkcs7_verify_sig_chain() is building the certificate chain for a SignerInfo using the certificates in the PKCS#7

[PATCH 4.14 14/54] PKCS#7: fix certificate blacklisting

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 29f4a67c17e19314b7d74b8569be935e6c7edf50 upstream. If there is a blacklisted certificate in a SignerInfo's certificate chain, then

[PATCH 4.14 14/54] PKCS#7: fix certificate blacklisting

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 29f4a67c17e19314b7d74b8569be935e6c7edf50 upstream. If there is a blacklisted certificate in a SignerInfo's certificate chain, then pkcs7_verify_sig_chain() sets

[PATCH 4.14 15/54] extcon: int3496: process id-pin first so that we start with the right status

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 0434352d3d2e950cf5e743f6062abd87de22f960 upstream. Some other drivers may be waiting for our extcon to show-up, exiting their probe methods with

[PATCH 4.14 16/54] RDMA/uverbs: Protect from races between lookup and destroy of uobjects

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 6623e3e3cd78020016d3fa42555763178e94ab64 upstream. The race is between lookup_get_idr_uobject and uverbs_idr_remove_uobj -> uverbs_uobject_put. We

[PATCH 4.14 15/54] extcon: int3496: process id-pin first so that we start with the right status

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 0434352d3d2e950cf5e743f6062abd87de22f960 upstream. Some other drivers may be waiting for our extcon to show-up, exiting their probe methods with -EPROBE_DEFER until we

[PATCH 4.14 16/54] RDMA/uverbs: Protect from races between lookup and destroy of uobjects

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 6623e3e3cd78020016d3fa42555763178e94ab64 upstream. The race is between lookup_get_idr_uobject and uverbs_idr_remove_uobj -> uverbs_uobject_put. We deliberately do not

[PATCH 4.14 17/54] RDMA/uverbs: Protect from command mask overflow

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 3f802b162dbf4a558ff98986449eddc717826209 upstream. The command number is not bounds checked against the command mask before it is shifted,

[PATCH 4.14 17/54] RDMA/uverbs: Protect from command mask overflow

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 3f802b162dbf4a558ff98986449eddc717826209 upstream. The command number is not bounds checked against the command mask before it is shifted, resulting in an ubsan hit.

[PATCH 4.14 19/54] RDMA/uverbs: Fix circular locking dependency

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 1ff5325c3ca1843228a86549318bbd3b414b9207 upstream. Avoid circular locking dependency by calling to uobj_alloc_commit() outside of xrcd_tree_mutex

[PATCH 4.14 19/54] RDMA/uverbs: Fix circular locking dependency

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 1ff5325c3ca1843228a86549318bbd3b414b9207 upstream. Avoid circular locking dependency by calling to uobj_alloc_commit() outside of xrcd_tree_mutex lock.

[PATCH 4.14 02/54] arm64: mm: dont write garbage into TTBR1_EL1 register

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel Stable backport commit 173358a49173 ("arm64: kpti: Add ->enable callback to remap swapper using nG mappings") of upstream commit f992b4dfd58b did not

[PATCH 4.14 02/54] arm64: mm: dont write garbage into TTBR1_EL1 register

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel Stable backport commit 173358a49173 ("arm64: kpti: Add ->enable callback to remap swapper using nG mappings") of upstream commit f992b4dfd58b did not survive the backporting

[PATCH 4.14 21/54] iio: adc: stm32: fix stm32h7_adc_enable error handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Fabrice Gasnier commit a3b5655ebdb501a98a45c0d3265dca9f2fe0218a upstream. Error handling in stm32h7_adc_enable routine doesn't unwind enable sequence correctly. ADEN

[PATCH 4.14 21/54] iio: adc: stm32: fix stm32h7_adc_enable error handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Fabrice Gasnier commit a3b5655ebdb501a98a45c0d3265dca9f2fe0218a upstream. Error handling in stm32h7_adc_enable routine doesn't unwind enable sequence correctly. ADEN can only be cleared by

[PATCH 4.14 20/54] RDMA/uverbs: Sanitize user entered port numbers prior to access it

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 5d4c05c3ee36f67ddc107ab5ea0898af01a62cc1 upstream. == BUG: KASAN: use-after-free in

[PATCH 4.14 20/54] RDMA/uverbs: Sanitize user entered port numbers prior to access it

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 5d4c05c3ee36f67ddc107ab5ea0898af01a62cc1 upstream. == BUG: KASAN: use-after-free in

Re: [PATCH v2 2/2] i2c: piix4: Use request_muxed_region

On Mon, Feb 26, 2018 at 12:46:53PM -0800, Guenter Roeck wrote: > Accesses to SB800_PIIX4_SMB_IDX can occur from multiple drivers. > One example for another driver is the sp5100_tco driver. > > Use request_muxed_region() to ensure synchronization. > > Signed-off-by: Guenter Roeck

[PATCH 4.14 23/54] iio: buffer: check if a buffer has been set up when poll is called

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

Re: [PATCH v2 2/2] i2c: piix4: Use request_muxed_region

On Mon, Feb 26, 2018 at 12:46:53PM -0800, Guenter Roeck wrote: > Accesses to SB800_PIIX4_SMB_IDX can occur from multiple drivers. > One example for another driver is the sp5100_tco driver. > > Use request_muxed_region() to ensure synchronization. > > Signed-off-by: Guenter Roeck To understand

[PATCH 4.14 23/54] iio: buffer: check if a buffer has been set up when poll is called

4.14-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 4.14 26/54] x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()

4.14-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.14 26/54] x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()

4.14-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.14 25/54] Kbuild: always define endianess in kconfig.h

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 101110f6271ce956a049250c907bc960030577f8 upstream. Build testing with LTO found a couple of files that get compiled differently depending on whether

[PATCH 4.14 25/54] Kbuild: always define endianess in kconfig.h

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 101110f6271ce956a049250c907bc960030577f8 upstream. Build testing with LTO found a couple of files that get compiled differently depending on whether asm/byteorder.h gets

[PATCH 4.14 28/54] irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()

4.14-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.14 28/54] irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()

4.14-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.14 03/54] kconfig.h: Include compiler types to avoid missed struct attributes

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 28128c61e08eaeced9cc8ec0e6b5d677b5b94690 upstream. The header files for some structures could get included in such a way that struct attributes

[PATCH 4.14 03/54] kconfig.h: Include compiler types to avoid missed struct attributes

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 28128c61e08eaeced9cc8ec0e6b5d677b5b94690 upstream. The header files for some structures could get included in such a way that struct attributes (specifically

[PATCH 4.14 31/54] ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and io_watchdog_func()

4.14-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.14 31/54] ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and io_watchdog_func()

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

[PATCH 4.14 30/54] PCI/cxgb4: Extend T3 PCI quirk to T4+ devices

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Casey Leedom commit 7dcf688d4c78a18ba9538b2bf1b11dc7a43fe9be upstream. We've run into a problem where our device is attached to a Virtual Machine and the use of the new

[PATCH 4.14 30/54] PCI/cxgb4: Extend T3 PCI quirk to T4+ devices

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Casey Leedom commit 7dcf688d4c78a18ba9538b2bf1b11dc7a43fe9be upstream. We've run into a problem where our device is attached to a Virtual Machine and the use of the new pci_set_vpd_size() API

[PATCH 4.14 32/54] usb: ohci: Proper handling of ed_rm_list to handle race condition between usb_kill_urb() and finish_unlinks()

4.14-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.14 32/54] usb: ohci: Proper handling of ed_rm_list to handle race condition between usb_kill_urb() and finish_unlinks()

4.14-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.14 33/54] arm64: Remove unimplemented syscall log message

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Weiser commit 1962682d2b2fbe6cfa995a85c53c069fadda473e upstream. Stop printing a (ratelimited) kernel message for each instance of an unimplemented syscall

[PATCH 4.14 33/54] arm64: Remove unimplemented syscall log message

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Weiser commit 1962682d2b2fbe6cfa995a85c53c069fadda473e upstream. Stop printing a (ratelimited) kernel message for each instance of an unimplemented syscall being called. Userland

[PATCH 4.14 04/54] MIPS: boot: Define __ASSEMBLY__ for its.S build

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 0f9da844d87796ac31b04e81ee95e155e9043132 upstream. The MIPS %.its.S compiler command did not define __ASSEMBLY__, which meant when compiler_types.h was

[PATCH 4.14 04/54] MIPS: boot: Define __ASSEMBLY__ for its.S build

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 0f9da844d87796ac31b04e81ee95e155e9043132 upstream. The MIPS %.its.S compiler command did not define __ASSEMBLY__, which meant when compiler_types.h was added to kconfig.h,

[PATCH 4.14 08/54] cfg80211: fix cfg80211_beacon_dup

4.14-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 4.14 00/54] 4.14.23-stable review

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. Responses should be made by Wed Feb 28 20:21:22 UTC 2018. Anything

[PATCH 4.14 35/54] arm64: cpufeature: Fix CTR_EL0 field definitions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit be68a8aaf925aaf35574260bf820bb09d2f9e07f upstream. Our field definitions for CTR_EL0 suffer from a number of problems: - The IDC and DIC fields are

[PATCH 4.14 08/54] cfg80211: fix cfg80211_beacon_dup

4.14-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 4.14 00/54] 4.14.23-stable review

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. Responses should be made by Wed Feb 28 20:21:22 UTC 2018. Anything

[PATCH 4.14 35/54] arm64: cpufeature: Fix CTR_EL0 field definitions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit be68a8aaf925aaf35574260bf820bb09d2f9e07f upstream. Our field definitions for CTR_EL0 suffer from a number of problems: - The IDC and DIC fields are missing, which causes

[PATCH 4.14 05/54] xtensa: fix high memory/reserved memory collision

4.14-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 4.14 05/54] xtensa: fix high memory/reserved memory collision

4.14-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 4.14 44/54] usb: gadget: f_fs: Use config_ep_by_speed()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jack Pham commit 675272d092e4a5570bace92593776f7348daf4c5 upstream. In commit 2bfa0719ac2a ("usb: gadget: function: f_fs: pass companion descriptor along") there is a

[PATCH 4.14 44/54] usb: gadget: f_fs: Use config_ep_by_speed()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jack Pham commit 675272d092e4a5570bace92593776f7348daf4c5 upstream. In commit 2bfa0719ac2a ("usb: gadget: function: f_fs: pass companion descriptor along") there is a pointer arithmetic bug

[PATCH 4.14 45/54] usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 17aa31f13cad25daa19d3f923323f552e87bc874 upstream. This fixes an issue that a gadget driver (usb_f_fs) is possible to stop rx

[PATCH 4.14 46/54] drm/cirrus: Load lut in crtc_commit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit 745fd50f3b044db6a3922e1718306555613164b0 upstream. In the past the ast driver relied upon the fbdev emulation helpers to call ->load_lut at

[PATCH 4.14 47/54] drm: Handle unexpected holes in color-eviction

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit b8ff1802815913aad52695898cccbc9f77b7e726 upstream. During eviction, the driver may free more than one hole in the drm_mm due to the side-effects

[PATCH 4.14 45/54] usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 17aa31f13cad25daa19d3f923323f552e87bc874 upstream. This fixes an issue that a gadget driver (usb_f_fs) is possible to stop rx transactions after the usb-dmac is used

[PATCH 4.14 46/54] drm/cirrus: Load lut in crtc_commit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit 745fd50f3b044db6a3922e1718306555613164b0 upstream. In the past the ast driver relied upon the fbdev emulation helpers to call ->load_lut at boot-up. But since commit

[PATCH 4.14 47/54] drm: Handle unexpected holes in color-eviction

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit b8ff1802815913aad52695898cccbc9f77b7e726 upstream. During eviction, the driver may free more than one hole in the drm_mm due to the side-effects in evicting the scanned

[PATCH 4.14 54/54] drm/i915/breadcrumbs: Ignore unsubmitted signalers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit 117172c8f9d40ba1de8cb35c6e614422faa03330 upstream. When a request is preempted, it is unsubmitted from the HW queue and removed from the active

[PATCH 4.14 54/54] drm/i915/breadcrumbs: Ignore unsubmitted signalers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit 117172c8f9d40ba1de8cb35c6e614422faa03330 upstream. When a request is preempted, it is unsubmitted from the HW queue and removed from the active list of breadcrumbs. In the

[PATCH 4.14 53/54] drm/amdgpu: add new device to use atpx quirk

4.14-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 v2 1/2] i2c: piix4: Use usleep_range()

The piix4 i2c driver is extremely slow. Replacing msleep() with usleep_range() increases its speed substantially. Use sleep ranges similar to those used in the i2c-801 driver to keep things simple. Signed-off-by: Guenter Roeck --- v2: Changed timeout values for usleep_range()

[PATCH 4.14 53/54] drm/amdgpu: add new device to use atpx quirk

4.14-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 v2 1/2] i2c: piix4: Use usleep_range()

The piix4 i2c driver is extremely slow. Replacing msleep() with usleep_range() increases its speed substantially. Use sleep ranges similar to those used in the i2c-801 driver to keep things simple. Signed-off-by: Guenter Roeck --- v2: Changed timeout values for usleep_range() 2000/2000 ->

[PATCH v2 2/2] i2c: piix4: Use request_muxed_region

Accesses to SB800_PIIX4_SMB_IDX can occur from multiple drivers. One example for another driver is the sp5100_tco driver. Use request_muxed_region() to ensure synchronization. Signed-off-by: Guenter Roeck --- v2: Dropped now unnecessary include of linux/mutex.h Added

[PATCH v2 2/2] i2c: piix4: Use request_muxed_region

Accesses to SB800_PIIX4_SMB_IDX can occur from multiple drivers. One example for another driver is the sp5100_tco driver. Use request_muxed_region() to ensure synchronization. Signed-off-by: Guenter Roeck --- v2: Dropped now unnecessary include of linux/mutex.h Added error message if

[PATCH 4.14 39/54] usb: dwc3: gadget: Set maxpacket size for ep0 IN

4.14-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.14 37/54] drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

4.14-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.14 39/54] usb: dwc3: gadget: Set maxpacket size for ep0 IN

4.14-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.14 37/54] drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

4.14-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.14 40/54] usb: dwc3: ep0: Reset TRB counter for ep0 IN

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thinh Nguyen commit f035d139ffece7b6a7b8bfb17bd0ba715ee57a04 upstream. DWC3 tracks TRB counter for each ep0 direction separately. In control read transfer

[PATCH 4.14 38/54] usb: host: ehci: use correct device pointer for dma ops

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Chen commit 02a10f061a3f8bca1b37332672f50a107198adbe upstream. commit a8c06e407ef9 ("usb: separate out sysdev pointer from usb_bus") converted to use

[PATCH 4.14 40/54] usb: dwc3: ep0: Reset TRB counter for ep0 IN

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thinh Nguyen commit f035d139ffece7b6a7b8bfb17bd0ba715ee57a04 upstream. DWC3 tracks TRB counter for each ep0 direction separately. In control read transfer completion handler, the driver needs

[PATCH 4.14 38/54] usb: host: ehci: use correct device pointer for dma ops

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Chen commit 02a10f061a3f8bca1b37332672f50a107198adbe upstream. commit a8c06e407ef9 ("usb: separate out sysdev pointer from usb_bus") converted to use hcd->self.sysdev for DMA operations

[PATCH 4.14 41/54] usb: ldusb: add PIDs for new CASSY devices supported by this driver

4.14-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.14 41/54] usb: ldusb: add PIDs for new CASSY devices supported by this driver

4.14-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.14 42/54] Revert "usb: musb: host: dont start next rx urb if current one failed"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bin Liu commit 44eb5e12b845cc8a0634f21b70ef07d774eb4b25 upstream. This reverts commit dbac5d07d13e330e6706813c9fde477140fb5d80. commit dbac5d07d13e ("usb: musb: host: don't

[PATCH 4.15 01/64] netfilter: drop outermost socket lock in getsockopt()

4.15-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.14 34/54] arm64: Disable unhandled signal log messages by default

4.14-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.14 42/54] Revert "usb: musb: host: dont start next rx urb if current one failed"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bin Liu commit 44eb5e12b845cc8a0634f21b70ef07d774eb4b25 upstream. This reverts commit dbac5d07d13e330e6706813c9fde477140fb5d80. commit dbac5d07d13e ("usb: musb: host: don't start next rx urb

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