This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. 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/v3.x/stable-review/patch-3.18.94-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-3.18.y and the diffstat can be found below.
thanks,
greg k-h
------------- Pseudo-Shortlog of commits:
Greg Kroah-Hartman gregkh@linuxfoundation.org Linux 3.18.94-rc1
Jesse Chan jc@linux.com ASoC: pcm512x: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
Stefan Agner stefan@agner.ch spi: imx: do not access registers while clocks disabled
Mark Salyzyn salyzyn@android.com selinux: general protection fault in sock_has_perm
Oliver Neukum oneukum@suse.com usb: uas: unconditionally bring back host after reset
Hemant Kumar hemantk@codeaurora.org usb: f_fs: Prevent gadget unbind if it is already unbound
Johan Hovold johan@kernel.org USB: serial: simple: add Motorola Tetra driver
Shuah Khan shuahkh@osg.samsung.com usbip: list: don't list devices attached to vhci_hcd
Shuah Khan shuahkh@osg.samsung.com usbip: prevent bind loops on devices attached to vhci_hcd
Jia-Ju Bai baijiaju1990@gmail.com USB: serial: io_edgeport: fix possible sleep-in-atomic
Oliver Neukum oneukum@suse.com CDC-ACM: apply quirk for card reader
Hans de Goede hdegoede@redhat.com USB: cdc-acm: Do not log urb submission errors on disconnect
Greg Kroah-Hartman gregkh@linuxfoundation.org USB: serial: pl2303: new device id for Chilitag
Larry Finger Larry.Finger@lwfinger.net staging: rtl8188eu: Fix incorrect response to SIOCGIWESSID
Colin Ian King colin.king@canonical.com usb: gadget: don't dereference g until after it has been null checked
Icenowy Zheng icenowy@aosc.io media: usbtv: add a new usbid
Gustavo A. R. Silva garsilva@embeddedor.com scsi: ufs: ufshcd: fix potential NULL pointer dereference in ufshcd_config_vreg
Tetsuo Handa penguin-kernel@I-love.SAKURA.ne.jp quota: Check for register_shrinker() failure.
Geert Uytterhoeven geert+renesas@glider.be net: ethernet: xilinx: Mark XILINX_LL_TEMAC broken on 64-bit
Robert Lippert roblip@gmail.com hwmon: (pmbus) Use 64bit math for DIRECT format values
Andrew Elble aweits@rit.edu nfsd: check for use of the closed special stateid
Trond Myklebust trond.myklebust@primarydata.com nfsd: CLOSE SHOULD return the invalid special stateid for NFSv4.x (x>0)
Eduardo Otubo otubo@redhat.com xen-netfront: remove warning when unloading module
Wanpeng Li wanpeng.li@hotmail.com KVM: VMX: Fix rflags cache during vCPU reset
Chun-Yeow Yeoh yeohchunyeow@gmail.com mac80211: fix the update of path metric for RANN frame
Michael Lyle mlyle@lyle.org bcache: check return value of register_shrinker
Wanpeng Li wanpeng.li@hotmail.com KVM: X86: Fix operand/address-size during instruction decoding
Liran Alon liran.alon@oracle.com KVM: x86: Don't re-execute instruction when not passing CR2 value
Liran Alon liran.alon@oracle.com KVM: x86: emulator: Return to user-mode on L1 CPL=0 emulation failure
Lyude Paul lyude@redhat.com igb: Free IRQs when device is hotplugged
Jesse Chan jc@linux.com gpio: iop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
Takashi Iwai tiwai@suse.de ALSA: seq: Make ioctls race-free
Linus Torvalds torvalds@linux-foundation.org loop: fix concurrent lo_open/lo_release
Richard Weinberger richard@nod.at um: Remove copy&paste code from init.h
Richard Weinberger richard@nod.at um: Stop abusing __KERNEL__
Thomas Meyer thomas@m3y3r.de um: link vmlinux with -no-pie
Dmitry Torokhov dmitry.torokhov@gmail.com Input: do not emit unneeded EV_SYN when suspending
-------------
Diffstat:
Makefile | 4 ++-- arch/um/Makefile | 9 +++++---- arch/um/drivers/mconsole.h | 2 +- arch/um/include/shared/init.h | 24 ++---------------------- arch/um/include/shared/user.h | 2 +- arch/x86/include/asm/kvm_host.h | 3 ++- arch/x86/kvm/emulate.c | 7 +++++++ arch/x86/kvm/vmx.c | 4 ++-- arch/x86/kvm/x86.c | 2 +- arch/x86/um/shared/sysdep/tls.h | 6 +++--- drivers/block/loop.c | 10 ++++++++-- drivers/gpio/gpio-iop.c | 4 ++++ drivers/hwmon/pmbus/pmbus_core.c | 21 ++++++++++++--------- drivers/input/input.c | 5 ++++- drivers/md/bcache/btree.c | 5 ++++- drivers/media/usb/usbtv/usbtv-core.c | 1 + drivers/net/ethernet/intel/igb/igb_main.c | 2 +- drivers/net/ethernet/xilinx/Kconfig | 1 + drivers/net/xen-netfront.c | 18 ++++++++++++++++++ drivers/scsi/ufs/ufshcd.c | 7 +++++-- drivers/spi/spi-imx.c | 15 +++++++++++++-- drivers/staging/rtl8188eu/os_dep/ioctl_linux.c | 14 ++++---------- drivers/usb/class/cdc-acm.c | 5 ++++- drivers/usb/gadget/composite.c | 7 +++++-- drivers/usb/gadget/function/f_fs.c | 3 ++- drivers/usb/serial/Kconfig | 1 + drivers/usb/serial/io_edgeport.c | 1 - drivers/usb/serial/pl2303.c | 1 + drivers/usb/serial/pl2303.h | 1 + drivers/usb/serial/usb-serial-simple.c | 7 +++++++ drivers/usb/storage/uas.c | 7 +++---- fs/nfsd/nfs4state.c | 15 +++++++++++++-- fs/quota/dquot.c | 3 ++- net/mac80211/mesh_hwmp.c | 15 +++++++++------ security/selinux/hooks.c | 2 ++ sound/core/seq/seq_clientmgr.c | 10 ++++++++-- sound/core/seq/seq_clientmgr.h | 1 + sound/soc/codecs/pcm512x-spi.c | 4 ++++ tools/usb/usbip/src/usbip_bind.c | 9 +++++++++ tools/usb/usbip/src/usbip_list.c | 9 +++++++++ 40 files changed, 182 insertions(+), 85 deletions(-)
On Mon, Feb 05, 2018 at 10:23:28AM -0800, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. Anything received after that time might be too late.
You'll also need upstream commit 0b5aedfe0e66 ("um: Fix out-of-tree build") to fix out-of-tree builds for um.
Guenter
On Mon, Feb 05, 2018 at 01:35:44PM -0800, Guenter Roeck wrote:
On Mon, Feb 05, 2018 at 10:23:28AM -0800, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. Anything received after that time might be too late.
You'll also need upstream commit 0b5aedfe0e66 ("um: Fix out-of-tree build") to fix out-of-tree builds for um.
Ah crap, I knew there was a reason I didn't do a 3.18.y release last cycle, and it was because I needed to fix up the um build :(
I'll go queue up this patch now, thanks for letting me know.
greg k-h
On 02/05/2018 11:23 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. 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/v3.x/stable-review/patch-3.18.94-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-3.18.y and the diffstat can be found below.
thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks, -- Shuah
stable-rc/linux-3.18.y boot: 57 boots: 3 failed, 52 passed with 2 untried/unknown (v3.18.93-36-gfc50e0e1d16b)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18... Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.93-36-...
Tree: stable-rc Branch: linux-3.18.y Git Describe: v3.18.93-36-gfc50e0e1d16b Git Commit: fc50e0e1d16b163b620eedaa5906f610fee2e8cc Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 28 unique boards, 12 SoC families, 12 builds out of 181
Boot Regressions Detected:
arm:
exynos_defconfig: exynos5420-arndale-octa: lab-baylibre-seattle: failing since 9 days (last pass: v3.18.92-20-gabb170c68d61 - first fail: v3.18.92-36-gda6d5b92b55f) exynos5800-peach-pi: lab-collabora: new failure (last pass: v3.18.93-25-gb9c290b9fa64)
multi_v7_defconfig: exynos5800-peach-pi: lab-collabora: new failure (last pass: v3.18.93-25-gb9c290b9fa64)
Boot Failures Detected:
arm:
multi_v7_defconfig exynos5800-peach-pi: 1 failed lab
exynos_defconfig exynos5420-arndale-octa: 1 failed lab exynos5800-peach-pi: 1 failed lab
--- For more info write to info@kernelci.org
On Tue 6 Feb, 2018, 12:09 AM Greg Kroah-Hartman, gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. 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/v3.x/stable-review/patch-3.18.94-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-3.18.y and the diffstat can be found below.
thanks,
greg k-h
Builds and boots on the OnePlus 3T, no regressions noticed.
Thanks,
Harsh Shandilya projekt development LLC
On Tue, Feb 06, 2018 at 06:48:53AM +0000, Harsh Shandilya wrote:
On Tue 6 Feb, 2018, 12:09 AM Greg Kroah-Hartman, gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. 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/v3.x/stable-review/patch-3.18.94-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-3.18.y and the diffstat can be found below.
thanks,
greg k-h
Builds and boots on the OnePlus 3T, no regressions noticed.
Yeah! That device is the only reason I keep this tree alive :)
thanks for testing and letting me know.
greg k-h
On Tue 6 Feb, 2018, 4:04 PM Greg Kroah-Hartman, gregkh@linuxfoundation.org wrote:
On Tue, Feb 06, 2018 at 06:48:53AM +0000, Harsh Shandilya wrote:
On Tue 6 Feb, 2018, 12:09 AM Greg Kroah-Hartman, <
gregkh@linuxfoundation.org>
wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. 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/v3.x/stable-review/patch-3.18.94-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-3.18.y and the diffstat can be found below.
thanks,
greg k-h
Builds and boots on the OnePlus 3T, no regressions noticed.
Yeah! That device is the only reason I keep this tree alive :)
thanks for testing and letting me know.
greg k-h
Guess I should drop my kernel tree for the device and save you the pain of maintaining 3.18 :P
Atleast CAF has been keeping up with upstream now thanks to your kernel-common merges so there's still hope for MSM platform users :)
P.S. common merge should go in cleanly, both the merge conflicts I had were from CAF changes.
Thanks, Harsh Shandilya projekt development LLC
On Tue, Feb 06, 2018 at 11:42:15AM +0000, Harsh Shandilya wrote:
On Tue 6 Feb, 2018, 4:04 PM Greg Kroah-Hartman, gregkh@linuxfoundation.org wrote:
On Tue, Feb 06, 2018 at 06:48:53AM +0000, Harsh Shandilya wrote:
On Tue 6 Feb, 2018, 12:09 AM Greg Kroah-Hartman, <
gregkh@linuxfoundation.org>
wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. 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/v3.x/stable-review/patch-3.18.94-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-3.18.y and the diffstat can be found below.
thanks,
greg k-h
Builds and boots on the OnePlus 3T, no regressions noticed.
Yeah! That device is the only reason I keep this tree alive :)
thanks for testing and letting me know.
greg k-h
Guess I should drop my kernel tree for the device and save you the pain of maintaining 3.18 :P
Heh, maybe :)
Atleast CAF has been keeping up with upstream now thanks to your kernel-common merges so there's still hope for MSM platform users :)
That's good to see. Now if only those platform users would actually update their kernels to these new versions :(
P.S. common merge should go in cleanly, both the merge conflicts I had were from CAF changes.
Thanks for letting me know, that's great to hear as I just had a question from some companies who are worried that taking stable patches will cause tons of merge issues. It hasn't in my experience, and seeing reports of this from others is great news.
thanks,
greg k-h
On 02/06/2018 05:14 AM, Greg Kroah-Hartman wrote:
On Tue, Feb 06, 2018 at 11:42:15AM +0000, Harsh Shandilya wrote:
On Tue 6 Feb, 2018, 4:04 PM Greg Kroah-Hartman, gregkh@linuxfoundation.org wrote:
On Tue, Feb 06, 2018 at 06:48:53AM +0000, Harsh Shandilya wrote:
On Tue 6 Feb, 2018, 12:09 AM Greg Kroah-Hartman, <
gregkh@linuxfoundation.org>
wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. 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/v3.x/stable-review/patch-3.18.94-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-3.18.y and the diffstat can be found below.
thanks,
greg k-h
Builds and boots on the OnePlus 3T, no regressions noticed.
Yeah! That device is the only reason I keep this tree alive :)
thanks for testing and letting me know.
greg k-h
Guess I should drop my kernel tree for the device and save you the pain of maintaining 3.18 :P
Heh, maybe :)
Atleast CAF has been keeping up with upstream now thanks to your kernel-common merges so there's still hope for MSM platform users :)
That's good to see. Now if only those platform users would actually update their kernels to these new versions :(
P.S. common merge should go in cleanly, both the merge conflicts I had were from CAF changes.
Thanks for letting me know, that's great to hear as I just had a question from some companies who are worried that taking stable patches will cause tons of merge issues. It hasn't in my experience, and seeing reports of this from others is great news.
From merging v4.4 and v4.14 into the respective ChromeOS branches, I would conclude that merging is for the most part easy. Major source of conflicts, if they happen, is that we may already have picked up additional commits from upstream.
This is only true, though, if merges are done on a release-by-release basis and if the merge happens shortly after a stable release is available. Otherwise, as time goes by, merges become more and more difficult (almost exponentially over time). Wait for more than 2-3 months between merges and it becomes almost impossible.
For reference, the top of tree for both branches is v4.14.16-3823-g597d36f1d331 v4.4.114-12977-ga207b53fe939 meaning there are _lots_ of patches on top of the mainline stable releases.
Also, overall, the rate of regressions is quite low (if I recall correctly, somewhere between 3 and 5 in chromeos-4.4, and one so far in chromeos-4.14, ie below 0.1%).
Guenter
On Tue, Feb 06, 2018 at 06:48:17AM -0800, Guenter Roeck wrote:
On 02/06/2018 05:14 AM, Greg Kroah-Hartman wrote:
Thanks for letting me know, that's great to hear as I just had a question from some companies who are worried that taking stable patches will cause tons of merge issues. It hasn't in my experience, and seeing reports of this from others is great news.
From merging v4.4 and v4.14 into the respective ChromeOS branches, I would conclude that merging is for the most part easy. Major source of conflicts, if they happen, is that we may already have picked up additional commits from upstream.
This is only true, though, if merges are done on a release-by-release basis and if the merge happens shortly after a stable release is available. Otherwise, as time goes by, merges become more and more difficult (almost exponentially over time). Wait for more than 2-3 months between merges and it becomes almost impossible.
For reference, the top of tree for both branches is v4.14.16-3823-g597d36f1d331 v4.4.114-12977-ga207b53fe939
Ugh, 12k patches is not trivial, gotta love those graphic drivers :(
meaning there are _lots_ of patches on top of the mainline stable releases.
Also, overall, the rate of regressions is quite low (if I recall correctly, somewhere between 3 and 5 in chromeos-4.4, and one so far in chromeos-4.14, ie below 0.1%).
Thanks a lot for the feedback, this helps out a lot when talking to companies that are "afraid" of doing merges with stable.
Based on this, one phone vendor just forward merged their 4.4.y based tree to the latest release in a few hours with no reported problems at all, so it has already helped out with tangable results.
thanks,
greg k-h
On Wed, Feb 07, 2018 at 06:37:06AM -0800, Greg Kroah-Hartman wrote:
On Tue, Feb 06, 2018 at 06:48:17AM -0800, Guenter Roeck wrote:
On 02/06/2018 05:14 AM, Greg Kroah-Hartman wrote:
Thanks for letting me know, that's great to hear as I just had a question from some companies who are worried that taking stable patches will cause tons of merge issues. It hasn't in my experience, and seeing reports of this from others is great news.
From merging v4.4 and v4.14 into the respective ChromeOS branches, I would conclude that merging is for the most part easy. Major source of conflicts, if they happen, is that we may already have picked up additional commits from upstream.
This is only true, though, if merges are done on a release-by-release basis and if the merge happens shortly after a stable release is available. Otherwise, as time goes by, merges become more and more difficult (almost exponentially over time). Wait for more than 2-3 months between merges and it becomes almost impossible.
For reference, the top of tree for both branches is v4.14.16-3823-g597d36f1d331 v4.4.114-12977-ga207b53fe939
Ugh, 12k patches is not trivial, gotta love those graphic drivers :(
That, plus a gazillion backports, plus vendor specific out-of-tree wireless drivers, plus all the Android stuff. No, there is no "love" involved, only annoyance :-(.
meaning there are _lots_ of patches on top of the mainline stable releases.
Also, overall, the rate of regressions is quite low (if I recall correctly, somewhere between 3 and 5 in chromeos-4.4, and one so far in chromeos-4.14, ie below 0.1%).
Thanks a lot for the feedback, this helps out a lot when talking to companies that are "afraid" of doing merges with stable.
Based on this, one phone vendor just forward merged their 4.4.y based tree to the latest release in a few hours with no reported problems at all, so it has already helped out with tangable results.
Excellent. More test coverage!
Guenter
On 02/05/2018 10:23 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. Anything received after that time might be too late.
For v3.18.93-38-g9193bae:
Build results: total: 136 pass: 136 fail: 0 Qemu test results: total: 112 pass: 112 fail: 0
Details are available at http://kerneltests.org/builders.
Guenter
On Tue, Feb 06, 2018 at 06:29:16AM -0800, Guenter Roeck wrote:
On 02/05/2018 10:23 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. Anything received after that time might be too late.
For v3.18.93-38-g9193bae:
Build results: total: 136 pass: 136 fail: 0 Qemu test results: total: 112 pass: 112 fail: 0
Details are available at http://kerneltests.org/builders.
Yeah, it's fixed! :)
thanks for testing all of these and letting me know.
greg k-h
On Tue 6 Feb, 2018, 12:09 AM Greg Kroah-Hartman, gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. Anything received after that time might be too late.
Let's find out if I am too late.
https://www.spinics.net/lists/stable/msg213160.html will have to be lined up for 3.18.94, or to .95 if I'm late since it's fixing a erroneous backport from 3.18.93 which went unnoticed until after release. The email bringing it up and the subsequent patch were probably lost in the usual stable noise. I have applied it to the CAF tree for the oneplus3 and verified that it does not break compilation or userspace for arm64.
Thanks, Harsh Shandilya projekt development LLC
On Wed, Feb 07, 2018 at 03:19:07PM +0000, Harsh Shandilya wrote:
On Tue 6 Feb, 2018, 12:09 AM Greg Kroah-Hartman, gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 3.18.94 release. There are 36 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 7 18:23:41 UTC 2018. Anything received after that time might be too late.
Let's find out if I am too late.
https://www.spinics.net/lists/stable/msg213160.html will have to be lined up for 3.18.94, or to .95 if I'm late since it's fixing a erroneous backport from 3.18.93 which went unnoticed until after release. The email bringing it up and the subsequent patch were probably lost in the usual stable noise. I have applied it to the CAF tree for the oneplus3 and verified that it does not break compilation or userspace for arm64.
It will be queued up for the next release, I missed it this time, sorry.
greg k-h
-
Greg Kroah-Hartman -
Guenter Roeck -
Harsh Shandilya -
kernelci.org bot -
Shuah Khan