January 2019 - Linux-stable-mirror

by Greg KH

I'm announcing the release of the 4.9.152 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser: http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary thanks, greg k-h ------------ Makefile | 2 arch/arm64/include/asm/kvm_arm.h | 3 arch/arm64/kernel/head.S | 5 - arch/arm64/kernel/kaslr.c | 8 +- arch/arm64/kvm/hyp/switch.c | 2 arch/mips/Kconfig | 1 arch/mips/pci/msi-octeon.c | 4 - crypto/authenc.c | 14 +++- crypto/authencesn.c | 2 drivers/block/loop.c | 79 +++++++++++------------ drivers/block/loop.h | 1 drivers/block/nbd.c | 37 ++++------ drivers/crypto/caam/caamhash.c | 15 ++-- drivers/crypto/talitos.c | 27 ++----- drivers/gpu/drm/drm_fb_helper.c | 7 +- drivers/media/platform/vivid/vivid-kthread-cap.c | 5 + drivers/media/platform/vivid/vivid-kthread-out.c | 5 + drivers/media/platform/vivid/vivid-vid-common.c | 2 drivers/media/usb/em28xx/em28xx-video.c | 4 - drivers/media/v4l2-core/videobuf2-core.c | 14 ++-- drivers/mfd/tps6586x.c | 24 ++++++ drivers/net/bonding/bond_main.c | 3 drivers/scsi/scsi_pm.c | 26 ++++--- drivers/scsi/sd.c | 6 + drivers/tty/tty_io.c | 22 ++++-- drivers/tty/tty_ldsem.c | 10 ++ drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c | 2 fs/block_dev.c | 28 +++++--- fs/btrfs/disk-io.c | 8 ++ fs/f2fs/recovery.c | 31 --------- fs/proc/array.c | 3 mm/memory.c | 22 ++++++ net/bridge/br_netfilter_hooks.c | 2 net/bridge/netfilter/ebtables.c | 6 + net/can/gw.c | 30 +++++++- net/ipv4/ip_sockglue.c | 12 +-- net/ipv6/datagram.c | 11 +-- net/packet/af_packet.c | 4 - net/sctp/ipv6.c | 5 - net/sctp/protocol.c | 4 - net/sunrpc/rpcb_clnt.c | 8 ++ net/tipc/netlink_compat.c | 50 ++++++++++++++ security/security.c | 7 ++ security/selinux/ss/policydb.c | 3 security/yama/yama_lsm.c | 4 - 45 files changed, 368 insertions(+), 200 deletions(-) Ard Biesheuvel (1): arm64: kaslr: ensure randomized quantities are clean to the PoC Arnd Bergmann (1): mips: fix n32 compat_ipc_parse_version Aymen Sghaier (1): crypto: caam - fix zero-length buffer DMA mapping Ben Hutchings (1): media: em28xx: Fix misplaced reset of dev->v4l::field_count Chao Yu (1): Revert "f2fs: do not recover from previous remained wrong dnodes" Christophe Leroy (2): crypto: talitos - reorder code in talitos_edesc_alloc() crypto: talitos - fix ablkcipher for CONFIG_VMAP_STACK Dmitry Safonov (4): tty/ldsem: Wake up readers after timed out down_write() tty: Hold tty_ldisc_lock() during tty_reopen() tty: Simplify tty->count math in tty_reopen() tty: Don't hold ldisc lock in tty_reopen() if ldisc present Eric Biggers (1): crypto: authenc - fix parsing key with misaligned rta_len Eric Dumazet (1): ipv6: fix kernel-infoleak in ipv6_local_error() Greg Kroah-Hartman (1): Linux 4.9.152 Guenter Roeck (1): proc: Remove empty line in /proc/self/status Hans Verkuil (3): media: vivid: fix error handling of kthread_run media: vivid: set min width/height to a value > 0 media: vb2: vb2_mmap: move lock up Harsh Jain (1): crypto: authencesn - Avoid twice completion call in decrypt path Ivan Mironov (2): scsi: sd: Fix cache_type_store() drm/fb-helper: Ignore the value of fb_var_screeninfo.pixclock J. Bruce Fields (1): sunrpc: handle ENOMEM in rpcb_getport_async James Morris (1): LSM: Check for NULL cred-security on free Jan Kara (4): blockdev: Fix livelocks on loop device loop: Fold __loop_release into loop_release loop: Get rid of loop_index_mutex nbd: Use set_blocksize() to set device blocksize Jason Gunthorpe (1): packet: Do not leak dev refcounts on error exit JianJhen Chen (1): net: bridge: fix a bug on using a neighbour cache entry without checking its state Jonathan Hunter (1): mfd: tps6586x: Handle interrupts on suspend Josef Bacik (2): btrfs: wait on ordered extents on abort cleanup nbd: set the logical and physical blocksize properly Kees Cook (1): Yama: Check for pid death before checking ancestry Mark Rutland (2): arm64/kvm: consistently handle host HCR_EL2 flags arm64: Don't trap host pointer auth use to EL2 Mauro Carvalho Chehab (1): media: vb2: be sure to unlock mutex on errors Michal Hocko (1): mm, memcg: fix reclaim deadlock with writeback Oliver Hartkopp (1): can: gw: ensure DLC boundaries after CAN frame modification Sasha Levin (1): Revert "scsi: target: iscsi: cxgbit: fix csk leak" Shakeel Butt (1): netfilter: ebtables: account ebt_table_info to kmemcg Stanley Chu (1): scsi: core: Synchronize request queue PM status only on successful resume Stephen Smalley (1): selinux: fix GPF on invalid policy Tetsuo Handa (2): block/loop: Use global lock for ioctl() operation. loop: Fix double mutex_unlock(&loop_ctl_mutex) in loop_control_ioctl() Varun Prakash (1): scsi: target: iscsi: cxgbit: fix csk leak Vlad Tsyrklevich (1): omap2fb: Fix stack memory disclosure Willem de Bruijn (2): bonding: update nest level on unlink ip: on queued skb use skb_header_pointer instead of pskb_may_pull Xin Long (1): sctp: allocate sctp_sockaddr_entry with kzalloc Ying Xue (5): tipc: fix uninit-value in tipc_nl_compat_link_reset_stats tipc: fix uninit-value in tipc_nl_compat_bearer_enable tipc: fix uninit-value in tipc_nl_compat_link_set tipc: fix uninit-value in tipc_nl_compat_name_table_dump tipc: fix uninit-value in tipc_nl_compat_doit YunQiang Su (1): Disable MSI also when pcie-octeon.pcie_disable on

5 years, 11 months

1
1
0 0

stable/linux-4.14.y boot: 111 boots: 1 failed, 103 passed with 3 offline, 1 untried/unknown, 3 conflicts (v4.14.95)

by kernelci.org bot

stable/linux-4.14.y boot: 111 boots: 1 failed, 103 passed with 3 offline, 1 untried/unknown, 3 conflicts (v4.14.95) Full Boot Summary: https://kernelci.org/boot/all/job/stable/branch/linux-4.14.y/kernel/v4.14.9… Full Build Summary: https://kernelci.org/build/stable/branch/linux-4.14.y/kernel/v4.14.95/ Tree: stable Branch: linux-4.14.y Git Describe: v4.14.95 Git Commit: 3b68e5cf57f08ad1a9dd7f8ca48ae1326ac98824 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git Tested: 61 unique boards, 23 SoC families, 11 builds out of 197 Boot Regressions Detected: arm: multi_v7_defconfig: tegra124-jetson-tk1: lab-baylibre: new failure (last pass: v4.14.94) arm64: defconfig: meson-gxl-s905x-khadas-vim: lab-baylibre-seattle: new failure (last pass: v4.14.94) Boot Failure Detected: arm64: defconfig rk3399-firefly: 1 failed lab Offline Platforms: arm: multi_v7_defconfig: exynos5800-peach-pi: 1 offline lab davinci_all_defconfig: dm365evm,legacy: 1 offline lab exynos_defconfig: exynos5800-peach-pi: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm64: defconfig: meson-gxl-s905x-khadas-vim: lab-baylibre: PASS lab-baylibre-seattle: FAIL meson-gxl-s905x-libretech-cc: lab-baylibre: PASS lab-baylibre-seattle: FAIL arm: multi_v7_defconfig: tegra124-jetson-tk1: lab-baylibre: FAIL lab-baylibre-seattle: PASS lab-mhart: PASS lab-collabora: PASS --- For more info write to <info(a)kernelci.org>

5 years, 11 months

1
0
0 0

stable-rc/linux-4.19.y boot: 114 boots: 0 failed, 110 passed with 3 offline, 1 conflict (v4.19.17)

by kernelci.org bot

stable-rc/linux-4.19.y boot: 114 boots: 0 failed, 110 passed with 3 offline, 1 conflict (v4.19.17) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.1… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.19.y/kernel/v4.19.17/ Tree: stable-rc Branch: linux-4.19.y Git Describe: v4.19.17 Git Commit: 23b6b8bf9011dc714e7c66ada789c665261607ac Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 63 unique boards, 23 SoC families, 12 builds out of 202 Boot Regressions Detected: arm64: defconfig: meson-gxl-s905x-khadas-vim: lab-baylibre-seattle: failing since 1 day (last pass: v4.19.16 - first fail: v4.19.16-100-ge43bc298813d) Offline Platforms: arm: multi_v7_defconfig: exynos5800-peach-pi: 1 offline lab davinci_all_defconfig: dm365evm,legacy: 1 offline lab exynos_defconfig: exynos5800-peach-pi: 1 offline lab Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm64: defconfig: meson-gxl-s905x-khadas-vim: lab-baylibre: PASS lab-baylibre-seattle: FAIL --- For more info write to <info(a)kernelci.org>

5 years, 11 months

1
0
0 0

stable/linux-4.9.y boot: 98 boots: 0 failed, 95 passed with 2 offline, 1 conflict (v4.9.152)

by kernelci.org bot

stable/linux-4.9.y boot: 98 boots: 0 failed, 95 passed with 2 offline, 1 conflict (v4.9.152) Full Boot Summary: https://kernelci.org/boot/all/job/stable/branch/linux-4.9.y/kernel/v4.9.152/ Full Build Summary: https://kernelci.org/build/stable/branch/linux-4.9.y/kernel/v4.9.152/ Tree: stable Branch: linux-4.9.y Git Describe: v4.9.152 Git Commit: ef50e3059ac91e7b035bce1a89e5b49771ed353a Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git Tested: 48 unique boards, 21 SoC families, 13 builds out of 193 Boot Regressions Detected: arm: tegra_defconfig: tegra124-jetson-tk1: lab-baylibre: new failure (last pass: v4.9.151) Offline Platforms: arm: multi_v7_defconfig: exynos5800-peach-pi: 1 offline lab exynos_defconfig: exynos5800-peach-pi: 1 offline lab Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: tegra_defconfig: tegra124-jetson-tk1: lab-baylibre: FAIL lab-baylibre-seattle: PASS lab-mhart: PASS lab-collabora: PASS --- For more info write to <info(a)kernelci.org>

5 years, 11 months

1
0
0 0

[PATCH 4.14 00/59] 4.14.95-stable review

by Greg Kroah-Hartman

This is the start of the stable review cycle for the 4.14.95 release. There are 59 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 Jan 23 12:23:55 UTC 2019. Anything received after that time might be too late. The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.95-rc… 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 <gregkh(a)linuxfoundation.org> Linux 4.14.95-rc1 Ivan Mironov <mironov.ivan(a)gmail.com> drm/fb-helper: Ignore the value of fb_var_screeninfo.pixclock Jaegeuk Kim <jaegeuk(a)kernel.org> loop: drop caches if offset or block_size are changed Tetsuo Handa <penguin-kernel(a)I-love.SAKURA.ne.jp> loop: Fix double mutex_unlock(&loop_ctl_mutex) in loop_control_ioctl() Jan Kara <jack(a)suse.cz> loop: Get rid of loop_index_mutex Jan Kara <jack(a)suse.cz> loop: Fold __loop_release into loop_release Tetsuo Handa <penguin-kernel(a)I-love.SAKURA.ne.jp> block/loop: Use global lock for ioctl() operation. Tetsuo Handa <penguin-kernel(a)I-love.SAKURA.ne.jp> block/loop: Don't grab "struct file" for vfs_getattr() operation. Ying Xue <ying.xue(a)windriver.com> tipc: fix uninit-value in tipc_nl_compat_doit Ying Xue <ying.xue(a)windriver.com> tipc: fix uninit-value in tipc_nl_compat_name_table_dump Ying Xue <ying.xue(a)windriver.com> tipc: fix uninit-value in tipc_nl_compat_link_set Ying Xue <ying.xue(a)windriver.com> tipc: fix uninit-value in tipc_nl_compat_bearer_enable Ying Xue <ying.xue(a)windriver.com> tipc: fix uninit-value in tipc_nl_compat_link_reset_stats Xin Long <lucien.xin(a)gmail.com> sctp: allocate sctp_sockaddr_entry with kzalloc Jan Kara <jack(a)suse.cz> blockdev: Fix livelocks on loop device Stephen Smalley <sds(a)tycho.nsa.gov> selinux: fix GPF on invalid policy Shakeel Butt <shakeelb(a)google.com> netfilter: ebtables: account ebt_table_info to kmemcg J. Bruce Fields <bfields(a)redhat.com> sunrpc: handle ENOMEM in rpcb_getport_async Hans Verkuil <hverkuil(a)xs4all.nl> media: vb2: vb2_mmap: move lock up James Morris <james.morris(a)microsoft.com> LSM: Check for NULL cred-security on free Willem de Bruijn <willemb(a)google.com> bpf: in __bpf_redirect_no_mac pull mac only if present Hans Verkuil <hverkuil-cisco(a)xs4all.nl> media: vivid: set min width/height to a value > 0 Hans Verkuil <hverkuil-cisco(a)xs4all.nl> media: vivid: fix error handling of kthread_run Vlad Tsyrklevich <vlad(a)tsyrklevich.net> omap2fb: Fix stack memory disclosure YunQiang Su <ysu(a)wavecomp.com> Disable MSI also when pcie-octeon.pcie_disable on Ard Biesheuvel <ard.biesheuvel(a)linaro.org> arm64: kaslr: ensure randomized quantities are clean to the PoC Kees Cook <keescook(a)chromium.org> pstore/ram: Avoid allocation and leak of platform data Sakari Ailus <sakari.ailus(a)linux.intel.com> media: v4l: ioctl: Validate num_planes for debug messages Jonathan Hunter <jonathanh(a)nvidia.com> mfd: tps6586x: Handle interrupts on suspend Julia Lawall <Julia.Lawall(a)lip6.fr> OF: properties: add missing of_node_put Hauke Mehrtens <hauke(a)hauke-m.de> MIPS: lantiq: Fix IPI interrupt handling Arnd Bergmann <arnd(a)arndb.de> mips: fix n32 compat_ipc_parse_version Christophe Leroy <christophe.leroy(a)c-s.fr> crypto: talitos - fix ablkcipher for CONFIG_VMAP_STACK Christophe Leroy <christophe.leroy(a)c-s.fr> crypto: talitos - reorder code in talitos_edesc_alloc() Ivan Mironov <mironov.ivan(a)gmail.com> scsi: sd: Fix cache_type_store() Stanley Chu <stanley.chu(a)mediatek.com> scsi: core: Synchronize request queue PM status only on successful resume Kees Cook <keescook(a)chromium.org> Yama: Check for pid death before checking ancestry Josef Bacik <josef(a)toxicpanda.com> btrfs: wait on ordered extents on abort cleanup David Sterba <dsterba(a)suse.com> Revert "btrfs: balance dirty metadata pages in btrfs_finish_ordered_io" Eric Biggers <ebiggers(a)google.com> crypto: authenc - fix parsing key with misaligned rta_len Eric Biggers <ebiggers(a)google.com> crypto: bcm - convert to use crypto_authenc_extractkeys() Harsh Jain <harsh(a)chelsio.com> crypto: authencesn - Avoid twice completion call in decrypt path Aymen Sghaier <aymen.sghaier(a)nxp.com> crypto: caam - fix zero-length buffer DMA mapping Willem de Bruijn <willemb(a)google.com> ip: on queued skb use skb_header_pointer instead of pskb_may_pull Willem de Bruijn <willemb(a)google.com> bonding: update nest level on unlink Jason Gunthorpe <jgg(a)mellanox.com> packet: Do not leak dev refcounts on error exit JianJhen Chen <kchen(a)synology.com> net: bridge: fix a bug on using a neighbour cache entry without checking its state Eric Dumazet <edumazet(a)google.com> ipv6: fix kernel-infoleak in ipv6_local_error() Mark Rutland <mark.rutland(a)arm.com> arm64: Don't trap host pointer auth use to EL2 Mark Rutland <mark.rutland(a)arm.com> arm64/kvm: consistently handle host HCR_EL2 flags Varun Prakash <varun(a)chelsio.com> scsi: target: iscsi: cxgbit: fix csk leak Sasha Levin <sashal(a)kernel.org> Revert "scsi: target: iscsi: cxgbit: fix csk leak" Xunlei Pang <xlpang(a)linux.alibaba.com> sched/fair: Fix bandwidth timer clock drift condition Ben Hutchings <ben(a)decadent.org.uk> media: em28xx: Fix misplaced reset of dev->v4l::field_count Loic Poulain <loic.poulain(a)linaro.org> mmc: sdhci-msm: Disable CDR function on TX Oliver Hartkopp <socketcan(a)hartkopp.net> can: gw: ensure DLC boundaries after CAN frame modification Dmitry Safonov <dima(a)arista.com> tty: Don't hold ldisc lock in tty_reopen() if ldisc present Dmitry Safonov <dima(a)arista.com> tty: Simplify tty->count math in tty_reopen() Dmitry Safonov <dima(a)arista.com> tty: Hold tty_ldisc_lock() during tty_reopen() Dmitry Safonov <dima(a)arista.com> tty/ldsem: Wake up readers after timed out down_write() ------------- Diffstat: Makefile | 4 +- arch/arm64/include/asm/kvm_arm.h | 3 + arch/arm64/kernel/head.S | 5 +- arch/arm64/kernel/kaslr.c | 8 +- arch/arm64/kvm/hyp/switch.c | 2 +- arch/mips/Kconfig | 1 + arch/mips/lantiq/irq.c | 68 +---------- arch/mips/pci/msi-octeon.c | 4 +- crypto/authenc.c | 14 ++- crypto/authencesn.c | 2 +- drivers/block/loop.c | 140 ++++++++++++++--------- drivers/block/loop.h | 1 - drivers/crypto/Kconfig | 1 + drivers/crypto/bcm/cipher.c | 44 +++---- drivers/crypto/caam/caamhash.c | 15 ++- drivers/crypto/talitos.c | 27 ++--- drivers/gpu/drm/drm_fb_helper.c | 7 +- drivers/media/platform/vivid/vivid-kthread-cap.c | 5 +- drivers/media/platform/vivid/vivid-kthread-out.c | 5 +- drivers/media/platform/vivid/vivid-vid-common.c | 2 +- drivers/media/usb/em28xx/em28xx-video.c | 4 +- drivers/media/v4l2-core/v4l2-ioctl.c | 4 +- drivers/media/v4l2-core/videobuf2-core.c | 11 +- drivers/mfd/tps6586x.c | 24 ++++ drivers/mmc/host/sdhci-msm.c | 51 ++++++++- drivers/net/bonding/bond_main.c | 3 + drivers/of/property.c | 1 + drivers/scsi/scsi_pm.c | 26 +++-- drivers/scsi/sd.c | 6 + drivers/tty/tty_io.c | 22 ++-- drivers/tty/tty_ldsem.c | 10 ++ drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c | 2 + fs/block_dev.c | 28 +++-- fs/btrfs/disk-io.c | 8 ++ fs/btrfs/inode.c | 3 - fs/pstore/ram.c | 9 +- kernel/sched/fair.c | 14 ++- kernel/sched/sched.h | 4 +- net/bridge/br_netfilter_hooks.c | 2 +- net/bridge/netfilter/ebtables.c | 6 +- net/can/gw.c | 30 ++++- net/core/filter.c | 21 ++-- net/core/lwt_bpf.c | 1 + net/ipv4/ip_sockglue.c | 12 +- net/ipv6/datagram.c | 11 +- net/packet/af_packet.c | 4 +- net/sctp/ipv6.c | 5 +- net/sctp/protocol.c | 4 +- net/sunrpc/rpcb_clnt.c | 8 ++ net/tipc/netlink_compat.c | 50 +++++++- security/security.c | 7 ++ security/selinux/ss/policydb.c | 3 +- security/yama/yama_lsm.c | 4 +- 53 files changed, 472 insertions(+), 284 deletions(-)

5 years, 11 months

5
64
0 0

stable-rc/linux-4.14.y boot: 111 boots: 1 failed, 106 passed with 3 offline, 1 conflict (v4.14.95)

by kernelci.org bot

stable-rc/linux-4.14.y boot: 111 boots: 1 failed, 106 passed with 3 offline, 1 conflict (v4.14.95) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.1… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.95/ Tree: stable-rc Branch: linux-4.14.y Git Describe: v4.14.95 Git Commit: 3b68e5cf57f08ad1a9dd7f8ca48ae1326ac98824 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 61 unique boards, 23 SoC families, 11 builds out of 197 Boot Failure Detected: arm64: defconfig rk3399-firefly: 1 failed lab Offline Platforms: arm: multi_v7_defconfig: exynos5800-peach-pi: 1 offline lab davinci_all_defconfig: dm365evm,legacy: 1 offline lab exynos_defconfig: exynos5800-peach-pi: 1 offline lab Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm64: defconfig: meson-gxl-s905x-libretech-cc: lab-baylibre: PASS lab-baylibre-seattle: FAIL --- For more info write to <info(a)kernelci.org>

5 years, 11 months

1
0
0 0

stable-rc/linux-4.20.y boot: 116 boots: 1 failed, 114 passed with 1 conflict (v4.20.4)

by kernelci.org bot

stable-rc/linux-4.20.y boot: 116 boots: 1 failed, 114 passed with 1 conflict (v4.20.4) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.20.y/kernel/v4.2… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.20.y/kernel/v4.20.4/ Tree: stable-rc Branch: linux-4.20.y Git Describe: v4.20.4 Git Commit: 3d4332cd825848da1a40c7116eb777b3269df0ea Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 65 unique boards, 23 SoC families, 13 builds out of 202 Boot Regressions Detected: arm64: defconfig: meson-gxl-s905x-khadas-vim: lab-baylibre-seattle: failing since 1 day (last pass: v4.20.3-112-g2fce01b9fc1e - first fail: v4.20.3-114-g67648eb553fb) Boot Failure Detected: arm64: defconfig mt7622-rfb1: 1 failed lab Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm64: defconfig: meson-gxl-s905x-khadas-vim: lab-baylibre: PASS lab-baylibre-seattle: FAIL --- For more info write to <info(a)kernelci.org>

5 years, 11 months

1
0
0 0

Re: [PATCH v3 01/11] mtd: cfi_cmdset_0002: Change do_write_oneword() to use chip_good()

by Joakim Tjernlund

On Wed, 2019-01-23 at 20:56 +0900, Tokunori Ikegami wrote: > > > Hi Jocke-san, > > Thanks for your advice. > > To make sure let me confirm below. > > The OpenWrt code includes your patch below. > > f69cd2d30a80 2018-05-01 12:58:18 -0700 mtd: cfi: cmdset_0002: Do not allow read/write to suspend erase block. [Joakim Tjernlund] > > Do you mean that it is possible to be needed an additional change more based on this? That patch resolves another problem. I have not sent a patch for problem I mentioned in this mail. > Or is it not related to the patch fixed by you? > Note: Sorry now I am not able to check the patches to try sent by you before. NP Jocke > > > I have lost track of all the details regarding this issue. I just want to > > add: > > > > There is a max number of suspend/resume cycles one can do during an > > erase(possibly also for write) > > and once that number is hit you get an error. One way to avoid this could > > be to > > wait after each resume until the erase has started again(look in status > > register) > > before continuing. > > > > If this has anything to do with this problem, I do not know. > > > > Jocke > > Regards, > Ikegami > > > -----Original Message----- > > From: Joakim Tjernlund [mailto:Joakim.Tjernlund@infinera.com] > > Sent: Wednesday, January 23, 2019 1:58 AM > > To: boris.brezillon(a)bootlin.com; ikegami_to(a)yahoo.co.jp > > Cc: linux-mtd(a)lists.infradead.org; chris.packham(a)alliedtelesis.co.nz; > > fbettoni(a)gmail.com; nbd(a)nbd.name; stable(a)vger.kernel.org; > > hauke(a)hauke-m.de; koen.vandeputte(a)ncentric.com; > > boris.brezillon(a)free-electrons.com > > Subject: Re: [PATCH v3 01/11] mtd: cfi_cmdset_0002: Change > > do_write_oneword() to use chip_good() > > > > On Wed, 2019-01-23 at 00:49 +0900, Tokunori Ikegami wrote: > > > > > > Hi Boris-san, > > > > > > Very sorry for too late to update about this. > > > But could you please let me consult below about this patch? > > > > > > I have tried to investigate the issue root cause and confirmed below but > > > still the root cause seems not clear. > > > > > > 1. Without the change the write oneword is retried and recovered by > > the > > > current existing chip_good() checking. > > > But after the 1,001 times recovery it was continued to fail recovery > > > with the 3 times retry. > > > > I have lost track of all the details regarding this issue. I just want to > > add: > > > > There is a max number of suspend/resume cycles one can do during an > > erase(possibly also for write) > > and once that number is hit you get an error. One way to avoid this could > > be to > > wait after each resume until the erase has started again(look in status > > register) > > before continuing. > > > > If this has anything to do with this problem, I do not know. > > > > Jocke > > > > > 2. By the patch change the recovery failure can be avoided and the write > > > oneword works correctly without any failure. > > > There are different from the original chip_good() checking as the > > > original code resets the chip before the retry. > > > The patch change wait the chip_good() status until the timeout expiry > > > without the chip reset. > > > Note: There is a different from the original OpenWrt patch and > > needed > > > to be changed as same and it will be done by the next v4 patch. > > > > > > 3. To narrow down the cause I have added some delays into the original > > > code to check the chip ready and good status. > > > But the failure behavior was not changed so it seems that the issue > > is > > > not depended to the timing. (But not sure) > > > > > > 4. On the OpenWrt the write buffer is disabled but to narrow down the > > > issue I have changed to enable the write buffer. > > > Then the flash error was not happened by the write buffer operation > > so > > > it seems that the flash driver works correctly. > > > But another issue was caused and it is similar issue with the original > > > OpenWrt behavior with the patch change. > > > Note: On the original OpenWrt needs to wait the file system > > > completion to build but it was not finished with the write buffer. (But > > not > > > sure about this behavior) > > > > > > Do you have any comment about this result? > > > > > > If you can agree about the patch change basically with the current > > situation > > > I will do send the v4 patch set later with fix for the comments. > > > > > > But it seems that it is difficult to investigate the root cause more at > > this > > > moment to me. > > > Since but the behavior looks depended on the flash chip hardware behavior > > > and I cannot debug the hardware behavior more I think. > > > Note: Now I can reproduce the flash error issue behavior on the OpenWrt > > > unit. > > > > > > > > > It is depended on the actual flash chip behavior so the root > > cause > > > > > is > > > > > > unknown. > > > > > > > > > > Yes, and that's what I'd like you to figure out, or at least have > > a > > > > > good idea why this doesn't work on some chips but works on others. > > > > > > > > I see. > > > > But it is a little bit difficult situation since I do not have the failure > > > > environment locally at this moment. > > > > But if needed I may ask to get the help for this to Fabio-san. > > > > > > Regards, > > > Ikegami > > > > > > > -----Original Message----- > > > > From: IKEGAMI Tokunori [mailto:ikegami@allied-telesis.co.jp] > > > > Sent: Tuesday, November 6, 2018 6:47 PM > > > > To: Boris Brezillon; ikegami_to(a)yahoo.co.jp > > > > Cc: boris.brezillon(a)free-electrons.com; Felix Fietkau; Hauke Mehrtens; > > > > stable(a)vger.kernel.org; Joakim Tjernlund; PACKHAM Chris; > > > > linux-mtd(a)lists.infradead.org; Koen Vandeputte; Fabio Bettoni > > > > Subject: RE: [PATCH v3 01/11] mtd: cfi_cmdset_0002: Change > > > > do_write_oneword() to use chip_good() > > > > > > > > Sorry let me resend the mail below by changing the email address of > > > > Felix-san. > > > > > > > > -----Original Message----- > > > > From: IKEGAMI Tokunori > > > > Sent: Tuesday, November 06, 2018 6:37 PM > > > > To: 'Boris Brezillon'; 'ikegami_to(a)yahoo.co.jp' > > > > Cc: boris.brezillon(a)free-electrons.com; Felix Fietkau; Hauke Mehrtens; > > > > stable(a)vger.kernel.org; Joakim Tjernlund; PACKHAM Chris; > > > > linux-mtd(a)lists.infradead.org; Koen Vandeputte; Fabio Bettoni > > > > Subject: RE: [PATCH v3 01/11] mtd: cfi_cmdset_0002: Change > > > > do_write_oneword() to use chip_good() > > > > > > > > Hi Boris-san, > > > > > > > > > -----Original Message----- > > > > > From: stable-owner(a)vger.kernel.org > > > > > [mailto:stable-owner@vger.kernel.org] On Behalf Of Boris Brezillon > > > > > Sent: Tuesday, November 06, 2018 5:34 PM > > > > > To: IKEGAMI Tokunori > > > > > Cc: boris.brezillon(a)free-electrons.com; Felix Fietkau; Hauke > > Mehrtens; > > > > > stable(a)vger.kernel.org; Joakim Tjernlund; PACKHAM Chris; > > > > > linux-mtd(a)lists.infradead.org; Koen Vandeputte; Fabio Bettoni > > > > > Subject: Re: [PATCH v3 01/11] mtd: cfi_cmdset_0002: Change > > > > > do_write_oneword() to use chip_good() > > > > > > > > > > Hi IKEGAMI, > > > > > > > > > > On Tue, 6 Nov 2018 00:25:43 +0000 > > > > > IKEGAMI Tokunori <ikegami(a)allied-telesis.co.jp> wrote: > > > > > > > > > > > > > Also the issue can be fixed by using chip_good() instead of > > > > > chip_ready(). > > > > > > > > The chip_ready() just checks the value from flash memory twice. > > > > > > > > And the chip_good() checks the value with the expected value. > > > > > > > > Probably the issue can be fixed as checked correctly by the > > > > chip_good(). > > > > > > > > So change to use chip_good() instead of chip_ready(). > > > > > > > > > > > > > > Well, that's not really explaining why you think chip_good() should > > > > > be > > > > > > > used instead of chip_ready(). So I went on and looked at the > > > > > > > chip_good(), chip_ready() and do_write_oneword() implementation, > > and > > > > > > > also looked at users of do_write_oneword(). It seems this function > > > > is > > > > > > > used to write data to the flash, and apparently the "one bit should > > > > > > > toggle to reflect a busy state" does not apply when writing things > > > > to > > > > > > > the memory array (it's probably working for other CFI commands, > > but > > > > > I > > > > > > > guess it takes more time to actually change the level of a NOR > > cell, > > > > > > > hence the result of 2 identical reads does not mean that the write > > > > is > > > > > > > done). > > > > > > > > > > > > > > Also, it seems that cmdset_0001 is not implementing chip_ready() > > the > > > > > > > same way, and I wonder if cmdset_0002 implementation is correct > > to > > > > > > > start with. Or maybe I don't get what chip_ready() is for. > > > > > > > > > > > > > > Anyway, this is the sort of clarification I'd like to have. > > > > > > > > > > > > I am thinking to update the commit message as below. > > > > > > > > > > > > mtd: cfi_cmdset_0002: Use chip_good() to retry in > > > > do_write_oneword() > > > > > > As reported by the OpenWRT team, write requests sometimes fail > > on > > > > > some > > > > > > platforms. > > > > > > Currently to check the state chip_ready() is used correctly > > as > > > > > described by > > > > > > the flash memory S29GL256P11TFI01 datasheet. > > > > > > > > > > I had a look at the S29GL256P datasheet here [1], and if I'm correct, > > > > > it's using cmdset 0001. > > > > > > > > No actually the cmdset 0002 is used on the flash chip. > > > > The manufacturer ID xx01h and Device ID 2201h are used to decide. > > > > > > > > There is information from Fobis-san below also about this. > > > > > > > > On forum thread musashino posted picture of flash chip: > > > > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforum > > .openwrt.org%2Ft%2Fimpossible-to-install-update-any-packages-&data > > =02%7C01%7Cjoakim.tjernlund%40infinera.com%7C916af968b27a402da8cf08d68 > > 0812fce%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C1%7C63683768968012655 > > 7&sdata=NNGSYgq1VTuofPPMMlyKIm9W1DJHQFw0s94Ernq5cts%3D&reserve > > d=0 > > > > on-wzr-hp-g300nh-18-06-1 > > > > > > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.cy > > press.com%2Fpart%2Fs29gl256p11tfi010&data=02%7C01%7Cjoakim.tjernlu > > nd%40infinera.com%7C916af968b27a402da8cf08d680812fce%7C285643de5f5b4b0 > > 3a1530ae2dc8aaf77%7C1%7C1%7C636837689680126557&sdata=Twk1VUEESz14U > > pdJjU4ohuhiQ5jN1uHLh0cAhlAznW0%3D&reserved=0 > > > > [ 0.862264] physmap platform flash device: 02000000 at 1e000000 > > > > [ 0.868331] physmap-flash: Found 1 x16 devices at 0x0 in 16-bit > > > > bank. Manufacturer ID 0x000001 Chip ID 0x002201 > > > > [ 0.878493] Amd/Fujitsu Extended Query Table at 0x0040 > > > > [ 0.883668] Amd/Fujitsu Extended Query version 1.3. > > > > [ 0.888768] number of CFI chips: 1 > > > > [ 0.894557] Searching for RedBoot partition table in physmap-flash > > > > at offset 0x1fc0000 > > > > [ 0.918009] Searching for RedBoot partition table in physmap-flash > > > > at offset 0x1fe0000 > > > > [ 0.941464] No RedBoot partition table detected in physmap-flash > > > > [ 0.947926] Creating 5 MTD partitions on "physmap-flash": > > > > [ 0.953384] 0x000000000000-0x000000040000 : "u-boot" > > > > [ 0.960853] 0x000000040000-0x000000060000 : "u-boot-env" > > > > [ 0.968803] 0x000000060000-0x000001fc0000 : "firmware" > > > > [ 0.981859] 2 uimage-fw partitions found on MTD device firmware > > > > [ 0.987900] 0x000000060000-0x0000001b5706 : "kernel" > > > > [ 0.994916] 0x0000001b5706-0x000001fc0000 : "rootfs" > > > > [ 1.001986] mtd: device 4 (rootfs) set to be root filesystem > > > > [ 1.007789] 1 squashfs-split partitions found on MTD device rootfs > > > > [ 1.014014] 0x0000003c0000-0x000001fc0000 : "rootfs_data" > > > > [ 1.022093] 0x000001fc0000-0x000001fe0000 : "user_property" > > > > [ 1.030283] 0x000001fe0000-0x000002000000 : "art" > > > > > > > > Maybe you could post links to forum thread, and data sheet. > > > > > > > > > > Also chip_good() is used to check if the write is succeeded > > and > > > > it > > > > > was > > > > > > implemented by the commit fb4a90bfcd6d8 ("[MTD] CFI-0002 - > > Improve > > > > > error > > > > > > checking"). > > > > > > But actually the write failure is caused on some platforms and > > > also > > > > > it can > > > > > > be fixed by using chip_good() to check the state and retry > > > instead. > > > > > Do you know on which NOR chips this happens? Do you have access to > > the > > > > > datasheet? > > > > > > > > But it looks SST49LF008A [3] from the changes below but I am not sure > > at > > > > this moment and probably it should be confirmed to the authr Eric W. > > > > Biedermann <ebiederman(a)lnxi.com> to make sure. > > > > > > > > +#define SST49LF008A 0x005a > > > > > > > > static int cfi_amdstd_read (struct mtd_info *, loff_t, size_t, size_t > > *, > > > > u_char *); > > > > static int cfi_amdstd_write_words(struct mtd_info *, loff_t, size_t, > > > > size_t *, const u_char *); > > > > @@ -191,6 +192,7 @@ static struct cfi_fixup cfi_fixup_table[] = { > > > > }; > > > > static struct cfi_fixup jedec_fixup_table[] = { > > > > { MANUFACTURER_SST, SST49LF004B, fixup_use_fwh_lock, NULL, }, > > > > + { MANUFACTURER_SST, SST49LF008A, fixup_use_fwh_lock, NULL, }, > > > > > > > > > > It is depended on the actual flash chip behavior so the root > > cause > > > > > is > > > > > > unknown. > > > > > > > > > > Yes, and that's what I'd like you to figure out, or at least have > > a > > > > > good idea why this doesn't work on some chips but works on others. > > > > > > > > I see. > > > > But it is a little bit difficult situation since I do not have the failure > > > > environment locally at this moment. > > > > But if needed I may ask to get the help for this to Fabio-san. > > > > > > > > > > If any comment please let me know. > > > > > > > > > > > > > > Signed-off-by: Tokunori Ikegami <ikegami(a)allied-telesis.co.jp> > > > > > > > > Signed-off-by: Hauke Mehrtens <hauke(a)hauke-m.de> > > > > > > > > Signed-off-by: Koen Vandeputte <koen.vandeputte(a)ncentric.com> > > > > > > > > Signed-off-by: Fabio Bettoni <fbettoni(a)gmail.com> > > > > > > > > > > > > > > Has the patch really gone through all those people? SoB is used > > when > > > > > you > > > > > > > apply a patch in your tree or when you're the original author. > > > > > > > > > > > > I have just checked the OpenWRT git log again and it looks that > > it was > > > > > originally > > > > > > implemented by Felix Fietkau <nbd(a)openwrt.org> by the patch below > > so > > > > I > > > > > will update the Signed-off-by tag as so. > > <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit. > > openwrt.org%2F%3Fp%3Dopenwrt%2Fopenwrt.git%3Ba%3Dcommitdiff%3Bh%3D2530 > > 640&data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7C916af968b27a4 > > 02da8cf08d680812fce%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C1%7C63683 > > 7689680126557&sdata=w13ZTKwD1NiUQzxQfUou92KVDlW80qGUiZVIcjU%2BGPA% > > 3D&reserved=0 > > > > > f07cd2b3b14fe9ec03fa63a586452cc5f> > > > > > > > > Co-Developed-by: Hauke Mehrtens <hauke(a)hauke-m.de> > > > > > > > > Co-Developed-by: Koen Vandeputte <koen.vandeputte(a)ncentric.com> > > > > > > > > Co-Developed-by: Fabio Bettoni <fbettoni(a)gmail.com> > > > > > > > > > > > > > > Not sure we want to add new undocumented tags, but you can mention > > > > > > > that all those people helped you find/debug the issue. They can > > also > > > > > > > add their Reviewed-by/Tested-by if they like. > > > > > > > > > > My bad, I just noticed these are valid flags [2], so you can keep > > them, > > > > > and according to the doc, you should also keep the SoB. > > > > > > > > I see. > > > > Yes I had also checked it. > > > > > > > > By the way in near future my company email address will be not able > > to > > > use. > > > > So I will change the mail address to my personal email address [4] after > > > > that or before. > > > > > > > > Regards, > > > > Ikegami > > > > > > > > > Regards, > > > > > > > > > > Boris > > > > > > > > > > >

5 years, 11 months

1
0
0 0

[PATCH 0/3] PCI: hv: Use vPCI protocol version 1.2 for v4.9

by Ajay Kaher

For now, please consider these patches for review and suggest if these can be merged to mainline kernel v4.9. These patches add support for vPCI protocol version 1.2, by backpotring from v4.14 to v4.9. Individual patches are summarised below: Patch 1: PCI: hv: Allocate physically contiguous hypercall params buffer Backported as is. Patch 2: PCI: hv: Add vPCI version protocol negotiation Backported as is. Patch 3: PCI: hv: Use vPCI protocol version 1.2 for v4.9 Change: Because v4.9 doesn't have hv_tmp_cpu_nr_to_vp_nr(), so original patch from v4.14 fails to apply on v4.9. To solve this, using vmbus_cpu_number_to_vp_number() instead of hv_tmp_cpu_nr_to_vp_nr() in this patch. drivers/pci/host/pci-hyperv.c | 387 +++++++++++++++++++++++++++++++++--------- 1 file changed, 311 insertions(+), 76 deletions(-) -- 2.7.4

5 years, 11 months

3
8
0 0

stable-rc/linux-4.9.y boot: 98 boots: 0 failed, 98 passed (v4.9.152)

by kernelci.org bot

stable-rc/linux-4.9.y boot: 98 boots: 0 failed, 98 passed (v4.9.152) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.152/ Tree: stable-rc Branch: linux-4.9.y Git Describe: v4.9.152 Git Commit: ef50e3059ac91e7b035bce1a89e5b49771ed353a Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 48 unique boards, 21 SoC families, 13 builds out of 193 --- For more info write to <info(a)kernelci.org>

5 years, 11 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror January 2019