On Mon, Mar 25, 2024 at 03:28:01PM +0530, Naresh Kamboju wrote:
On Mon, 25 Mar 2024 at 04:31, Sasha Levin sashal@kernel.org wrote:
This is the start of the stable review cycle for the 6.6.23 release. There are 638 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 Tue Mar 26 11:01:10 PM UTC 2024. Anything received after that time might be too late.
The whole patch series can be found in one patch at: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/p... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.6.y and the diffstat can be found below.
Thanks, Sasha
The regression detected while building allmodconfig builds with clang-17 failed on all the architectures.
Andrii Nakryiko (3): libbpf: Fix faccessat() usage on Android libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API bpf: don't infer PTR_TO_CTX for programs with unnamed context type
arm64 gcc-13 - FAILED (other architectures passed) arm64 clang-17 - FAILED (All other architectures failed))
The 2 errors are only noticed on arm64.
Jason Gunthorpe (1): iommu/arm-smmu-v3: Check that the RID domain is S1 in SVA
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
Build error:
kernel/bpf/btf.c:5660:10: error: expression which evaluates to zero treated as a null pointer constant of type 'const struct btf_member *' [-Werror,-Wnon-literal-null-conversion] 5660 | return false; | ^~~~~ 1 error generated.
<trim>
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c:358:10: error: incompatible integer to pointer conversion returning 'int' from a function with result type 'struct iommu_sva *' [-Wint-conversion] 358 | return -ENODEV; | ^~~~~~~ drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c:361:10: error: incompatible integer to pointer conversion returning 'int' from a function with result type 'struct iommu_sva *' [-Wint-conversion] 361 | return -ENODEV; | ^~~~~~~ 2 errors generated.
Thanks for the report! I've dropped the two offending commits.