Re: [PATCH 4.9 000/116] 4.9.2-stable review
On Mon, Jan 09, 2017 at 10:19:31AM -0800, Kevin Hilman wrote: > Greg Kroah-Hartmanwrites: > > > On Fri, Jan 06, 2017 at 09:42:24PM -0800, kernelci.org bot wrote: > >> stable-rc boot: 513 boots: 4 failed, 489 passed with 20 offline > >> (v4.9.1-117-ge3bc65e52a08) > >> > >> Full Boot Summary: > >> https://kernelci.org/boot/all/job/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ > >> Full Build Summary: > >> https://kernelci.org/build/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ > >> > >> Tree: stable-rc > >> Branch: local/linux-4.9.y > >> Git Describe: v4.9.1-117-ge3bc65e52a08 > >> Git Commit: e3bc65e52a086ea9bcc31605737bbf0476f9bcd3 > >> Git URL: > >> http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >> Tested: 88 unique boards, 25 SoC families, 35 builds out of 206 > >> > >> Boot Regressions Detected: > >> > >> arm: > >> > >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: > >> vexpress-v2p-ca15_a7: > >> lab-broonie: new failure (last pass: v4.9.1) > >> > >> Boot Failures Detected: > >> > >> arm: > >> > >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y > >> vexpress-v2p-ca15_a7: 1 failed lab > >> > >> sunxi_defconfig > >> sun4i-a10-cubieboard: 1 failed lab > >> > >> exynos_defconfig > >> exynos5422-odroidxu3_rootfs:nfs: 1 failed lab > >> > >> arm64: > >> > >> defconfig+CONFIG_CPU_BIG_ENDIAN=y > >> juno-r2: 1 failed lab > > > > Are all of these really "failures"? Some of them seem like they really > > did boot, but the test system didn't detect it? > > > > I don't know what to do with these reports, should I trust them that I > > broke something, or just ignore them and let someone else dig into them > > to determine if it's a false-positive or something like that? > > Until we get these more reliable, you can assume that I'll flag > something that's really a blocker. Ok, thanks for that, it makes my life easier in trying to parse these reports :) greg k-h
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On Mon, Jan 09, 2017 at 10:19:31AM -0800, Kevin Hilman wrote: > Greg Kroah-Hartman writes: > > > On Fri, Jan 06, 2017 at 09:42:24PM -0800, kernelci.org bot wrote: > >> stable-rc boot: 513 boots: 4 failed, 489 passed with 20 offline > >> (v4.9.1-117-ge3bc65e52a08) > >> > >> Full Boot Summary: > >> https://kernelci.org/boot/all/job/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ > >> Full Build Summary: > >> https://kernelci.org/build/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ > >> > >> Tree: stable-rc > >> Branch: local/linux-4.9.y > >> Git Describe: v4.9.1-117-ge3bc65e52a08 > >> Git Commit: e3bc65e52a086ea9bcc31605737bbf0476f9bcd3 > >> Git URL: > >> http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >> Tested: 88 unique boards, 25 SoC families, 35 builds out of 206 > >> > >> Boot Regressions Detected: > >> > >> arm: > >> > >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: > >> vexpress-v2p-ca15_a7: > >> lab-broonie: new failure (last pass: v4.9.1) > >> > >> Boot Failures Detected: > >> > >> arm: > >> > >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y > >> vexpress-v2p-ca15_a7: 1 failed lab > >> > >> sunxi_defconfig > >> sun4i-a10-cubieboard: 1 failed lab > >> > >> exynos_defconfig > >> exynos5422-odroidxu3_rootfs:nfs: 1 failed lab > >> > >> arm64: > >> > >> defconfig+CONFIG_CPU_BIG_ENDIAN=y > >> juno-r2: 1 failed lab > > > > Are all of these really "failures"? Some of them seem like they really > > did boot, but the test system didn't detect it? > > > > I don't know what to do with these reports, should I trust them that I > > broke something, or just ignore them and let someone else dig into them > > to determine if it's a false-positive or something like that? > > Until we get these more reliable, you can assume that I'll flag > something that's really a blocker. Ok, thanks for that, it makes my life easier in trying to parse these reports :) greg k-h
Re: [PATCH 4.9 000/116] 4.9.2-stable review
Greg Kroah-Hartmanwrites: > On Fri, Jan 06, 2017 at 09:42:24PM -0800, kernelci.org bot wrote: >> stable-rc boot: 513 boots: 4 failed, 489 passed with 20 offline >> (v4.9.1-117-ge3bc65e52a08) >> >> Full Boot Summary: >> https://kernelci.org/boot/all/job/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ >> Full Build Summary: >> https://kernelci.org/build/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ >> >> Tree: stable-rc >> Branch: local/linux-4.9.y >> Git Describe: v4.9.1-117-ge3bc65e52a08 >> Git Commit: e3bc65e52a086ea9bcc31605737bbf0476f9bcd3 >> Git URL: >> http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> Tested: 88 unique boards, 25 SoC families, 35 builds out of 206 >> >> Boot Regressions Detected: >> >> arm: >> >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: >> vexpress-v2p-ca15_a7: >> lab-broonie: new failure (last pass: v4.9.1) >> >> Boot Failures Detected: >> >> arm: >> >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y >> vexpress-v2p-ca15_a7: 1 failed lab >> >> sunxi_defconfig >> sun4i-a10-cubieboard: 1 failed lab >> >> exynos_defconfig >> exynos5422-odroidxu3_rootfs:nfs: 1 failed lab >> >> arm64: >> >> defconfig+CONFIG_CPU_BIG_ENDIAN=y >> juno-r2: 1 failed lab > > Are all of these really "failures"? Some of them seem like they really > did boot, but the test system didn't detect it? > > I don't know what to do with these reports, should I trust them that I > broke something, or just ignore them and let someone else dig into them > to determine if it's a false-positive or something like that? Until we get these more reliable, you can assume that I'll flag something that's really a blocker. Only the exynos5422-odroidxu3 failure is a true failure which is also happendin in mainline. It's been reported and fixed. The others are silly lab/hardware issues that are hard to get stabilized. e.g. QEMU taking a really long time to boot CONFIG_PROVE_LOCKING=y kernels, flaky USB-UART cables etc. Kevin
Re: [PATCH 4.9 000/116] 4.9.2-stable review
Greg Kroah-Hartman writes: > On Fri, Jan 06, 2017 at 09:42:24PM -0800, kernelci.org bot wrote: >> stable-rc boot: 513 boots: 4 failed, 489 passed with 20 offline >> (v4.9.1-117-ge3bc65e52a08) >> >> Full Boot Summary: >> https://kernelci.org/boot/all/job/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ >> Full Build Summary: >> https://kernelci.org/build/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ >> >> Tree: stable-rc >> Branch: local/linux-4.9.y >> Git Describe: v4.9.1-117-ge3bc65e52a08 >> Git Commit: e3bc65e52a086ea9bcc31605737bbf0476f9bcd3 >> Git URL: >> http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> Tested: 88 unique boards, 25 SoC families, 35 builds out of 206 >> >> Boot Regressions Detected: >> >> arm: >> >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: >> vexpress-v2p-ca15_a7: >> lab-broonie: new failure (last pass: v4.9.1) >> >> Boot Failures Detected: >> >> arm: >> >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y >> vexpress-v2p-ca15_a7: 1 failed lab >> >> sunxi_defconfig >> sun4i-a10-cubieboard: 1 failed lab >> >> exynos_defconfig >> exynos5422-odroidxu3_rootfs:nfs: 1 failed lab >> >> arm64: >> >> defconfig+CONFIG_CPU_BIG_ENDIAN=y >> juno-r2: 1 failed lab > > Are all of these really "failures"? Some of them seem like they really > did boot, but the test system didn't detect it? > > I don't know what to do with these reports, should I trust them that I > broke something, or just ignore them and let someone else dig into them > to determine if it's a false-positive or something like that? Until we get these more reliable, you can assume that I'll flag something that's really a blocker. Only the exynos5422-odroidxu3 failure is a true failure which is also happendin in mainline. It's been reported and fixed. The others are silly lab/hardware issues that are hard to get stabilized. e.g. QEMU taking a really long time to boot CONFIG_PROVE_LOCKING=y kernels, flaky USB-UART cables etc. Kevin
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On Sat, Jan 07, 2017 at 08:02:28AM -0800, Guenter Roeck wrote: > On 01/06/2017 01:42 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.2 release. > > There are 116 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 Sun Jan 8 21:38:42 UTC 2017. > > Anything received after that time might be too late. > > > > Build results: > total: 150 pass: 149 fail: 1 > Failed builds: > avr32:merisc_defconfig > > Qemu test results: > total: 122 pass: 122 fail: 0 > > As before, the avr32 failure is caused by a toolchain problem. Wonderful, thanks for testing all of these and letting me know. greg k-h
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On Sat, Jan 07, 2017 at 08:02:28AM -0800, Guenter Roeck wrote: > On 01/06/2017 01:42 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.2 release. > > There are 116 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 Sun Jan 8 21:38:42 UTC 2017. > > Anything received after that time might be too late. > > > > Build results: > total: 150 pass: 149 fail: 1 > Failed builds: > avr32:merisc_defconfig > > Qemu test results: > total: 122 pass: 122 fail: 0 > > As before, the avr32 failure is caused by a toolchain problem. Wonderful, thanks for testing all of these and letting me know. greg k-h
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On 01/06/2017 01:42 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.2 release. There are 116 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 Sun Jan 8 21:38:42 UTC 2017. Anything received after that time might be too late. Build results: total: 150 pass: 149 fail: 1 Failed builds: avr32:merisc_defconfig Qemu test results: total: 122 pass: 122 fail: 0 As before, the avr32 failure is caused by a toolchain problem. Details are available at http://kerneltests.org/builders. Guenter
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On 01/06/2017 01:42 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.2 release. There are 116 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 Sun Jan 8 21:38:42 UTC 2017. Anything received after that time might be too late. Build results: total: 150 pass: 149 fail: 1 Failed builds: avr32:merisc_defconfig Qemu test results: total: 122 pass: 122 fail: 0 As before, the avr32 failure is caused by a toolchain problem. Details are available at http://kerneltests.org/builders. Guenter
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On Fri, Jan 06, 2017 at 09:42:24PM -0800, kernelci.org bot wrote: > stable-rc boot: 513 boots: 4 failed, 489 passed with 20 offline > (v4.9.1-117-ge3bc65e52a08) > > Full Boot Summary: > https://kernelci.org/boot/all/job/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ > Full Build Summary: > https://kernelci.org/build/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ > > Tree: stable-rc > Branch: local/linux-4.9.y > Git Describe: v4.9.1-117-ge3bc65e52a08 > Git Commit: e3bc65e52a086ea9bcc31605737bbf0476f9bcd3 > Git URL: > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > Tested: 88 unique boards, 25 SoC families, 35 builds out of 206 > > Boot Regressions Detected: > > arm: > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: > vexpress-v2p-ca15_a7: > lab-broonie: new failure (last pass: v4.9.1) > > Boot Failures Detected: > > arm: > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y > vexpress-v2p-ca15_a7: 1 failed lab > > sunxi_defconfig > sun4i-a10-cubieboard: 1 failed lab > > exynos_defconfig > exynos5422-odroidxu3_rootfs:nfs: 1 failed lab > > arm64: > > defconfig+CONFIG_CPU_BIG_ENDIAN=y > juno-r2: 1 failed lab Are all of these really "failures"? Some of them seem like they really did boot, but the test system didn't detect it? I don't know what to do with these reports, should I trust them that I broke something, or just ignore them and let someone else dig into them to determine if it's a false-positive or something like that? thanks, greg k-h
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On Fri, Jan 06, 2017 at 09:42:24PM -0800, kernelci.org bot wrote: > stable-rc boot: 513 boots: 4 failed, 489 passed with 20 offline > (v4.9.1-117-ge3bc65e52a08) > > Full Boot Summary: > https://kernelci.org/boot/all/job/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ > Full Build Summary: > https://kernelci.org/build/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/ > > Tree: stable-rc > Branch: local/linux-4.9.y > Git Describe: v4.9.1-117-ge3bc65e52a08 > Git Commit: e3bc65e52a086ea9bcc31605737bbf0476f9bcd3 > Git URL: > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > Tested: 88 unique boards, 25 SoC families, 35 builds out of 206 > > Boot Regressions Detected: > > arm: > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: > vexpress-v2p-ca15_a7: > lab-broonie: new failure (last pass: v4.9.1) > > Boot Failures Detected: > > arm: > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y > vexpress-v2p-ca15_a7: 1 failed lab > > sunxi_defconfig > sun4i-a10-cubieboard: 1 failed lab > > exynos_defconfig > exynos5422-odroidxu3_rootfs:nfs: 1 failed lab > > arm64: > > defconfig+CONFIG_CPU_BIG_ENDIAN=y > juno-r2: 1 failed lab Are all of these really "failures"? Some of them seem like they really did boot, but the test system didn't detect it? I don't know what to do with these reports, should I trust them that I broke something, or just ignore them and let someone else dig into them to determine if it's a false-positive or something like that? thanks, greg k-h
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On Fri, Jan 06, 2017 at 07:04:20PM -0700, Shuah Khan wrote: > On 01/06/2017 02:42 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.2 release. > > There are 116 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 Sun Jan 8 21:38:42 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.9.2-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.9.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > > > Compiled and booted on my test system. No dmesg regressions. Thanks for testing all of these and letting me know. greg k-h
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On Fri, Jan 06, 2017 at 07:04:20PM -0700, Shuah Khan wrote: > On 01/06/2017 02:42 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.2 release. > > There are 116 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 Sun Jan 8 21:38:42 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.9.2-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.9.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > > > Compiled and booted on my test system. No dmesg regressions. Thanks for testing all of these and letting me know. greg k-h
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On 01/06/2017 02:42 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.2 release. > There are 116 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 Sun Jan 8 21:38:42 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.9.2-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.9.y > and the diffstat can be found below. > > thanks, > > greg k-h > Compiled and booted on my test system. No dmesg regressions. thanks, -- Shuah -- Shuah Khan Sr. Linux Kernel Developer Open Source Innovation Group Samsung Research America(Silicon Valley) shuah...@samsung.com
Re: [PATCH 4.9 000/116] 4.9.2-stable review
On 01/06/2017 02:42 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.2 release. > There are 116 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 Sun Jan 8 21:38:42 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.9.2-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.9.y > and the diffstat can be found below. > > thanks, > > greg k-h > Compiled and booted on my test system. No dmesg regressions. thanks, -- Shuah -- Shuah Khan Sr. Linux Kernel Developer Open Source Innovation Group Samsung Research America(Silicon Valley) shuah...@samsung.com
[PATCH 4.9 000/116] 4.9.2-stable review
This is the start of the stable review cycle for the 4.9.2 release. There are 116 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 Sun Jan 8 21:38:42 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.9.2-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.9.y and the diffstat can be found below. thanks, greg k-h - Pseudo-Shortlog of commits: Greg Kroah-HartmanLinux 4.9.2-rc1 Mika Kuoppala drm/i915: Fix setting of boost freq tunable Paulo Zanoni drm/i915: skip the first 4k of stolen memory on everything >= gen8 Ville Syrjälä drm/i915: Initialize dev_priv->atomic_cdclk_freq at init time Ville Syrjälä drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things Hans de Goede drm/i915/dsi: Do not clear DPOUNIT_CLOCK_GATE_DISABLE from vlv_init_display_clock_gating Hans de Goede drm/i915/dsi: Fix chv_exec_gpio disabling the GPIOs it is setting Thomas Petazzoni net: mvpp2: fix dma unmapping of TX buffers for fragments Al Viro sg_write()/bsg_write() is not fit to be called under KERNEL_DS Ben Hutchings kconfig/nconf: Fix hang when editing symbol with a long prompt Andy Grover target/user: Fix use-after-free of tcmu_cmds if they are expired Dan Williams libnvdimm, pfn: fix align attribute David Daney of, numa: Return NUMA_NO_NODE from disable of_node_to_nid() if nid not possible. Nicholas Piggin powerpc/boot: Request no dynamic linker for boot wrapper Geoff Levand powerpc/ps3: Fix system hang with GCC 5 builds Nicholas Piggin powerpc/64e: Convert cmpi to cmpwi in head_64.S NeilBrown SUNRPC: fix refcounting problems with auth_gss messages. Trond Myklebust pNFS: Fix a deadlock between read resends and layoutreturn Trond Myklebust pNFS: Clear NFS_LAYOUT_RETURN_REQUESTED when invalidating the layout stateid Trond Myklebust pNFS: Don't clear the layout stateid if a layout return is outstanding Trond Myklebust pNFS: On error, do not send LAYOUTGET until the LAYOUTRETURN has completed Al Viro nfs_write_end(): fix handling of short copies Ilya Dryomov libceph: verify authorize reply on connect Alan Stern PCI: Check for PME in targeted sleep state Shiraz Saleem i40iw: Use correct src address in memcpy to rdma stats counters Miklos Szeredi bad_inode: add missing i_op initializers Jingkui Wang Input: drv260x - fix input device's parent assignment Laurent Pinchart v4l: tvp5150: Add missing break in set control handler Andrey Utkin media: solo6x10: fix lockup by avoiding delayed register write Marek Szyprowski s5p-mfc: fix failure path of s5p_mfc_alloc_memdev() Antti Palosaari mn88473: fix chip id check on probe Antti Palosaari mn88472: fix chip id check on probe Bart Van Assche IB/cma: Fix a race condition in iboe_addr_get_sgid() Bart Van Assche IB/rxe: Fix a memory leak in rxe_qp_cleanup() Bart Van Assche IB/multicast: Check ib_find_pkey() return value Bart Van Assche IPoIB: Avoid reading an uninitialized member variable Bart Van Assche IB/mad: Fix an array index check Steven Rostedt (Red Hat) fgraph: Handle a case where a tracer ignores set_graph_notrace Thomas Gleixner x86/smpboot: Make logical package management more robust Marcos Paulo de Souza platform/x86: asus-nb-wmi.c: Add X45U quirk Steven Rostedt (Red Hat) ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps to it Michael S. Tsirkin vsock/virtio: fix src/dst cid format Jan Kara
[PATCH 4.9 000/116] 4.9.2-stable review
This is the start of the stable review cycle for the 4.9.2 release. There are 116 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 Sun Jan 8 21:38:42 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.9.2-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.9.y and the diffstat can be found below. thanks, greg k-h - Pseudo-Shortlog of commits: Greg Kroah-Hartman Linux 4.9.2-rc1 Mika Kuoppala drm/i915: Fix setting of boost freq tunable Paulo Zanoni drm/i915: skip the first 4k of stolen memory on everything >= gen8 Ville Syrjälä drm/i915: Initialize dev_priv->atomic_cdclk_freq at init time Ville Syrjälä drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things Hans de Goede drm/i915/dsi: Do not clear DPOUNIT_CLOCK_GATE_DISABLE from vlv_init_display_clock_gating Hans de Goede drm/i915/dsi: Fix chv_exec_gpio disabling the GPIOs it is setting Thomas Petazzoni net: mvpp2: fix dma unmapping of TX buffers for fragments Al Viro sg_write()/bsg_write() is not fit to be called under KERNEL_DS Ben Hutchings kconfig/nconf: Fix hang when editing symbol with a long prompt Andy Grover target/user: Fix use-after-free of tcmu_cmds if they are expired Dan Williams libnvdimm, pfn: fix align attribute David Daney of, numa: Return NUMA_NO_NODE from disable of_node_to_nid() if nid not possible. Nicholas Piggin powerpc/boot: Request no dynamic linker for boot wrapper Geoff Levand powerpc/ps3: Fix system hang with GCC 5 builds Nicholas Piggin powerpc/64e: Convert cmpi to cmpwi in head_64.S NeilBrown SUNRPC: fix refcounting problems with auth_gss messages. Trond Myklebust pNFS: Fix a deadlock between read resends and layoutreturn Trond Myklebust pNFS: Clear NFS_LAYOUT_RETURN_REQUESTED when invalidating the layout stateid Trond Myklebust pNFS: Don't clear the layout stateid if a layout return is outstanding Trond Myklebust pNFS: On error, do not send LAYOUTGET until the LAYOUTRETURN has completed Al Viro nfs_write_end(): fix handling of short copies Ilya Dryomov libceph: verify authorize reply on connect Alan Stern PCI: Check for PME in targeted sleep state Shiraz Saleem i40iw: Use correct src address in memcpy to rdma stats counters Miklos Szeredi bad_inode: add missing i_op initializers Jingkui Wang Input: drv260x - fix input device's parent assignment Laurent Pinchart v4l: tvp5150: Add missing break in set control handler Andrey Utkin media: solo6x10: fix lockup by avoiding delayed register write Marek Szyprowski s5p-mfc: fix failure path of s5p_mfc_alloc_memdev() Antti Palosaari mn88473: fix chip id check on probe Antti Palosaari mn88472: fix chip id check on probe Bart Van Assche IB/cma: Fix a race condition in iboe_addr_get_sgid() Bart Van Assche IB/rxe: Fix a memory leak in rxe_qp_cleanup() Bart Van Assche IB/multicast: Check ib_find_pkey() return value Bart Van Assche IPoIB: Avoid reading an uninitialized member variable Bart Van Assche IB/mad: Fix an array index check Steven Rostedt (Red Hat) fgraph: Handle a case where a tracer ignores set_graph_notrace Thomas Gleixner x86/smpboot: Make logical package management more robust Marcos Paulo de Souza platform/x86: asus-nb-wmi.c: Add X45U quirk Steven Rostedt (Red Hat) ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps to it Michael S. Tsirkin vsock/virtio: fix src/dst cid format Jan Kara fsnotify: Fix possible use-after-free in inode iteration on umount Jim Mattson kvm: nVMX: Allow L1 to intercept software exceptions (#BP and #OF) Paul Mackerras KVM: PPC: Book3S HV: Don't lose hardware R/C bit updates in H_PROTECT Paul Mackerras KVM: PPC: Book3S HV: Save/restore XER in checkpointed register state Kevin Barnett scsi: aacraid: remove wildcard for series 9 controllers Konstantin Khlebnikov md/raid5: limit request size according to implementation limits Josh Cartwright sc16is7xx: Drop bogus use of IRQF_ONESHOT Kees Cook latent_entropy: fix ARM build error on earlier gcc Marc Zyngier arm64: KVM: pmu: Reset PMSELR_EL0.SEL to a sane value before entering the guest Heiko Carstens s390/kexec: use node 0 when re-adding crash kernel memory Gerald Schaefer s390/vmlogrdr: fix IUCV buffer allocation Yves-Alexis Perez firmware: fix usermode helper fallback loading Vineet Gupta ARC: mm: arc700: Don't assume 2 colours for aliasing VIPT dcache Wei Fang scsi: avoid a permanent stop of the scsi