public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ard Biesheuvel <ardb@kernel.org>, Tom Saeger <tom.saeger@oracle.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	Nathan Chancellor <nathan@kernel.org>,
	Dennis Gilmore <dennis@ausil.us>,
	Palmer Dabbelt <palmer@rivosinc.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 5.15 000/117] 5.15.90-rc1 review
Date: Mon, 23 Jan 2023 08:51:23 +0100	[thread overview]
Message-ID: <Y848ey9hzyHf3t8d@kroah.com> (raw)
In-Reply-To: <CAMj1kXF02H87N4NsPWCdjdkGz-D_EQVMxbN3=btgzr5F=P0eRQ@mail.gmail.com>

On Mon, Jan 23, 2023 at 08:28:18AM +0100, Ard Biesheuvel wrote:
> On Mon, 23 Jan 2023 at 08:24, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Mon, Jan 23, 2023 at 12:39:55PM +0530, Naresh Kamboju wrote:
> > > On Sun, 22 Jan 2023 at 20:46, Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > This is the start of the stable review cycle for the 5.15.90 release.
> > > > There are 117 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, 24 Jan 2023 15:02:08 +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/v5.x/stable-review/patch-5.15.90-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-5.15.y
> > > > and the diffstat can be found below.
> > > >
> > > > thanks,
> > > >
> > > > greg k-h
> > >
> > > Results from Linaro’s test farm.
> > >
> > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > >
> > > Build regressions found on sh:
> > >    - build/gcc-8-dreamcast_defconfig
> > >    - build/gcc-8-microdev_defconfig
> > >
> > >
> > > Build error logs:
> > >
> > > `.exit.text' referenced in section `__bug_table' of crypto/algboss.o:
> > > defined in discarded section `.exit.text' of crypto/algboss.o
> > > `.exit.text' referenced in section `__bug_table' of
> > > drivers/char/hw_random/core.o: defined in discarded section
> > > `.exit.text' of drivers/char/hw_random/core.o
> > > make[1]: *** [/builds/linux/Makefile:1218: vmlinux] Error 1
> > >
> > > Bisection points to this commit,
> > >     arch: fix broken BuildID for arm64 and riscv
> > >     commit 99cb0d917ffa1ab628bb67364ca9b162c07699b1 upstream.
> > >
> > > Ref:
> > > upstream discussion thread,
> > > https://lore.kernel.org/all/Y7Jal56f6UBh1abE@dev-arch.thelio-3990X/
> >
> > Argh, what a mess.  Ok, let me rip out that commit (and the "fixes up
> > that commit") series from the trees and push out a -rc2 in a few hours
> > after I wake up.  I was worried about that one, and I should have
> > trusted my first instinct...
> >
> 
> The patch in question has
> 
>     Fixes: 994b7ac1697b ("arm64: remove special treatment for the link
> order of head.o")
>     Fixes: 2348e6bf4421 ("riscv: remove special treatment for the link
> order of head.o")
> 
> both of which were introduced in the current v6.2 cycle.
> 
> Neither of those are marked for stable, are obviously non-stable
> material, and were not queued up themselves.
> 
> So how did we end up queuing these in the first place?

Because of this long thread:
	https://lore.kernel.org/r/Y842qsBn37yi9OuR@kroah.com
it was requested by Tom to add it (to: him as well.)

I'm dropping the whole series now, and will wait for a working set of
backports to be submitted by Tom before reconsidering them.

thanks,

greg k-h

  reply	other threads:[~2023-01-23  7:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 15:03 [PATCH 5.15 000/117] 5.15.90-rc1 review Greg Kroah-Hartman
2023-01-22 15:03 ` [PATCH 5.15 011/117] x86/asm: Fix an assembler warning with current binutils Greg Kroah-Hartman
2023-01-23  4:07 ` [PATCH 5.15 000/117] 5.15.90-rc1 review Bagas Sanjaya
2023-01-23  4:21 ` Joel Fernandes
2023-01-23  7:09 ` Naresh Kamboju
2023-01-23  7:24   ` Greg Kroah-Hartman
2023-01-23  7:28     ` Ard Biesheuvel
2023-01-23  7:51       ` Greg Kroah-Hartman [this message]
2023-01-23 11:17 ` Sudip Mukherjee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y848ey9hzyHf3t8d@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dennis@ausil.us \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=masahiroy@kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=nathan@kernel.org \
    --cc=palmer@rivosinc.com \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=tom.saeger@oracle.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox