From: Marc Zyngier <maz@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,
Catalin Marinas <catalin.marinas@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Dan Carpenter <dan.carpenter@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [PATCH 6.12 000/160] 6.12.7-rc1 review
Date: Fri, 27 Dec 2024 13:43:46 +0000 [thread overview]
Message-ID: <87cyhdp7fx.wl-maz@kernel.org> (raw)
In-Reply-To: <2024122711-dab-submarine-a475@gregkh>
On Fri, 27 Dec 2024 13:34:52 +0000,
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> On Fri, Dec 27, 2024 at 01:23:40PM +0000, Marc Zyngier wrote:
> > On Fri, 27 Dec 2024 13:04:11 +0000,
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Thu, Dec 26, 2024 at 01:41:41PM +0000, Marc Zyngier wrote:
> > > > On Tue, 24 Dec 2024 19:12:40 +0000,
> > > > Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> > > > >
> > > > > On Mon, 23 Dec 2024 at 21:31, Greg Kroah-Hartman
> > > > > <gregkh@linuxfoundation.org> wrote:
> > > > > >
> > > > > > This is the start of the stable review cycle for the 6.12.7 release.
> > > > > > There are 160 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 Fri, 27 Dec 2024 15:53:30 +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.12.7-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.12.y
> > > > > > and the diffstat can be found below.
> > > > > >
> > > > > > thanks,
> > > > > >
> > > > > > greg k-h
> > > > >
> > > > > The following test regressions found on arm64 selftests
> > > > > kvm kvm_set_id_regs.
> > > > >
> > > > > This was reported and fixed by a patch [1].
> > > > >
> > > > > * graviton4-metal, kselftest-kvm
> > > > > - kvm_set_id_regs
> > > > >
> > > > > * rk3399-rock-pi-4b-nvhe, kselftest-kvm
> > > > > - kvm_set_id_regs
> > > > >
> > > > > * rk3399-rock-pi-4b-protected, kselftest-kvm
> > > > > - kvm_set_id_regs
> > > > >
> > > > > * rk3399-rock-pi-4b-vhe, kselftest-kvm
> > > > > - kvm_set_id_regs
> > > > >
> > > > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > > >
> > > > This is totally harmless, and if anything, indicates that the *fix*
> > > > is doing its job, and that this patch *must* be backported.
> >
> > I think I caused the confusion here, as "this patch" refers to the
> > original fix which has been queued, rather than the patch to the
> > selftest, which I don't consider a candidate for backports.
> >
> > > Ok, but for some bizare reason someone stripped OFF the Fixes: tag,
> >
> > "Someone" == we, the KVM/arm64 maintainers.
> >
> > And that's on purpose. A selftest patch doesn't fix anything, and I
> > really don't want to use the "Fixes:" tag as a type of dependency.
> > Additionally, these tests are mostly pointless anyway, specially this
> > one, which really should be deleted.
>
> So should I drop something? Revert it? Add a new commit? What is
> going to help solve the issue that we now have selftests failing?
There is nothing to add, as the fix for the selftest isn't upstream
yet. If you are that bothered about an utterly pointless test failing,
feel free to drop the backport of this patch and leave 6.12 being
broken.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-12-27 13:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 15:56 [PATCH 6.12 000/160] 6.12.7-rc1 review Greg Kroah-Hartman
2024-12-23 21:16 ` SeongJae Park
2024-12-23 22:39 ` Shuah Khan
2024-12-23 23:23 ` Takeshi Ogasawara
2024-12-24 8:42 ` Harshit Mogalapalli
2024-12-24 10:16 ` Ron Economos
2024-12-24 12:18 ` Peter Schneider
2024-12-24 12:25 ` Luna Jernberg
2024-12-24 13:26 ` Jon Hunter
2024-12-24 19:12 ` Naresh Kamboju
2024-12-26 13:41 ` Marc Zyngier
2024-12-27 13:04 ` Greg Kroah-Hartman
2024-12-27 13:23 ` Marc Zyngier
2024-12-27 13:34 ` Greg Kroah-Hartman
2024-12-27 13:43 ` Marc Zyngier [this message]
2024-12-27 13:49 ` Greg Kroah-Hartman
2024-12-27 17:27 ` Guenter Roeck
2024-12-24 21:36 ` Justin Forbes
2024-12-26 10:08 ` Muhammad Usama Anjum
2024-12-26 10:32 ` Markus Reichelt
2024-12-26 17:17 ` Florian Fainelli
2024-12-26 19:35 ` [PATCH 6.12] " Hardik Garg
2024-12-26 20:21 ` [PATCH 6.12 000/160] " Pavel Machek
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=87cyhdp7fx.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=oliver.upton@linux.dev \
--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 \
/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