5.15.64-rc1 review
Subsystems (3)
Greg Kroah-Hartman
maintainerPATCH 136/136 bpf: Dont use tnum_range on array range checking for poke descriptors
In reply to Greg Kroah-HartmanFrom: Daniel Borkmann <[email protected]>
commit a657182a5c5150cdfacb6640aad1d2712571a409 upstream.
Hsin-Wei reported a KASAN splat triggered by their BPF runtime fuzzer which is based on a customized syzkaller:
BUG: KASAN: slab-out-of-bounds in bpf_int_jit_compile+0x1257/0x13f0 Read of size 8 at addr ffff888004e90b58 by task syz-executor.0/1489 CPU: 1 PID: 1489 Comm: syz-executor.0 Not tainted 5.19.0 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x9c/0xc9 print_address_description.constprop.0+0x1f/0x1f0 ? bpf_int_jit_compile+0x1257/0x13f0 kasan_report.cold+0xeb/0x197 ? kvmalloc_node+0x170/0x200 ? bpf_int_jit_compile+0x1257/0x13f0 bpf_int_jit_compile+0x1257/0x13f0 ? arch_prepare_bpf_dispatcher+0xd0/0xd0 ? rcu_read_lock_sched_held+0x43/0x70 bpf_prog_select_runtime+0x3e8/0x640 ? bpf_obj_name_cpy+0x149/0x1b0 bpf_prog_load+0x102f/0x2220 ? __bpf_prog_put.constprop.0+0x220/0x220 ? find_held_lock+0x2c/0x110 ? __might_fault+0xd6/0x180 ? lock_downgrade+0x6e0/0x6e0 ? lock_is_held_type+0xa6/0x120 ? __might_fault+0x147/0x180 __sys_bpf+0x137b/0x6070 ? bpf_perf_link_attach+0x530/0x530 ? new_sync_read+0x600/0x600 ? __fget_files+0x255/0x450 ? lock_downgrade+0x6e0/0x6e0 ? fput+0x30/0x1a0 ? ksys_write+0x1a8/0x260 __x64_sys_bpf+0x7a/0xc0 ? syscall_enter_from_user_mode+0x21/0x70 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f917c4e2c2d
The problem here is that a range of tnum_range(0, map->max_entries - 1) has limited ability to represent the concrete tight range with the tnum as the set of resulting states from value + mask can result in a superset of the actual intended range, and as such a tnum_in(range, reg->var_off) check may yield true when it shouldn't, for example tnum_range(0, 2) would result in 00XX -> v = 0000, m = 0011 such that the intended set of {0, 1, 2} is here represented by a less precise superset of {0, 1, 2, 3}. As the register is known const scalar, really just use the concrete reg->var_off.value for the upper index check.
--- kernel/bpf/verifier.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)
kernel/bpf/verifier.c +4 -6
@@ -6096,8 +6096,7 @@ record_func_key(struct bpf_verifier_envstruct bpf_insn_aux_data *aux = &env->insn_aux_data[insn_idx];struct bpf_reg_state *regs =cur_regs (env), *reg;struct bpf_map *map = meta->map_ptr; -struct tnum range; -u64 val; +u64 val, max;int err;if (func_id != BPF_FUNC_tail_call)
@@ -6107,10 +6106,11 @@ record_func_key(struct bpf_verifier_envreturn -EINVAL ; } - range =tnum_range (0 , map->max_entries -1 ); reg = ®s[BPF_REG_3 ]; + val = reg->var_off.value; + max = map->max_entries; -if (!register_is_const (reg) || !tnum_in (range, reg->var_off)) { +if (!(register_is_const (reg) && val < max)) {bpf_map_key_store (aux,BPF_MAP_KEY_POISON );return 0 ; }
@@ -6118,8 +6118,6 @@ record_func_key(struct bpf_verifier_env err =mark_chain_precision (env,BPF_REG_3 );if (err)return err; - - val = reg->var_off.value;if (bpf_map_key_unseen (aux))bpf_map_key_store (aux, val); else if (!bpf_map_key_poisoned(aux) &&
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.64-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.15.y
and the diffstat can be found below.thanks,
greg k-h
On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels and build tested on BMIPS_GENERIC:
Signature · 1 line
Florian
Hi Greg,
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
My builds are still running, but just an initial report for gcc-12. (I know v5.15.y still does not build completely with gcc-12).
x86_64 and arm64 allmodconfig build fails with gcc-12, with the error:
drivers/acpi/thermal.c: In function 'acpi_thermal_resume':drivers/acpi/thermal.c:1101:21: error: the comparison will always evaluate as 'true' for the address of 'active' will never be NULL [-Werror=address]
1101 | if (!(&tz->trips.active[i]))
| ^drivers/acpi/thermal.c:151:36: note: 'active' declared here
151 | struct acpi_thermal_active active[ACPI_THERMAL_MAX_ACTIVE];
Will need e5b5d25444e9 ("ACPI: thermal: drop an always true check").
powerpc allmodconfig fails with gcc-12, the error is:
In function 'memcmp',
inlined from 'bacmp' at ./include/net/bluetooth/bluetooth.h:278:9, inlined from 'l2cap_global_chan_by_psm' atnet/bluetooth/l2cap_core.c:2003:15:./include/linux/fortify-string.h:19:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread]
19 | #define __underlying_memcmp __builtin_memcmp
| ^
./include/linux/fortify-string.h:235:16: note: in expansion of macro
'__underlying_memcmp'
235 | return __underlying_memcmp(p, q, size);
| ^~~~~~~~~~~~~~~~~~~In function 'memcmp',
inlined from 'bacmp' at ./include/net/bluetooth/bluetooth.h:278:9, inlined from 'l2cap_global_chan_by_psm' atnet/bluetooth/l2cap_core.c:2004:15:./include/linux/fortify-string.h:19:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread]
19 | #define __underlying_memcmp __builtin_memcmp
| ^
./include/linux/fortify-string.h:235:16: note: in expansion of macro
'__underlying_memcmp'
235 | return __underlying_memcmp(p, q, size);
| ^~~~~~~~~~~~~~~~~~~Introduced in v5.15.61 due to 2711bedab26c ("Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm regression").
But v5.19.y and mainline does not show the build failure as they also have 41b7a347bf14 ("powerpc: Book3S 64-bit outline-only KASAN support").
Signature · 2 lines
Regards Sudip
Greg Kroah-Hartman
maintainerQuoted 27 lines · Sudip Mukherjee
Hi Greg,
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
My builds are still running, but just an initial report for gcc-12. (I know v5.15.y still does not build completely with gcc-12).
x86_64and arm64 allmodconfig build fails with gcc-12, with the error:
drivers/acpi/thermal.c: In function 'acpi_thermal_resume':drivers/acpi/thermal.c:1101:21: error: the comparison will always evaluate as 'true' for the address of 'active' will never be NULL [-Werror=address]
1101 | if (!(&tz->trips.active[i]))
| ^drivers/acpi/thermal.c:151:36: note: 'active' declared here
151 | structacpi_thermal_activeactive[ACPI_THERMAL_MAX_ACTIVE];
Quoted 1 line
Will need
e5b5d25444e9("ACPI: thermal: drop an always true check").
Now applied.
Quoted 27 lines
powerpc allmodconfig fails with gcc-12, the error is:
In function 'memcmp',
inlined from 'bacmp' at./include/net/bluetooth/bluetooth.h:278:9, inlined from 'l2cap_global_chan_by_psm' atnet/bluetooth/l2cap_core.c:2003:15:./include/linux/fortify-string.h:19:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread]19 | #define __underlying_memcmp __builtin_memcmp | ^ ./include/linux/fortify-string.h:235:16: note: in expansion of macro '__underlying_memcmp' 235 | return __underlying_memcmp(p, q, size); | ^~~~~~~~~~~~~~~~~~~In function 'memcmp',
inlined from 'bacmp' at./include/net/bluetooth/bluetooth.h:278:9, inlined from 'l2cap_global_chan_by_psm' atnet/bluetooth/l2cap_core.c:2004:15:./include/linux/fortify-string.h:19:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread]19 | #define __underlying_memcmp __builtin_memcmp | ^ ./include/linux/fortify-string.h:235:16: note: in expansion of macro '__underlying_memcmp' 235 | return __underlying_memcmp(p, q, size); | ^~~~~~~~~~~~~~~~~~~
Quoted 5 lines
Introduced in v5.15.61 due to
2711bedab26c("Bluetooth: L2CAP: Fixl2cap_global_chan_by_psmregression").
But v5.19.y and mainline does not show the build failure as they also have41b7a347bf14("powerpc: Book3S 64-bit outline-only KASAN support").
Ick, ok, what to do here? I can't really backport 41b7a347bf14 to 5.15 easily as it's huge and a new feature. Any other ideas?
thanks,
greg k-h
Quoted 20 lines · Greg Kroah-Hartman
Quoted 18 lines · Sudip Mukherjee
Hi Greg,
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
My builds are still running, but just an initial report for gcc-12. (I know v5.15.y still does not build completely with gcc-12).
x86_64and arm64 allmodconfig build fails with gcc-12, with the error:
<snip>
Quoted 9 lines
Quoted 6 lines
Introduced in v5.15.61 due to
2711bedab26c("Bluetooth: L2CAP: Fixl2cap_global_chan_by_psmregression").
But v5.19.y and mainline does not show the build failure as they also have41b7a347bf14("powerpc: Book3S 64-bit outline-only KASAN support").Ick, ok, what to do here? I can't really backport
41b7a347bf14to 5.15 easily as it's huge and a new feature. Any other ideas?
Yeah.
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b840304fb46cdf7012722f456bce06f151b3e81b
will fix the it for mips and csky failure in mainline and v5.19.y. And I just verified that it will fix for powerpc also in v5.15.y. So, we just need to wait for now.
Signature · 2 lines
Regards Sudip
Greg Kroah-Hartman
maintainerQuoted 32 lines · Sudip Mukherjee
Quoted 20 lines · Greg Kroah-Hartman
Quoted 18 lines · Sudip Mukherjee
Hi Greg,
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
My builds are still running, but just an initial report for gcc-12. (I know v5.15.y still does not build completely with gcc-12).
x86_64and arm64 allmodconfig build fails with gcc-12, with the error:<snip>
Quoted 7 lines
Quoted 6 lines
Introduced in v5.15.61 due to
2711bedab26c("Bluetooth: L2CAP: Fixl2cap_global_chan_by_psmregression").
But v5.19.y and mainline does not show the build failure as they also have41b7a347bf14("powerpc: Book3S 64-bit outline-only KASAN support").
Quoted 8 lines
Quoted 2 lines
Ick, ok, what to do here? I can't really backport
41b7a347bf14to 5.15 easily as it's huge and a new feature. Any other ideas?Yeah.
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b840304fb46cdf7012722f456bce06f151b3e81b
will fix the it for mips and csky failure in mainline and v5.19.y. And I just verified that it will fix for powerpc also in v5.15.y. So, we just need to wait for now.
Ah good, thanks for pointing that out!
greg k-h
Quoted 37 lines · Greg Kroah-Hartman
Quoted 35 lines · Sudip Mukherjee
Quoted 20 lines · Greg Kroah-Hartman
Quoted 18 lines · Sudip Mukherjee
Hi Greg,
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
My builds are still running, but just an initial report for gcc-12. (I know v5.15.y still does not build completely with gcc-12).
x86_64and arm64 allmodconfig build fails with gcc-12, with the error:<snip>
Quoted 9 lines
Quoted 6 lines
Introduced in v5.15.61 due to
2711bedab26c("Bluetooth: L2CAP: Fixl2cap_global_chan_by_psmregression").
But v5.19.y and mainline does not show the build failure as they also have41b7a347bf14("powerpc: Book3S 64-bit outline-only KASAN support").Ick, ok, what to do here? I can't really backport
41b7a347bf14to 5.15 easily as it's huge and a new feature. Any other ideas?
Quoted 7 lines
Quoted 5 lines
Yeah.
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b840304fb46cdf7012722f456bce06f151b3e81b
will fix the it for mips and csky failure in mainline and v5.19.y. And I just verified that it will fix for powerpc also in v5.15.y. So, we just need to wait for now.Ah good, thanks for pointing that out!
uhh.. I can see you already added to the stable tree, but its not in mainline yet.
Signature · 2 lines
Regards Sudip
Greg Kroah-Hartman
maintainerQuoted 45 lines · Sudip Mukherjee
Quoted 43 lines · Greg Kroah-Hartman
Quoted 40 lines · Sudip Mukherjee
Quoted 20 lines · Greg Kroah-Hartman
Quoted 18 lines · Sudip Mukherjee
Hi Greg,
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
My builds are still running, but just an initial report for gcc-12. (I know v5.15.y still does not build completely with gcc-12).
x86_64and arm64 allmodconfig build fails with gcc-12, with the error:<snip>
Quoted 9 lines
Quoted 6 lines
Introduced in v5.15.61 due to
2711bedab26c("Bluetooth: L2CAP: Fixl2cap_global_chan_by_psmregression").
But v5.19.y and mainline does not show the build failure as they also have41b7a347bf14("powerpc: Book3S 64-bit outline-only KASAN support").Ick, ok, what to do here? I can't really backport
41b7a347bf14to 5.15 easily as it's huge and a new feature. Any other ideas?Yeah.
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b840304fb46cdf7012722f456bce06f151b3e81b
will fix the it for mips and csky failure in mainline and v5.19.y. And I just verified that it will fix for powerpc also in v5.15.y. So, we just need to wait for now.
Quoted 4 lines
Quoted 1 line
Ah good, thanks for pointing that out!
uhh.. I can see you already added to the stable tree, but its not in mainline yet.
It's on track to get to Linus and fixes a build problem, should be ok.
Greg Kroah-Hartman
maintainerQuoted 46 lines · Greg Kroah-Hartman
Quoted 45 lines · Sudip Mukherjee
Quoted 43 lines · Greg Kroah-Hartman
Quoted 40 lines · Sudip Mukherjee
Quoted 20 lines · Greg Kroah-Hartman
Quoted 18 lines · Sudip Mukherjee
Hi Greg,
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
My builds are still running, but just an initial report for gcc-12. (I know v5.15.y still does not build completely with gcc-12).
x86_64and arm64 allmodconfig build fails with gcc-12, with the error:<snip>
Quoted 9 lines
Quoted 6 lines
Introduced in v5.15.61 due to
2711bedab26c("Bluetooth: L2CAP: Fixl2cap_global_chan_by_psmregression").
But v5.19.y and mainline does not show the build failure as they also have41b7a347bf14("powerpc: Book3S 64-bit outline-only KASAN support").Ick, ok, what to do here? I can't really backport
41b7a347bf14to 5.15 easily as it's huge and a new feature. Any other ideas?Yeah.
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b840304fb46cdf7012722f456bce06f151b3e81b
will fix the it for mips and csky failure in mainline and v5.19.y. And I just verified that it will fix for powerpc also in v5.15.y. So, we just need to wait for now.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
Ah good, thanks for pointing that out!
uhh.. I can see you already added to the stable tree, but its not in mainline yet.
It's on track to get to Linus and fixes a build problem, should be ok.
And it's now in Linus's tree so all is good :)
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.64-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.15.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
Build results:
total: 159 pass: 159 fail: 0 Qemu test results: total: 485 pass: 485 fail: 0
Guenter
Hello!
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.64-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.15.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro's test farm.
No regressions on arm64, arm, x86_64, and i386.
## Build
* kernel: 5.15.64-rc1
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-5.15.y
* git commit: 881ab4a7404df537a02c17ade40cb8c7510b5ff0
* git describe: v5.15.63-137-g881ab4a7404d
* test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.63-137-g881ab4a7404d
## No test regressions (compared to v5.15.63)
## No metric regressions (compared to v5.15.63)
## No test fixes (compared to v5.15.63)
## No metric fixes (compared to v5.15.63)
## Test result summary
total: 104529, pass: 92369, fail: 635, skip: 11206, xfail: 319
## Build Summary
* arc: 10 total, 10 passed, 0 failed
* arm: 306 total, 303 passed, 3 failed
* arm64: 68 total, 65 passed, 3 failed
* i386: 57 total, 51 passed, 6 failed
* mips: 50 total, 47 passed, 3 failed
* parisc: 14 total, 14 passed, 0 failed
* powerpc: 59 total, 56 passed, 3 failed
* riscv: 27 total, 26 passed, 1 failed
* s390: 26 total, 23 passed, 3 failed
* sh: 26 total, 24 passed, 2 failed
* sparc: 14 total, 14 passed, 0 failed
* x86_64: 61 total, 58 passed, 3 failed
## Test suites summary
* fwts
* igt-gpu-tools
* kunit
* kvm-unit-tests
* libgpiod
* libhugetlbfs
* log-parser-boot
* log-parser-test
* ltp-cap_bounds
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-fsx
* ltp-hugetlb
* ltp-io
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-open-posix-tests
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-syscalls
* ltp-tracing
* network-basic-tests
* packetdrill
* rcutorture
* v4l2-compliance
* vdso
Greetings!
Daniel Díaz
[email protected]
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Quoted 4 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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.
Successfully cross-compiled for arm64 (bcm2711_defconfig, GCC 10.2.0) and powerpc (ps3_defconfig, GCC 12.1.0).
Signature · 1 line
An old man doll... just what I always wanted! - Clara
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.64-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.15.y
and the diffstat can be found below.thanks,
greg k-h
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Jon Hunter
maintainerHi Greg,
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.64-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.15.y
and the diffstat can be found below.thanks,
greg k-h
I have been out on vacation and unfortunately some boot issues were introduced for Tegra back in 5.15.61 ...
Test results for stable-v5.15:
10 builds: 10 pass, 0 fail
32 boots: 28 pass, 4 fail
68 tests: 68 pass, 0 failLinux version: 5.15.64-rc1-g881ab4a7404d
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
tegra20-ventana, tegra210-p2371-2180,
tegra210-p3450-0000, tegra30-cardhu-a04Boot failures: tegra186-p2771-0000, tegra194-p2972-0000,
tegra194-p3509-0000+p3668-0000
Fortunately, these boot issues are specific to Tegra and were caused by commit a7f751d4e830c5a2ac9e9908df43e8d29b7d3b22 ("arm64: tegra: Mark BPMP channels as no-memory-wc"). This commit had the fixes tag populated but it has a dependency on mainline commit a4740b148a04 ("firmware: tegra: bpmp: Do only aligned access to IPC memory area") which did not have any fixes tag populated.
Can you pull mainline commit a4740b148a04 ("firmware: tegra: bpmp: Do only aligned access to IPC memory area") into 5.15.y, 5.18.y and 5.19.y? Fine if you want to do it for the next stable update.
Sorry about this. In future I will definitely make sure that someone is monitoring this while I am away.
Thanks
Jon
Signature · 1 line
nvpublic
Greg Kroah-Hartman
maintainerQuoted 47 lines · Jon Hunter
Hi Greg,
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.64-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.15.y
and the diffstat can be found below.thanks,
greg k-h
I have been out on vacation and unfortunately some boot issues were introduced for Tegra back in 5.15.61 ...
Test results for stable-v5.15:
10 builds: 10 pass, 0 fail 32 boots: 28 pass, 4 fail 68 tests: 68 pass, 0 failLinux version: 5.15.64-rc1-g881ab4a7404d
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04Boot failures: tegra186-p2771-0000, tegra194-p2972-0000,
tegra194-p3509-0000+p3668-0000Fortunately, these boot issues are specific to Tegra and were caused by commit
a7f751d4e830c5a2ac9e9908df43e8d29b7d3b22("arm64: tegra: Mark BPMP channels as no-memory-wc"). This commit had the fixes tag populated but it has a dependency on mainline commita4740b148a04("firmware: tegra: bpmp: Do only aligned access to IPC memory area") which did not have any fixes tag populated.
Quoted 3 lines
Can you pull mainline commit
a4740b148a04("firmware: tegra: bpmp: Do only aligned access to IPC memory area") into 5.15.y, 5.18.y and 5.19.y? Fine if you want to do it for the next stable update.
5.18.y is end-of-life, so I've applied this to the other branches now, thanks!
greg k-h
Hi Greg,
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.64 release. There are 136 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, 31 Aug 2022 10:57:37 +0000. Anything received after that time might be too late.
Build test (gcc version 11.3.1 20220819):
mips: 62 configs -> no failure
arm: 99 configs -> no failure
arm64: 3 configs -> no failurex86_64: 4 configs -> no failure
alpha allmodconfig -> no failure
csky allmodconfig -> no failure
powerpc allmodconfig -> no failure
riscv allmodconfig -> no failure
s390 allmodconfig -> no failure
xtensa allmodconfig -> no failure
Boot test:x86_64: Booted on my test laptop. No regression.x86_64: Booted on qemu. No regression. [1]
arm64: Booted on rpi4b (4GB model). No regression. [2]
mips: Booted on ci20 board. No regression. [3]
[1]. https://openqa.qa.codethink.co.uk/tests/1729
[2]. https://openqa.qa.codethink.co.uk/tests/1733
[3]. https://openqa.qa.codethink.co.uk/tests/1735
--
Regards
Sudip