Re: [PATCH 6.13 00/23] 6.13.10-rc1 review

[Greg Kroah-Hartman]

On Sat, Apr 05, 2025 at 11:50:59AM +0530, Naresh Kamboju wrote:
> On Thu, 3 Apr 2025 at 20:56, Greg Kroah-Hartman
> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> >
> > This is the start of the stable review cycle for the 6.13.10 release.
> > There are 23 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 Sat, 05 Apr 2025 15:16:11 +0000.
> > 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/v6.x/stable-review/patch-6.13.10-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-6.13.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> 
> 
> Regressions on arm, arm64 and x86_64.
> 
> 1)
> The selftests rseq failed across the boards and virtual environments.
> These test failures were also noticed on Linux mainline and next.
> 
> We will bisect these lists of regressions and get back to you.

Thanks, this I'll care about, but:

> * kselftest-rseq
>   - rseq_basic_percpu_ops_mm_cid_test
>   - rseq_basic_percpu_ops_test
>   - rseq_basic_test
>   - rseq_param_test
>   - rseq_param_test_benchmark
>   - rseq_param_test_compare_twice
>   - rseq_param_test_mm_cid
>   - rseq_param_test_mm_cid_benchmark
>   - rseq_param_test_mm_cid_compare_twice
> 
> 2)
>  The clang-nightly build issues reported on mainline and next.
> 
> * S390, powerpc, build
>   - clang-nightly-defconfig
>   - clang-nightly-lkftconfig-hardening
>   - clang-nightly-lkftconfig-lto-full
>   - clang-nightly-lkftconfig-lto-thing
> 
>  clang-nightly: ERROR: modpost: "wcslen" [fs/smb/client/cifs.ko] undefined!
>   - https://lore.kernel.org/all/CA+G9fYuQHeGicnEx1d=XBC0p1LCsndi5q0p86V7pCZ02d8Fv_w@xxxxxxxxxxxxxx/
> 
> 3)
>  The clang-nightly boot regressions with no console output have been
>  reported on mainline and next.

These 2 I don't, as that's a mainline issue first.

thanks,

greg k-h