On Wed, Apr 30, 2025 at 04:09:18PM +0530, Naresh Kamboju wrote: > On Tue, 29 Apr 2025 at 23:31, Greg Kroah-Hartman > <gre...@linuxfoundation.org> wrote: > > > > This is the start of the stable review cycle for the 6.1.136 release. > > There are 167 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 Thu, 01 May 2025 16:10:15 +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.1.136-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.1.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > There are three build regressions and two build warnings. > > 1) > Regressions on x86_64 with defconfig builds with clang-nightly toolchain > on the stable-rc 6.1.136-rc1. > > * x86_64, build > - clang-nightly-lkftconfig > - clang-nightly-x86_64_defconfig > > Regression Analysis: > - New regression? Yes > - Reproducibility? Yes > > Build regression: x86_64 clang-nightly net ip.h error default > initialization of an object of type 'typeof (rt->dst.expires)' > > Reported-by: Linux Kernel Functional Testing <l...@linaro.org> > > ## Build error x86_64 > include/net/ip.h:462:14: error: default initialization of an object of > type 'typeof (rt->dst.expires)' (aka 'const unsigned long') leaves the > object uninitialized and is incompatible with C++ > [-Werror,-Wdefault-const-init-unsafe] > 462 | if (mtu && time_before(jiffies, rt->dst.expires)) > | ^
This isn't c++, so are you sure this isn't just a clang bug? thanks, greg k-h
