public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
	"Russell King - ARM Linux" <linux@armlinux.org.uk>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	"Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Subject: Re: [PATCH 5.15 000/411] 5.15.186-rc1 review
Date: Thu, 6 Nov 2025 11:32:18 -0800	[thread overview]
Message-ID: <202511061127.52ECA4AB40@keescook> (raw)
In-Reply-To: <2025062517-lucrative-justness-83fe@gregkh>

On Wed, Jun 25, 2025 at 09:39:45AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jun 25, 2025 at 07:15:24AM +0530, Naresh Kamboju wrote:
> > On Tue, 24 Jun 2025 at 15:48, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Tue, Jun 24, 2025 at 02:12:05AM +0530, Naresh Kamboju wrote:
> > > > On Mon, 23 Jun 2025 at 18:39, Greg Kroah-Hartman
> > > > <gregkh@linuxfoundation.org> wrote:
> > > > >
> > > > > This is the start of the stable review cycle for the 5.15.186 release.
> > > > > There are 411 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 Wed, 25 Jun 2025 13:05:51 +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.186-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
> > > >
> > > > Regressions on arm64 allyesconfig builds with gcc-12 and clang failed on
> > > > the Linux stable-rc 5.15.186-rc1.
> > > >
> > > > Regressions found on arm64
> > > > * arm64, build
> > > >   - gcc-12-allyesconfig
> > > >
> > > > Regression Analysis:
> > > >  - New regression? Yes
> > > >  - Reproducibility? Yes
> > > >
> > > > Build regression: stable-rc 5.15.186-rc1 arm64
> > > > drivers/scsi/qedf/qedf_main.c:702:9: error: positional initialization
> > > > of field in 'struct' declared with 'designated_init' attribute
> > > >
> > > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > > >
> > > > ## Build errors
> > > > drivers/scsi/qedf/qedf_main.c:702:9: error: positional initialization
> > > > of field in 'struct' declared with 'designated_init' attribute
> > > > [-Werror=designated-init]
> > > >   702 |         {
> > > >       |         ^
> > > > drivers/scsi/qedf/qedf_main.c:702:9: note: (near initialization for
> > > > 'qedf_cb_ops')
> > > > cc1: all warnings being treated as errors
> > >
> > > I saw this locally, at times, it's random, not always showing up.  Turn
> > > off the gcc randconfig build option and it goes away, which explains the
> > > randomness I guess.
> > >
> > > If you can bisect this to a real change that causes it, please let me
> > > know, I couldn't figure it out and so just gave up as I doubt anyone is
> > > really using that gcc plugin for that kernel version.
> > 
> > You are right !
> > The reported arm64 allyesconfig build failures are due to,
> > 
> >   randstruct: gcc-plugin: Remove bogus void member
> >   [ Upstream commit e136a4062174a9a8d1c1447ca040ea81accfa6a8 ]
> 
> Thanks for the bisection, for some reason that wasn't working for me.
> I've dropped this, and the other randstruct change from 5.15.y and older
> kernels now.

This thread got pointed out to me. You can put this back in if you want;
you just need the other associated fix (which had a bit of an obscure
Fixes tag):

d8720235d5b5 ("scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops")

-Kees

-- 
Kees Cook

  reply	other threads:[~2025-11-06 19:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 13:02 [PATCH 5.15 000/411] 5.15.186-rc1 review Greg Kroah-Hartman
2025-06-23 20:42 ` Naresh Kamboju
2025-06-24 10:18   ` Greg Kroah-Hartman
2025-06-25  1:45     ` Naresh Kamboju
2025-06-25  8:39       ` Greg Kroah-Hartman
2025-11-06 19:32         ` Kees Cook [this message]
2025-11-21  9:36           ` Greg Kroah-Hartman
2025-11-21 18:00             ` Kees Cook
2025-11-27 13:46               ` Greg Kroah-Hartman
2025-06-23 20:49 ` Florian Fainelli
2025-06-24  8:39 ` Ron Economos
2025-06-25  7:23 ` Jon Hunter
2025-06-25  7:32 ` Vijayendra Suman
2025-07-07 18:05 ` Guenter Roeck
2025-07-08 16:05   ` Martin Blumenstingl
2025-07-12 12:37     ` Greg Kroah-Hartman
2025-07-14 19:56       ` Martin Blumenstingl
2025-07-21 13:48         ` Greg Kroah-Hartman
2025-07-21 14:12         ` Guenter Roeck

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=202511061127.52ECA4AB40@keescook \
    --to=kees@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=jejb@linux.ibm.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=martin.petersen@oracle.com \
    --cc=naresh.kamboju@linaro.org \
    --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=torvalds@linux-foundation.org \
    --cc=valdis.kletnieks@vt.edu \
    /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