On Thu, Mar 06, 2025 at 06:44:42PM +0100, Borislav Petkov wrote: > On Thu, Mar 06, 2025 at 10:59:35PM +0530, Naresh Kamboju wrote: > > On Thu, 6 Mar 2025 at 20:50, Greg Kroah-Hartman > > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > This is the start of the stable review cycle for the 6.6.81 release. > > > There are 147 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, 08 Mar 2025 15:13:38 +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.6.81-rc2.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.6.y > > > and the diffstat can be found below. > > > > > > thanks, > > > > > > greg k-h > > > > > > Regressions on i386 the defconfig builds failed with clang-20 > > and gcc-13 the stable-rc 6.6.81-rc2. > > > > First seen on the > > Good: v6.6.78 > > Bad: v6.6.78-442-g8f0527d547fe > > > > * i386 build > > - clang-20-defconfig > > - clang-nightly-defconfig > > - gcc-13-defconfig > > - gcc-8-defconfig > > > > Regression Analysis: > > - New regression? Yes > > - Reproducibility? Yes > > > > Build regression: i386 microcode core.c use of undeclared identifier > > 'initrd_start_early' > > Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx> > > > > ## Build log > > arch/x86/kernel/cpu/microcode/core.c:198:11: error: use of undeclared > > identifier 'initrd_start_early'; did you mean 'initrd_start'? > > 198 | start = initrd_start_early; > > | ^~~~~~~~~~~~~~~~~~ > > | initrd_start > > include/linux/initrd.h:18:22: note: 'initrd_start' declared here > > 18 | extern unsigned long initrd_start, initrd_end; > > | ^ > > 1 error generated. > > Looks like we need: > > 4c585af7180c ("x86/boot/32: Temporarily map initrd for microcode loading") > > after all. Stupid 32-bit sh*t. > > Greg, ontop of what do you want this backported? Or should I send you a whole > set again with this patch in the right spot and you can apply the whole set > again? Let me see if that backports cleanly... Nope. A backported version would be great. If you want to just send me a single patch, or a whole new bundle, anything will work, whatever is easier for you. thanks, greg k-h
