April 2020 - Linux-stable-mirror

Re: [PATCH v2 1/1] NFSv4.1: fix handling of backchannel binding in BIND_CONN_TO_SESSION

by Sasha Levin

Hi [This is an automated email] This commit has been processed because it contains a -stable tag. The stable tag indicates that it's relevant for the following trees: all The bot has tested the following trees: v5.6.7, v5.4.35, v4.19.118, v4.14.177, v4.9.220, v4.4.220. v5.6.7: Build OK! v5.4.35: Failed to apply! Possible dependencies: Unable to calculate v4.19.118: Failed to apply! Possible dependencies: 07d02a67b7fa ("SUNRPC: Simplify lookup code") 3453d5708b33 ("NFSv4.1: Avoid false retries when RPC calls are interrupted") 5c441544f045 ("NFSv4.x: Handle bad/dead sessions correctly in nfs41_sequence_process()") 79b181810285 ("SUNRPC: Convert auth creds to use refcount_t") 8276c902bbe9 ("SUNRPC: remove uid and gid from struct auth_cred") 95cd623250ad ("SUNRPC: Clean up the AUTH cache code") 97f68c6b02e0 ("SUNRPC: add 'struct cred *' to auth_cred and rpc_cred") a52458b48af1 ("NFS/NFSD/SUNRPC: replace generic creds with 'struct cred'.") fc0664fd9bcc ("SUNRPC: remove groupinfo from struct auth_cred.") v4.14.177: Failed to apply! Possible dependencies: 07d02a67b7fa ("SUNRPC: Simplify lookup code") 12f275cdd163 ("NFSv4: Retry CLOSE and DELEGRETURN on NFS4ERR_OLD_STATEID.") 1eb5d98f16f6 ("nfs: convert to new i_version API") 3453d5708b33 ("NFSv4.1: Avoid false retries when RPC calls are interrupted") 35156bfff3c0 ("NFSv4: Fix the nfs_inode_set_delegation() arguments") 5c441544f045 ("NFSv4.x: Handle bad/dead sessions correctly in nfs41_sequence_process()") 79b181810285 ("SUNRPC: Convert auth creds to use refcount_t") 95cd623250ad ("SUNRPC: Clean up the AUTH cache code") 97f68c6b02e0 ("SUNRPC: add 'struct cred *' to auth_cred and rpc_cred") a52458b48af1 ("NFS/NFSD/SUNRPC: replace generic creds with 'struct cred'.") b3dce6a2f060 ("pnfs/blocklayout: handle transient devices") fc0664fd9bcc ("SUNRPC: remove groupinfo from struct auth_cred.") v4.9.220: Failed to apply! Possible dependencies: 172d9de15a0d ("NFS: Change nfs4_get_session() to take an nfs_client structure") 3453d5708b33 ("NFSv4.1: Avoid false retries when RPC calls are interrupted") 3be0f80b5fe9 ("NFSv4.1: Fix up replays of interrupted requests") 42e1cca7e91e ("NFS: Change nfs4_setup_sequence() to take an nfs_client structure") 5c441544f045 ("NFSv4.x: Handle bad/dead sessions correctly in nfs41_sequence_process()") 6de7e12f53a1 ("NFS: Use nfs4_setup_sequence() everywhere") 7981c8a65914 ("NFS: Create a single nfs4_setup_sequence() function") efc6f4aa742d ("NFS: Move nfs4_get_session() into nfs4_session.h") v4.4.220: Failed to apply! Possible dependencies: 172d9de15a0d ("NFS: Change nfs4_get_session() to take an nfs_client structure") 3453d5708b33 ("NFSv4.1: Avoid false retries when RPC calls are interrupted") 3be0f80b5fe9 ("NFSv4.1: Fix up replays of interrupted requests") 42e1cca7e91e ("NFS: Change nfs4_setup_sequence() to take an nfs_client structure") 5c441544f045 ("NFSv4.x: Handle bad/dead sessions correctly in nfs41_sequence_process()") 5f83d86cf531 ("NFSv4.x: Fix wraparound issues when validing the callback sequence id") 68d264cf02b0 ("NFS42: handle layoutstats stateid error") 6de7e12f53a1 ("NFS: Use nfs4_setup_sequence() everywhere") 80f9642724af ("NFSv4.x: Enforce the ca_maxresponsesize_cached on the back channel") 810d82e68301 ("NFSv4.x: Allow multiple callbacks in flight") 9a0fe86745b8 ("pNFS: Handle NFS4ERR_OLD_STATEID correctly in LAYOUTSTAT calls") efc6f4aa742d ("NFS: Move nfs4_get_session() into nfs4_session.h") f74a834a0e1b ("NFSv4.x: CB_SEQUENCE should return NFS4ERR_DELAY if still executing") NOTE: The patch will not be queued to stable trees until it is upstream. How should we proceed with this patch? -- Thanks Sasha

4 years, 8 months

2
2
0 0

Re: [PATCH v5.7] iwlwifi: pcie: handle QuZ configs with killer NICs as well

by Sasha Levin

Hi [This is an automated email] This commit has been processed because it contains a "Fixes:" tag fixing commit: 5a8c31aa6357 ("iwlwifi: pcie: fix recognition of QuZ devices"). The bot has tested the following trees: v5.6.7, v5.4.35. v5.6.7: Failed to apply! Possible dependencies: 32ed101aa140 ("iwlwifi: convert all Qu with Jf devices to the new config table") 56ba371a5288 ("iwlwifi: move the remaining 0x2526 configs to the new table") 5e003982b07a ("iwlwifi: move AX200 devices to the new table") 67eb556da609 ("iwlwifi: combine 9260 cfgs that only change names") 95939551e28c ("iwlwifi: add GNSS differentiation to the device tables") d6f2134a3831 ("iwlwifi: add mac/rf types and 160MHz to the device tables") fe25b1518f72 ("iwlwifi: move TH1 devices to the new table") v5.4.35: Failed to apply! Possible dependencies: 32ed101aa140 ("iwlwifi: convert all Qu with Jf devices to the new config table") 3681021fc6af ("iwlwifi: remove IWL_DEVICE_22560/IWL_DEVICE_FAMILY_22560") 3b589d5624ce ("iwlwifi: dbg_ini: use new trigger TLV in dump flow") 593fae3e5e90 ("iwlwifi: dbg_ini: add monitor dumping support") 69f0e5059b09 ("iwlwifi: dbg: remove multi buffers infra") bfc3e9fdbfb8 ("iwlwifi: 22000: fix some indentation") c042f0c77f3d ("iwlwifi: allocate more receive buffers for HE devices") c9fe75e9f347 ("iwlwifi: dbg_ini: use new region TLV in dump flow") NOTE: The patch will not be queued to stable trees until it is upstream. How should we proceed with this patch? -- Thanks Sasha

4 years, 8 months

1
0
0 0

[PATCH] propogate_mnt: Handle the first propogated copy being a slave

by TuQuan

commit 5ec0811d30378ae104f250bfc9b3640242d81e3f upstream When the first propgated copy was a slave the following oops would result: > BUG: unable to handle kernel NULL pointer dereference at > 0000000000000010 > IP: [<ffffffff811fba4e>] propagate_one+0xbe/0x1c0 > PGD bacd4067 PUD bac66067 PMD 0 > Oops: 0000 [#1] SMP > Modules linked in: > CPU: 1 PID: 824 Comm: mount Not tainted 4.6.0-rc5userns+ #1523 > Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007 > task: ffff8800bb0a8000 ti: ffff8800bac3c000 task.ti: ffff8800bac3c000 > RIP: 0010:[<ffffffff811fba4e>] [<ffffffff811fba4e>] > propagate_one+0xbe/0x1c0 > RSP: 0018:ffff8800bac3fd38 EFLAGS: 00010283 > RAX: 0000000000000000 RBX: ffff8800bb77ec00 RCX: 0000000000000010 > RDX: 0000000000000000 RSI: ffff8800bb58c000 RDI: ffff8800bb58c480 > RBP: ffff8800bac3fd48 R08: 0000000000000001 R09: 0000000000000000 > R10: 0000000000001ca1 R11: 0000000000001c9d R12: 0000000000000000 > R13: ffff8800ba713800 R14: ffff8800bac3fda0 R15: ffff8800bb77ec00 > FS: 00007f3c0cd9b7e0(0000) GS:ffff8800bfb00000(0000) > knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 0000000000000010 CR3: 00000000bb79d000 CR4: 00000000000006e0 > Stack: > ffff8800bb77ec00 0000000000000000 ffff8800bac3fd88 ffffffff811fbf85 > ffff8800bac3fd98 ffff8800bb77f080 ffff8800ba713800 ffff8800bb262b40 > 0000000000000000 0000000000000000 ffff8800bac3fdd8 ffffffff811f1da0 > Call Trace: > [<ffffffff811fbf85>] propagate_mnt+0x105/0x140 > [<ffffffff811f1da0>] attach_recursive_mnt+0x120/0x1e0 > [<ffffffff811f1ec3>] graft_tree+0x63/0x70 > [<ffffffff811f1f6b>] do_add_mount+0x9b/0x100 > [<ffffffff811f2c1a>] do_mount+0x2aa/0xdf0 > [<ffffffff8117efbe>] ? strndup_user+0x4e/0x70 > [<ffffffff811f3a45>] SyS_mount+0x75/0xc0 > [<ffffffff8100242b>] do_syscall_64+0x4b/0xa0 > [<ffffffff81988f3c>] entry_SYSCALL64_slow_path+0x25/0x25 > Code: 00 00 75 ec 48 89 0d 02 22 22 01 8b 89 10 01 00 00 48 89 05 fd > 21 22 01 39 8e 10 01 00 00 0f 84 e0 00 00 00 48 8b 80 d8 00 00 00 <48> > 8b 50 10 48 89 05 df 21 22 01 48 89 15 d0 21 22 01 8b 53 30 > RIP [<ffffffff811fba4e>] propagate_one+0xbe/0x1c0 > RSP <ffff8800bac3fd38> > CR2: 0000000000000010 > ---[ end trace 2725ecd95164f217 ]--- This oops happens with the namespace_sem held and can be triggered by non-root users. An all around not pleasant experience. To avoid this scenario when finding the appropriate source mount to copy stop the walk up the mnt_master chain when the first source mount is encountered. Further rewrite the walk up the last_source mnt_master chain so that it is clear what is going on. The reason why the first source mount is special is that it it's mnt_parent is not a mount in the dest_mnt propagation tree, and as such termination conditions based up on the dest_mnt mount propgation tree do not make sense. To avoid other kinds of confusion last_dest is not changed when computing last_source. last_dest is only used once in propagate_one and that is above the point of the code being modified, so changing the global variable is meaningless and confusing. Cc: stable(a)vger.kernel.org fixes: f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68 ("smarter propagate_mnt()") Reported-by: Tycho Andersen <tycho.andersen(a)canonical.com> Reviewed-by: Seth Forshee <seth.forshee(a)canonical.com> Tested-by: Seth Forshee <seth.forshee(a)canonical.com> Signed-off-by: "Eric W. Biederman" <ebiederm(a)xmission.com> --- 7u/fs/pnode.c | 32 ++++++++++++++++++++------------ 1 file changed, 20 insertions(+), 12 deletions(-) diff --git a/7u/fs/pnode.c b/7u/fs/pnode.c index 30d9a548d..52c262e71 100644 --- a/7u/fs/pnode.c +++ b/7u/fs/pnode.c @@ -198,10 +198,15 @@ static struct mount *next_group(struct mount *m, struct mount *origin) /* all accesses are serialized by namespace_sem */ static struct user_namespace *user_ns; -static struct mount *last_dest, *last_source, *dest_master; +static struct mount *last_dest, *first_source, *last_source, *dest_master; static struct mountpoint *mp; static struct list_head *list; +static inline bool peers(struct mount *m1, struct mount *m2) +{ + return m1->mnt_group_id == m2->mnt_group_id && m1->mnt_group_id; +} + static int propagate_one(struct mount *m) { struct mount *child; @@ -212,24 +217,26 @@ static int propagate_one(struct mount *m) /* skip if mountpoint isn't covered by it */ if (!is_subdir(mp->m_dentry, m->mnt.mnt_root)) return 0; - if (m->mnt_group_id == last_dest->mnt_group_id) { + if (peers(m, last_dest)) { type = CL_MAKE_SHARED; } else { struct mount *n, *p; + bool done; for (n = m; ; n = p) { p = n->mnt_master; - if (p == dest_master || IS_MNT_MARKED(p)) { - while (last_dest->mnt_master != p) { - last_source = last_source->mnt_master; - last_dest = last_source->mnt_parent; - } - if (n->mnt_group_id != last_dest->mnt_group_id) { - last_source = last_source->mnt_master; - last_dest = last_source->mnt_parent; - } + if (p == dest_master || IS_MNT_MARKED(p)) break; - } } + do { + struct mount *parent = last_source->mnt_parent; + if (last_source == first_source) + break; + done = parent->mnt_master == p; + if (done && peers(n, parent)) + break; + last_source = last_source->mnt_master; + } while (!done); + type = CL_SLAVE; /* beginning of peer group among the slaves? */ if (IS_MNT_SHARED(m)) @@ -280,6 +287,7 @@ int propagate_mnt(struct mount *dest_mnt, struct mountpoint *dest_mp, */ user_ns = current->nsproxy->mnt_ns->user_ns; last_dest = dest_mnt; + first_source = source_mnt; last_source = source_mnt; mp = dest_mp; list = tree_list; -- 2.14.4.44.g2045bb6

4 years, 8 months

1
0
0 0

[4.19-stable] Security fixes

by Ben Hutchings

Here are some fixes that required backporting for 4.19. All of them are already present in later stable branches. Ben. -- Ben Hutchings, Software Developer Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street Manchester, M1 2HF, United Kingdom

4 years, 8 months

2
1
0 0

stable-rc/linux-4.19.y boot: 149 boots: 1 failed, 135 passed with 7 offline, 5 untried/unknown, 1 conflict (v4.19.118)

by kernelci.org bot

stable-rc/linux-4.19.y boot: 149 boots: 1 failed, 135 passed with 7 offline, 5 untried/unknown, 1 conflict (v4.19.118) 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.118/ Tree: stable-rc Branch: linux-4.19.y Git Describe: v4.19.118 Git Commit: 7edd66cf61670d2d0c31f89cb3a247016e489a8a Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 86 unique boards, 22 SoC families, 20 builds out of 206 Boot Regressions Detected: arm: davinci_all_defconfig: gcc-8: da850-evm: lab-baylibre-seattle: failing since 2 days (last pass: v4.19.117-18-gff69db5bee37 - first fail: v4.19.117-65-gb5f03cd61ab6) dm365evm,legacy: lab-baylibre-seattle: failing since 2 days (last pass: v4.19.117-18-gff69db5bee37 - first fail: v4.19.117-65-gb5f03cd61ab6) qcom_defconfig: gcc-8: qcom-apq8064-cm-qs600: lab-baylibre-seattle: failing since 77 days (last pass: v4.19.101 - first fail: v4.19.102-96-g0632821fe218) sama5_defconfig: gcc-8: at91-sama5d4_xplained: lab-baylibre: failing since 43 days (last pass: v4.19.108-87-g624c124960e8 - first fail: v4.19.109) arm64: defconfig: gcc-8: meson-axg-s400: lab-baylibre-seattle: new failure (last pass: v4.19.117-65-gb5f03cd61ab6) x86_64: x86_64_defconfig: gcc-8: qemu_x86_64: lab-collabora: failing since 3 days (last pass: v4.19.117 - first fail: v4.19.117-18-gff69db5bee37) Boot Failure Detected: arm: sama5_defconfig: gcc-8: at91-sama5d4_xplained: 1 failed lab Offline Platforms: arm64: defconfig: gcc-8 meson-axg-s400: 1 offline lab arm: multi_v7_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab qcom-apq8064-cm-qs600: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab davinci_all_defconfig: gcc-8 da850-evm: 1 offline lab dm365evm,legacy: 1 offline lab exynos_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) x86_64: x86_64_defconfig: qemu_x86_64: lab-baylibre: PASS (gcc-8) lab-collabora: FAIL (gcc-8) --- For more info write to <info(a)kernelci.org>

4 years, 8 months

1
0
0 0

stable-rc/linux-4.14.y boot: 133 boots: 3 failed, 118 passed with 6 offline, 5 untried/unknown, 1 conflict (v4.14.177)

by kernelci.org bot

stable-rc/linux-4.14.y boot: 133 boots: 3 failed, 118 passed with 6 offline, 5 untried/unknown, 1 conflict (v4.14.177) 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.177/ Tree: stable-rc Branch: linux-4.14.y Git Describe: v4.14.177 Git Commit: 050272a0423e68207fd2367831ae610680129062 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 75 unique boards, 20 SoC families, 18 builds out of 201 Boot Regressions Detected: arm: davinci_all_defconfig: gcc-8: da850-evm: lab-baylibre-seattle: new failure (last pass: v4.14.176-199-ga7097ef0ff82) dm365evm,legacy: lab-baylibre-seattle: new failure (last pass: v4.14.176-199-ga7097ef0ff82) qcom_defconfig: gcc-8: qcom-apq8064-cm-qs600: lab-baylibre-seattle: failing since 77 days (last pass: v4.14.169-92-gb4137330c582 - first fail: v4.14.170-62-gd6856e4a2c23) sama5_defconfig: gcc-8: at91-sama5d4_xplained: lab-baylibre: failing since 65 days (last pass: v4.14.170-141-g00a0113414f7 - first fail: v4.14.171-29-g9cfe30e85240) Boot Failures Detected: arm64: defconfig: gcc-8: meson-gxbb-p200: 1 failed lab meson-gxm-q200: 1 failed lab arm: sama5_defconfig: gcc-8: at91-sama5d4_xplained: 1 failed lab Offline Platforms: arm: multi_v7_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab qcom-apq8064-cm-qs600: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab davinci_all_defconfig: gcc-8 da850-evm: 1 offline lab dm365evm,legacy: 1 offline lab exynos_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) i386: i386_defconfig: qemu_i386: lab-baylibre: PASS (gcc-8) lab-collabora: FAIL (gcc-8) --- For more info write to <info(a)kernelci.org>

4 years, 8 months

1
0
0 0

stable-rc/linux-5.4.y boot: 171 boots: 1 failed, 156 passed with 7 offline, 7 untried/unknown (v5.4.35)

by kernelci.org bot

stable-rc/linux-5.4.y boot: 171 boots: 1 failed, 156 passed with 7 offline, 7 untried/unknown (v5.4.35) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.4.y/kernel/v5.4.… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.4.y/kernel/v5.4.35/ Tree: stable-rc Branch: linux-5.4.y Git Describe: v5.4.35 Git Commit: 0c418786cb3aa175823f0172d939679df9ab9a54 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 105 unique boards, 26 SoC families, 22 builds out of 200 Boot Regressions Detected: arm: davinci_all_defconfig: gcc-8: da850-evm: lab-baylibre-seattle: failing since 2 days (last pass: v5.4.34-32-g913df976b290 - first fail: v5.4.34-119-g186764443bf3) dm365evm,legacy: lab-baylibre-seattle: failing since 2 days (last pass: v5.4.34-32-g913df976b290 - first fail: v5.4.34-119-g186764443bf3) qcom_defconfig: gcc-8: qcom-apq8064-cm-qs600: lab-baylibre-seattle: failing since 77 days (last pass: v5.4.17-99-gbd0c6624a110 - first fail: v5.4.17-238-gbffcaa93483d) sama5_defconfig: gcc-8: at91-sama5d4_xplained: lab-baylibre: failing since 17 days (last pass: v5.4.30-37-g40da5db79b55 - first fail: v5.4.30-39-g23c04177b89f) arm64: defconfig: gcc-8: meson-axg-s400: lab-baylibre-seattle: new failure (last pass: v5.4.34-119-g186764443bf3) meson-gxl-s805x-libretech-ac: lab-baylibre: new failure (last pass: v5.4.33-61-gf969422316c7) Boot Failure Detected: arm: sama5_defconfig: gcc-8: at91-sama5d4_xplained: 1 failed lab Offline Platforms: arm64: defconfig: gcc-8 meson-axg-s400: 1 offline lab arm: multi_v7_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab qcom-apq8064-cm-qs600: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab davinci_all_defconfig: gcc-8 da850-evm: 1 offline lab dm365evm,legacy: 1 offline lab exynos_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab --- For more info write to <info(a)kernelci.org>

4 years, 8 months

1
0
0 0

stable-rc/linux-4.4.y boot: 91 boots: 3 failed, 77 passed with 6 offline, 4 untried/unknown, 1 conflict (v4.4.220)

by kernelci.org bot

stable-rc/linux-4.4.y boot: 91 boots: 3 failed, 77 passed with 6 offline, 4 untried/unknown, 1 conflict (v4.4.220) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.220/ Tree: stable-rc Branch: linux-4.4.y Git Describe: v4.4.220 Git Commit: 5efe91c00c98c72cbe8475caa6e72c520199e32b Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 49 unique boards, 18 SoC families, 17 builds out of 190 Boot Regressions Detected: arm: davinci_all_defconfig: gcc-8: da850-evm: lab-baylibre-seattle: failing since 2 days (last pass: v4.4.219-83-g20fbd20eb91a - first fail: v4.4.219-101-gacb152478366) dm365evm,legacy: lab-baylibre-seattle: failing since 2 days (last pass: v4.4.219-83-g20fbd20eb91a - first fail: v4.4.219-101-gacb152478366) qcom_defconfig: gcc-8: qcom-apq8064-cm-qs600: lab-baylibre-seattle: failing since 77 days (last pass: v4.4.212-56-g758a39807529 - first fail: v4.4.213-28-ga3b43e6eae91) sama5_defconfig: gcc-8: at91-sama5d4_xplained: lab-baylibre: failing since 30 days (last pass: v4.4.216-127-g955137020949 - first fail: v4.4.217) x86_64: x86_64_defconfig: gcc-8: qemu_x86_64: lab-baylibre: new failure (last pass: v4.4.219-101-gacb152478366) Boot Failures Detected: arm: sama5_defconfig: gcc-8: at91-sama5d4_xplained: 1 failed lab multi_v5_defconfig: gcc-8: imx27-phytec-phycard-s-rdk: 1 failed lab imx_v4_v5_defconfig: gcc-8: imx27-phytec-phycard-s-rdk: 1 failed lab Offline Platforms: arm: multi_v7_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab qcom-apq8064-cm-qs600: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab davinci_all_defconfig: gcc-8 da850-evm: 1 offline lab dm365evm,legacy: 1 offline lab exynos_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) x86_64: x86_64_defconfig: qemu_x86_64: lab-baylibre: FAIL (gcc-8) lab-collabora: PASS (gcc-8) --- For more info write to <info(a)kernelci.org>

4 years, 8 months

1
0
0 0

Queue up bc0c4d1e176e

by Jens Axboe

Hi, Can you queue up this: commit bc0c4d1e176eeb614dc8734fc3ace34292771f11 Author: Linus Torvalds <torvalds(a)linux-foundation.org> Date: Fri Apr 24 11:10:58 2020 -0700 mm: check that mm is still valid in madvise() for 5.6-stable? -- Jens Axboe

4 years, 8 months

2
2
0 0

stable-rc/linux-5.6.y boot: 168 boots: 3 failed, 150 passed with 8 offline, 5 untried/unknown, 2 conflicts (v5.6.7)

by kernelci.org bot

stable-rc/linux-5.6.y boot: 168 boots: 3 failed, 150 passed with 8 offline, 5 untried/unknown, 2 conflicts (v5.6.7) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.6.y/kernel/v5.6.… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.6.y/kernel/v5.6.7/ Tree: stable-rc Branch: linux-5.6.y Git Describe: v5.6.7 Git Commit: 55b2af1c23eb12663015998079992f79fdfa56c8 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 103 unique boards, 24 SoC families, 22 builds out of 200 Boot Regressions Detected: arm: davinci_all_defconfig: gcc-8: da850-evm: lab-baylibre-seattle: new failure (last pass: v5.6.6-168-g0c5e841761a8) dm365evm,legacy: lab-baylibre-seattle: new failure (last pass: v5.6.6-168-g0c5e841761a8) arm64: defconfig: gcc-8: meson-axg-s400: lab-baylibre-seattle: new failure (last pass: v5.6.6-168-g0c5e841761a8) x86_64: x86_64_defconfig: gcc-8: qemu_x86_64: lab-collabora: new failure (last pass: v5.6.6-39-gc5f3b541dbc1) Boot Failures Detected: arm: sama5_defconfig: gcc-8: at91-sama5d4_xplained: 1 failed lab multi_v7_defconfig: gcc-8: bcm2836-rpi-2-b: 1 failed lab vexpress_defconfig: gcc-8: vexpress-v2p-ca9: 1 failed lab Offline Platforms: arm64: defconfig: gcc-8 meson-axg-s400: 1 offline lab arm: multi_v7_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab qcom-apq8064-cm-qs600: 1 offline lab stih410-b2120: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab davinci_all_defconfig: gcc-8 da850-evm: 1 offline lab dm365evm,legacy: 1 offline lab exynos_defconfig: gcc-8 exynos5800-peach-pi: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) i386: i386_defconfig: qemu_i386: lab-baylibre: PASS (gcc-8) lab-collabora: FAIL (gcc-8) x86_64: x86_64_defconfig: qemu_x86_64: lab-baylibre: PASS (gcc-8) lab-collabora: FAIL (gcc-8) --- For more info write to <info(a)kernelci.org>

4 years, 8 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror April 2020