Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Sat, Dec 09, 2017 at 07:32:38PM +0200, Thomas Backlund wrote: > Den 09.12.2017 kl. 19:13, skrev Greg Kroah-Hartman: > > On Sat, Dec 09, 2017 at 07:56:40AM +, Ivan Kozik wrote: > > > On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartman > > >wrote: > > > > On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: > > > > > I saw no problems on 8 of 9 machines, but the last one had a problem > > > > > because it used NVIDIA drivers (387); DKMS reported: > > > > > > > > > > FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only > > > > > symbol 'ex_handler_refcount' > > > > > //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: > > > > > recipe for target '__modpost' failed > > > > > make[3]: *** [__modpost] Error 1 > > > > > > > > Is this a new issue? Does 4.14.4 have this issue? > > > > > > I believe it is a new issue, because I have a 4.14.4 build and an > > > NVIDIA DKMS log for that 4.14.4 showing build success. > > > > > > > Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text > > > > section for refcount exceptions") causing this? > > > > > > That was my guess too, but I did not verify. > > > > That feels really wrong here, I'd like to get some confirmation before I > > add this patch... > > > > It's needed. > > The reason you hit in 4.14.5 queue is because of: > > [PATCH 4.14 64/75] locking/refcounts, x86/asm: Enable > CONFIG_ARCH_HAS_REFCOUNT > > From foo@baz Wed Dec 6 18:04:41 CET 2017 > From: Kees Cook > Date: Sat, 2 Sep 2017 13:09:46 -0700 > Subject: locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT > > > that does this: > > - select ARCH_HAS_REFCOUNTif BROKEN > + select ARCH_HAS_REFCOUNT > > > > So it exposes previously hidden code Ah yes, thanks for the explaination. I've queued up that patch now. greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Sat, Dec 09, 2017 at 07:32:38PM +0200, Thomas Backlund wrote: > Den 09.12.2017 kl. 19:13, skrev Greg Kroah-Hartman: > > On Sat, Dec 09, 2017 at 07:56:40AM +, Ivan Kozik wrote: > > > On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartman > > > wrote: > > > > On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: > > > > > I saw no problems on 8 of 9 machines, but the last one had a problem > > > > > because it used NVIDIA drivers (387); DKMS reported: > > > > > > > > > > FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only > > > > > symbol 'ex_handler_refcount' > > > > > //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: > > > > > recipe for target '__modpost' failed > > > > > make[3]: *** [__modpost] Error 1 > > > > > > > > Is this a new issue? Does 4.14.4 have this issue? > > > > > > I believe it is a new issue, because I have a 4.14.4 build and an > > > NVIDIA DKMS log for that 4.14.4 showing build success. > > > > > > > Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text > > > > section for refcount exceptions") causing this? > > > > > > That was my guess too, but I did not verify. > > > > That feels really wrong here, I'd like to get some confirmation before I > > add this patch... > > > > It's needed. > > The reason you hit in 4.14.5 queue is because of: > > [PATCH 4.14 64/75] locking/refcounts, x86/asm: Enable > CONFIG_ARCH_HAS_REFCOUNT > > From foo@baz Wed Dec 6 18:04:41 CET 2017 > From: Kees Cook > Date: Sat, 2 Sep 2017 13:09:46 -0700 > Subject: locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT > > > that does this: > > - select ARCH_HAS_REFCOUNTif BROKEN > + select ARCH_HAS_REFCOUNT > > > > So it exposes previously hidden code Ah yes, thanks for the explaination. I've queued up that patch now. greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Sat, Dec 9, 2017 at 5:13 PM, Greg Kroah-Hartmanwrote: > On Sat, Dec 09, 2017 at 07:56:40AM +, Ivan Kozik wrote: >> On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartman >> wrote: >> > On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: >> >> I saw no problems on 8 of 9 machines, but the last one had a problem >> >> because it used NVIDIA drivers (387); DKMS reported: >> >> >> >> FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only >> >> symbol 'ex_handler_refcount' >> >> //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: >> >> recipe for target '__modpost' failed >> >> make[3]: *** [__modpost] Error 1 >> > >> > Is this a new issue? Does 4.14.4 have this issue? >> >> I believe it is a new issue, because I have a 4.14.4 build and an >> NVIDIA DKMS log for that 4.14.4 showing build success. >> >> > Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text >> > section for refcount exceptions") causing this? >> >> That was my guess too, but I did not verify. > > That feels really wrong here, I'd like to get some confirmation before I > add this patch... I built a 4.14.4 with all the stable-queue patches except: locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT and NVIDIA built fine with DKMS, so it looks like the refcount enablement patch was responsible. In summary, NVIDIA builds fine with 4.14.4 4.14.4 + all stable-queue except ...Enable CONFIG_ARCH_HAS_REFCOUNT 4.14.4 + all stable-queue + https://lkml.org/lkml/2017/12/4/1110 Thanks, Ivan
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Sat, Dec 9, 2017 at 5:13 PM, Greg Kroah-Hartman wrote: > On Sat, Dec 09, 2017 at 07:56:40AM +, Ivan Kozik wrote: >> On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartman >> wrote: >> > On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: >> >> I saw no problems on 8 of 9 machines, but the last one had a problem >> >> because it used NVIDIA drivers (387); DKMS reported: >> >> >> >> FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only >> >> symbol 'ex_handler_refcount' >> >> //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: >> >> recipe for target '__modpost' failed >> >> make[3]: *** [__modpost] Error 1 >> > >> > Is this a new issue? Does 4.14.4 have this issue? >> >> I believe it is a new issue, because I have a 4.14.4 build and an >> NVIDIA DKMS log for that 4.14.4 showing build success. >> >> > Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text >> > section for refcount exceptions") causing this? >> >> That was my guess too, but I did not verify. > > That feels really wrong here, I'd like to get some confirmation before I > add this patch... I built a 4.14.4 with all the stable-queue patches except: locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT and NVIDIA built fine with DKMS, so it looks like the refcount enablement patch was responsible. In summary, NVIDIA builds fine with 4.14.4 4.14.4 + all stable-queue except ...Enable CONFIG_ARCH_HAS_REFCOUNT 4.14.4 + all stable-queue + https://lkml.org/lkml/2017/12/4/1110 Thanks, Ivan
Re: [PATCH 4.14 00/75] 4.14.5-stable review
Den 09.12.2017 kl. 19:13, skrev Greg Kroah-Hartman: On Sat, Dec 09, 2017 at 07:56:40AM +, Ivan Kozik wrote: On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartmanwrote: On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: I saw no problems on 8 of 9 machines, but the last one had a problem because it used NVIDIA drivers (387); DKMS reported: FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only symbol 'ex_handler_refcount' //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: recipe for target '__modpost' failed make[3]: *** [__modpost] Error 1 Is this a new issue? Does 4.14.4 have this issue? I believe it is a new issue, because I have a 4.14.4 build and an NVIDIA DKMS log for that 4.14.4 showing build success. Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text section for refcount exceptions") causing this? That was my guess too, but I did not verify. That feels really wrong here, I'd like to get some confirmation before I add this patch... It's needed. The reason you hit in 4.14.5 queue is because of: [PATCH 4.14 64/75] locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT From foo@baz Wed Dec 6 18:04:41 CET 2017 From: Kees Cook Date: Sat, 2 Sep 2017 13:09:46 -0700 Subject: locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT that does this: - select ARCH_HAS_REFCOUNTif BROKEN + select ARCH_HAS_REFCOUNT So it exposes previously hidden code -- Thomas
Re: [PATCH 4.14 00/75] 4.14.5-stable review
Den 09.12.2017 kl. 19:13, skrev Greg Kroah-Hartman: On Sat, Dec 09, 2017 at 07:56:40AM +, Ivan Kozik wrote: On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartman wrote: On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: I saw no problems on 8 of 9 machines, but the last one had a problem because it used NVIDIA drivers (387); DKMS reported: FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only symbol 'ex_handler_refcount' //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: recipe for target '__modpost' failed make[3]: *** [__modpost] Error 1 Is this a new issue? Does 4.14.4 have this issue? I believe it is a new issue, because I have a 4.14.4 build and an NVIDIA DKMS log for that 4.14.4 showing build success. Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text section for refcount exceptions") causing this? That was my guess too, but I did not verify. That feels really wrong here, I'd like to get some confirmation before I add this patch... It's needed. The reason you hit in 4.14.5 queue is because of: [PATCH 4.14 64/75] locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT From foo@baz Wed Dec 6 18:04:41 CET 2017 From: Kees Cook Date: Sat, 2 Sep 2017 13:09:46 -0700 Subject: locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT that does this: - select ARCH_HAS_REFCOUNTif BROKEN + select ARCH_HAS_REFCOUNT So it exposes previously hidden code -- Thomas
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Sat, Dec 09, 2017 at 07:56:40AM +, Ivan Kozik wrote: > On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartman >wrote: > > On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: > >> I saw no problems on 8 of 9 machines, but the last one had a problem > >> because it used NVIDIA drivers (387); DKMS reported: > >> > >> FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only > >> symbol 'ex_handler_refcount' > >> //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: > >> recipe for target '__modpost' failed > >> make[3]: *** [__modpost] Error 1 > > > > Is this a new issue? Does 4.14.4 have this issue? > > I believe it is a new issue, because I have a 4.14.4 build and an > NVIDIA DKMS log for that 4.14.4 showing build success. > > > Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text > > section for refcount exceptions") causing this? > > That was my guess too, but I did not verify. That feels really wrong here, I'd like to get some confirmation before I add this patch... thanks, greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Sat, Dec 09, 2017 at 07:56:40AM +, Ivan Kozik wrote: > On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartman > wrote: > > On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: > >> I saw no problems on 8 of 9 machines, but the last one had a problem > >> because it used NVIDIA drivers (387); DKMS reported: > >> > >> FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only > >> symbol 'ex_handler_refcount' > >> //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: > >> recipe for target '__modpost' failed > >> make[3]: *** [__modpost] Error 1 > > > > Is this a new issue? Does 4.14.4 have this issue? > > I believe it is a new issue, because I have a 4.14.4 build and an > NVIDIA DKMS log for that 4.14.4 showing build success. > > > Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text > > section for refcount exceptions") causing this? > > That was my guess too, but I did not verify. That feels really wrong here, I'd like to get some confirmation before I add this patch... thanks, greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Fri, Dec 08, 2017 at 12:03:34PM -0800, Kevin Hilman wrote: > kernelci.org botwrites: > > > stable-rc/linux-4.14.y boot: 142 boots: 1 failed, 127 passed with 14 > > offline (v4.14.4-76-gf91a57b206e0) > > > > Full Boot Summary: > > https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.4-76-gf91a57b206e0/ > > Full Build Summary: > > https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.4-76-gf91a57b206e0/ > > > > Tree: stable-rc > > Branch: linux-4.14.y > > Git Describe: v4.14.4-76-gf91a57b206e0 > > Git Commit: f91a57b206e0ca82c4d3f13372c392e3b374e1ce > > Git URL: > > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > Tested: 76 unique boards, 23 SoC families, 18 builds out of 189 > > > > Boot Regressions Detected: > > > > arm64: > > > > defconfig: > > meson-gxbb-p200: > > TL;DR; All is well. > > Re-ran this one and it's fine. Great, thanks for letting me know. greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Fri, Dec 08, 2017 at 12:03:34PM -0800, Kevin Hilman wrote: > kernelci.org bot writes: > > > stable-rc/linux-4.14.y boot: 142 boots: 1 failed, 127 passed with 14 > > offline (v4.14.4-76-gf91a57b206e0) > > > > Full Boot Summary: > > https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.4-76-gf91a57b206e0/ > > Full Build Summary: > > https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.4-76-gf91a57b206e0/ > > > > Tree: stable-rc > > Branch: linux-4.14.y > > Git Describe: v4.14.4-76-gf91a57b206e0 > > Git Commit: f91a57b206e0ca82c4d3f13372c392e3b374e1ce > > Git URL: > > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > Tested: 76 unique boards, 23 SoC families, 18 builds out of 189 > > > > Boot Regressions Detected: > > > > arm64: > > > > defconfig: > > meson-gxbb-p200: > > TL;DR; All is well. > > Re-ran this one and it's fine. Great, thanks for letting me know. greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartmanwrote: > On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: >> I saw no problems on 8 of 9 machines, but the last one had a problem >> because it used NVIDIA drivers (387); DKMS reported: >> >> FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only >> symbol 'ex_handler_refcount' >> //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: >> recipe for target '__modpost' failed >> make[3]: *** [__modpost] Error 1 > > Is this a new issue? Does 4.14.4 have this issue? I believe it is a new issue, because I have a 4.14.4 build and an NVIDIA DKMS log for that 4.14.4 showing build success. > Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text > section for refcount exceptions") causing this? That was my guess too, but I did not verify. Thanks, Ivan
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartman wrote: > On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: >> I saw no problems on 8 of 9 machines, but the last one had a problem >> because it used NVIDIA drivers (387); DKMS reported: >> >> FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only >> symbol 'ex_handler_refcount' >> //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: >> recipe for target '__modpost' failed >> make[3]: *** [__modpost] Error 1 > > Is this a new issue? Does 4.14.4 have this issue? I believe it is a new issue, because I have a 4.14.4 build and an NVIDIA DKMS log for that 4.14.4 showing build success. > Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text > section for refcount exceptions") causing this? That was my guess too, but I did not verify. Thanks, Ivan
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: > On Thu, Dec 7, 2017 at 1:07 PM, Greg Kroah-Hartman >wrote: > > This is the start of the stable review cycle for the 4.14.5 release. > > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > > Anything received after that time might be too late. > > I saw no problems on 8 of 9 machines, but the last one had a problem > because it used NVIDIA drivers (387); DKMS reported: > > FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only > symbol 'ex_handler_refcount' > //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: > recipe for target '__modpost' failed > make[3]: *** [__modpost] Error 1 Is this a new issue? Does 4.14.4 have this issue? > The drivers built fine after rebuilding Linux with [PATCH] > locking/refcounts: Do not force refcount_t usage as GPL-only export > https://lkml.org/lkml/2017/12/4/1110 > > which appears to be in Linus' tree as b562c171cf011d297059bd0265742eb5fab0ad2f Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text section for refcount exceptions") causing this? thanks, greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote: > On Thu, Dec 7, 2017 at 1:07 PM, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.14.5 release. > > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > > Anything received after that time might be too late. > > I saw no problems on 8 of 9 machines, but the last one had a problem > because it used NVIDIA drivers (387); DKMS reported: > > FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only > symbol 'ex_handler_refcount' > //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: > recipe for target '__modpost' failed > make[3]: *** [__modpost] Error 1 Is this a new issue? Does 4.14.4 have this issue? > The drivers built fine after rebuilding Linux with [PATCH] > locking/refcounts: Do not force refcount_t usage as GPL-only export > https://lkml.org/lkml/2017/12/4/1110 > > which appears to be in Linus' tree as b562c171cf011d297059bd0265742eb5fab0ad2f Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text section for refcount exceptions") causing this? thanks, greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Thu, Dec 7, 2017 at 1:07 PM, Greg Kroah-Hartmanwrote: > This is the start of the stable review cycle for the 4.14.5 release. > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > Anything received after that time might be too late. I saw no problems on 8 of 9 machines, but the last one had a problem because it used NVIDIA drivers (387); DKMS reported: FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only symbol 'ex_handler_refcount' //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: recipe for target '__modpost' failed make[3]: *** [__modpost] Error 1 The drivers built fine after rebuilding Linux with [PATCH] locking/refcounts: Do not force refcount_t usage as GPL-only export https://lkml.org/lkml/2017/12/4/1110 which appears to be in Linus' tree as b562c171cf011d297059bd0265742eb5fab0ad2f Thanks, Ivan
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Thu, Dec 7, 2017 at 1:07 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.5 release. > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > Anything received after that time might be too late. I saw no problems on 8 of 9 machines, but the last one had a problem because it used NVIDIA drivers (387); DKMS reported: FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only symbol 'ex_handler_refcount' //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92: recipe for target '__modpost' failed make[3]: *** [__modpost] Error 1 The drivers built fine after rebuilding Linux with [PATCH] locking/refcounts: Do not force refcount_t usage as GPL-only export https://lkml.org/lkml/2017/12/4/1110 which appears to be in Linus' tree as b562c171cf011d297059bd0265742eb5fab0ad2f Thanks, Ivan
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Thu, Dec 07, 2017 at 12:55:49PM -0800, Guenter Roeck wrote: > On Thu, Dec 07, 2017 at 02:07:22PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.5 release. > > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > > Anything received after that time might be too late. > > > > Build results: > total: 145 pass: 145 fail: 0 > Qemu test results: > total: 124 pass: 124 fail: 0 > > Details are available at http://kerneltests.org/builders. Great, thanks for testing all of these and letting me know. greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Thu, Dec 07, 2017 at 12:55:49PM -0800, Guenter Roeck wrote: > On Thu, Dec 07, 2017 at 02:07:22PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.5 release. > > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > > Anything received after that time might be too late. > > > > Build results: > total: 145 pass: 145 fail: 0 > Qemu test results: > total: 124 pass: 124 fail: 0 > > Details are available at http://kerneltests.org/builders. Great, thanks for testing all of these and letting me know. greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Thu, Dec 07, 2017 at 05:08:23PM -0700, Shuah Khan wrote: > On 12/07/2017 06:07 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.5 release. > > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.5-rc1.gz > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > linux-4.14.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > > > Compiled and booted on my test system. No dmesg regressions. Great, thanks for testing all of these (especially 4.9, the sync stuff was messy), and letting me know. greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Thu, Dec 07, 2017 at 05:08:23PM -0700, Shuah Khan wrote: > On 12/07/2017 06:07 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.5 release. > > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.5-rc1.gz > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > linux-4.14.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > > > Compiled and booted on my test system. No dmesg regressions. Great, thanks for testing all of these (especially 4.9, the sync stuff was messy), and letting me know. greg k-h
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On 7 December 2017 at 18:37, Greg Kroah-Hartmanwrote: > This is the start of the stable review cycle for the 4.14.5 release. > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.5-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.14.y > and the diffstat can be found below. > > thanks, > > greg k-h Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.14.5-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: f91a57b206e0ca82c4d3f13372c392e3b374e1ce git describe: v4.14.4-76-gf91a57b206e0 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.4-76-gf91a57b206e0 No regressions (compared to build v4.14.4-65-g27c40adc50db) Boards, architectures and test suites: - hi6220-hikey - arm64 * boot - pass: 20, * kselftest - pass: 38, skip: 15 * libhugetlbfs - pass: 90, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 21, skip: 1 * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 14, * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 982, skip: 121 * ltp-timers-tests - pass: 12, juno-r2 - arm64 * boot - pass: 20, * kselftest - pass: 37, skip: 15 * libhugetlbfs - pass: 90, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 22, * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 14, * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 985, skip: 121 * ltp-timers-tests - pass: 12, x15 - arm * boot - pass: 20, * kselftest - pass: 33, skip: 20 * libhugetlbfs - pass: 87, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 20, skip: 2 * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 13, skip: 1 * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 1036, skip: 66 * ltp-timers-tests - pass: 12, x86_64 * boot - pass: 20, * kselftest - pass: 53, skip: 14 * libhugetlbfs - pass: 76, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 1, * ltp-fs-tests - pass: 61, skip: 1 * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 21, * ltp-io-tests - pass: 2, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 9, skip: 1 * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 957, skip: 163 * ltp-timers-tests - pass: 12, Documentation - https://collaborate.linaro.org/display/LKFT/Email+Reports Tested-by: Naresh Kamboju
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On 7 December 2017 at 18:37, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.5 release. > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.5-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.14.y > and the diffstat can be found below. > > thanks, > > greg k-h Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.14.5-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: f91a57b206e0ca82c4d3f13372c392e3b374e1ce git describe: v4.14.4-76-gf91a57b206e0 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.4-76-gf91a57b206e0 No regressions (compared to build v4.14.4-65-g27c40adc50db) Boards, architectures and test suites: - hi6220-hikey - arm64 * boot - pass: 20, * kselftest - pass: 38, skip: 15 * libhugetlbfs - pass: 90, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 21, skip: 1 * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 14, * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 982, skip: 121 * ltp-timers-tests - pass: 12, juno-r2 - arm64 * boot - pass: 20, * kselftest - pass: 37, skip: 15 * libhugetlbfs - pass: 90, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 22, * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 14, * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 985, skip: 121 * ltp-timers-tests - pass: 12, x15 - arm * boot - pass: 20, * kselftest - pass: 33, skip: 20 * libhugetlbfs - pass: 87, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 20, skip: 2 * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 13, skip: 1 * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 1036, skip: 66 * ltp-timers-tests - pass: 12, x86_64 * boot - pass: 20, * kselftest - pass: 53, skip: 14 * libhugetlbfs - pass: 76, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 1, * ltp-fs-tests - pass: 61, skip: 1 * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 21, * ltp-io-tests - pass: 2, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 9, skip: 1 * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 957, skip: 163 * ltp-timers-tests - pass: 12, Documentation - https://collaborate.linaro.org/display/LKFT/Email+Reports Tested-by: Naresh Kamboju
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On 12/07/2017 06:07 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.5 release. > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.5-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.14.y > and the diffstat can be found below. > > thanks, > > greg k-h > Compiled and booted on my test system. No dmesg regressions. thanks, -- Shuah
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On 12/07/2017 06:07 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.5 release. > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.5-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.14.y > and the diffstat can be found below. > > thanks, > > greg k-h > Compiled and booted on my test system. No dmesg regressions. thanks, -- Shuah
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Thu, Dec 07, 2017 at 02:07:22PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.5 release. > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > Anything received after that time might be too late. > Build results: total: 145 pass: 145 fail: 0 Qemu test results: total: 124 pass: 124 fail: 0 Details are available at http://kerneltests.org/builders. Guenter
Re: [PATCH 4.14 00/75] 4.14.5-stable review
On Thu, Dec 07, 2017 at 02:07:22PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.5 release. > There are 75 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 Sat Dec 9 13:07:57 UTC 2017. > Anything received after that time might be too late. > Build results: total: 145 pass: 145 fail: 0 Qemu test results: total: 124 pass: 124 fail: 0 Details are available at http://kerneltests.org/builders. Guenter
[PATCH 4.14 00/75] 4.14.5-stable review
This is the start of the stable review cycle for the 4.14.5 release. There are 75 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 Sat Dec 9 13:07:57 UTC 2017. Anything received after that time might be too late. The whole patch series can be found in one patch at: kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.5-rc1.gz or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.14.y and the diffstat can be found below. thanks, greg k-h - Pseudo-Shortlog of commits: Greg Kroah-HartmanLinux 4.14.5-rc1 Colin Ian King usb: host: fix incorrect updating of offset Oliver Neukum USB: usbfs: Filter flags passed in from user space Masakazu Mokuno USB: core: Add type-specific length check of BOS descriptors Yu Chen usb: xhci: fix panic in xhci_free_virt_devices_depth_first Mathias Nyman xhci: Don't show incorrect WARN message about events for empty rings Johan Hovold USB: ulpi: fix bus-node lookup Mike Looijmans usb: hub: Cycle HUB power when initialization fails Gilad Ben-Yossef staging: ccree: fix leak of import() after init() Dominik Behr dma-buf/sw_sync: force signal all unsignaled fences on dying timeline Naveen N. Rao powerpc/kprobes: Disable preemption before invoking probe handler for optprobes Naveen N. Rao powerpc/jprobes: Disable preemption when triggered through ftrace Kees Cook locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT Gustavo A. R. Silva iio: multiplexer: add NULL check on devm_kzalloc() and devm_kmemdup() return values Ladislav Michl iio: adc: ti-ads1015: add 10% to conversion wait time Kirill A. Shutemov mm, x86/mm: Fix performance regression in get_user_pages_fast() Martin Kepplinger perf tools: Fix leaking rec_argv in error cases Arnaldo Carvalho de Melo tools include: Do not use poison with C++ Heiko Carstens s390/ptrace: fix guarded storage regset handling Kees Cook locking/refcounts, x86/asm: Use unique .text section for refcount exceptions Masami Hiramatsu kprobes/x86: Disable preemption in ftrace-based jprobes Thomas Richter perf test attr: Fix python error on empty result Thomas Richter perf test attr: Fix ignored test case result Ioana Radulescu staging: fsl-mc/dpio: Fix incorrect comparison Ian Jamison serial: imx: Update cached mctrl value when changing RTS Ben Hutchings usbip: tools: Install all headers needed for libusbip development Andy Lowe serial: sh-sci: suppress warning for ports without dma channels Jibin Xu sysrq : fix Show Regs call trace on ARM Lu Baolu usb: xhci: Return error when host is dead in xhci_disable_slot() Leo Yan ARM: cpuidle: Correct driver unregistration if init fails Larry Finger staging: rtl8822be: Keep array subscript no lower than zero Ioana Radulescu staging: fsl-dpaa2/eth: Account for Rx FD buffers on error path Chunfeng Yun usb: mtu3: fix error return code in ssusb_gadget_init() Gustavo A. R. Silva EDAC, sb_edac: Fix missing break in switch Geert Uytterhoeven dt-bindings: timer: renesas, cmt: Fix SoC-specific compatible values Ard Biesheuvel clocksource/drivers/arm_arch_timer: Validate CNTFRQ after enabling frame Dave Hansen x86/entry: Use SYSCALL_DEFINE() macros for sys_modify_ldt() Masami Hiramatsu kprobes: Use synchronize_rcu_tasks() for optprobe with CONFIG_PREEMPT=y Aaron Sierra serial: 8250: Preserve DLD[7:4] for PORT_XR17V35X Reinette Chatre x86/intel_rdt: Fix potential deadlock during resctrl mount Reinette Chatre x86/intel_rdt: Initialize bitmask of shareable resource if CDP enabled Kishon Vijay Abraham I PCI: dra7xx: Create functional dependency between PCIe
[PATCH 4.14 00/75] 4.14.5-stable review
This is the start of the stable review cycle for the 4.14.5 release. There are 75 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 Sat Dec 9 13:07:57 UTC 2017. Anything received after that time might be too late. The whole patch series can be found in one patch at: kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.5-rc1.gz or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.14.y and the diffstat can be found below. thanks, greg k-h - Pseudo-Shortlog of commits: Greg Kroah-Hartman Linux 4.14.5-rc1 Colin Ian King usb: host: fix incorrect updating of offset Oliver Neukum USB: usbfs: Filter flags passed in from user space Masakazu Mokuno USB: core: Add type-specific length check of BOS descriptors Yu Chen usb: xhci: fix panic in xhci_free_virt_devices_depth_first Mathias Nyman xhci: Don't show incorrect WARN message about events for empty rings Johan Hovold USB: ulpi: fix bus-node lookup Mike Looijmans usb: hub: Cycle HUB power when initialization fails Gilad Ben-Yossef staging: ccree: fix leak of import() after init() Dominik Behr dma-buf/sw_sync: force signal all unsignaled fences on dying timeline Naveen N. Rao powerpc/kprobes: Disable preemption before invoking probe handler for optprobes Naveen N. Rao powerpc/jprobes: Disable preemption when triggered through ftrace Kees Cook locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT Gustavo A. R. Silva iio: multiplexer: add NULL check on devm_kzalloc() and devm_kmemdup() return values Ladislav Michl iio: adc: ti-ads1015: add 10% to conversion wait time Kirill A. Shutemov mm, x86/mm: Fix performance regression in get_user_pages_fast() Martin Kepplinger perf tools: Fix leaking rec_argv in error cases Arnaldo Carvalho de Melo tools include: Do not use poison with C++ Heiko Carstens s390/ptrace: fix guarded storage regset handling Kees Cook locking/refcounts, x86/asm: Use unique .text section for refcount exceptions Masami Hiramatsu kprobes/x86: Disable preemption in ftrace-based jprobes Thomas Richter perf test attr: Fix python error on empty result Thomas Richter perf test attr: Fix ignored test case result Ioana Radulescu staging: fsl-mc/dpio: Fix incorrect comparison Ian Jamison serial: imx: Update cached mctrl value when changing RTS Ben Hutchings usbip: tools: Install all headers needed for libusbip development Andy Lowe serial: sh-sci: suppress warning for ports without dma channels Jibin Xu sysrq : fix Show Regs call trace on ARM Lu Baolu usb: xhci: Return error when host is dead in xhci_disable_slot() Leo Yan ARM: cpuidle: Correct driver unregistration if init fails Larry Finger staging: rtl8822be: Keep array subscript no lower than zero Ioana Radulescu staging: fsl-dpaa2/eth: Account for Rx FD buffers on error path Chunfeng Yun usb: mtu3: fix error return code in ssusb_gadget_init() Gustavo A. R. Silva EDAC, sb_edac: Fix missing break in switch Geert Uytterhoeven dt-bindings: timer: renesas, cmt: Fix SoC-specific compatible values Ard Biesheuvel clocksource/drivers/arm_arch_timer: Validate CNTFRQ after enabling frame Dave Hansen x86/entry: Use SYSCALL_DEFINE() macros for sys_modify_ldt() Masami Hiramatsu kprobes: Use synchronize_rcu_tasks() for optprobe with CONFIG_PREEMPT=y Aaron Sierra serial: 8250: Preserve DLD[7:4] for PORT_XR17V35X Reinette Chatre x86/intel_rdt: Fix potential deadlock during resctrl mount Reinette Chatre x86/intel_rdt: Initialize bitmask of shareable resource if CDP enabled Kishon Vijay Abraham I PCI: dra7xx: Create functional dependency between PCIe and PHY Alexey Khoroshilov usb: phy: tahvo: fix error handling in tahvo_usb_probe() John Stultz usb: dwc2: Error out of dwc2_hsotg_ep_disable() if we're in host mode John Stultz usb: dwc2: Fix UDC state tracking Peter Zijlstra perf/core: Fix __perf_read_group_add() locking Edward A. James hwmon: (pmbus/core) Prevent unintentional setting of page to 0xFF Subhash Jadavani mmc: sdhci-msm: fix issue with power irq Fabrizio Castro mmc: tmio: check mmc_regulator_get_supply return value Johan Hovold spi: spi-axi: fix potential use-after-free after deregistration Hiromitsu Yamasaki spi: sh-msiof: Fix DMA transfer size check Colin Ian King staging: rtl8188eu: avoid a null dereference on pmlmepriv Stanislaw Gruszka staging: rtl8822be: fix wrong dma unmap len Lukas Wunner serial: 8250_fintek: Fix rs485 disablement on invalid ioctl() Greg Ungerer m68k: fix ColdFire node shift size calculation Bryan O'Donoghue staging: greybus: loopback: Fix