From: Conor Dooley <conor.dooley@microchip.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <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>
Subject: Re: [PATCH 6.1 00/15] 6.1.48-rc1 review
Date: Fri, 25 Aug 2023 13:16:07 +0100 [thread overview]
Message-ID: <20230825-radish-gong-b42f53b3e6ad@wendy> (raw)
In-Reply-To: <20230824141447.155846739@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 3754 bytes --]
On Thu, Aug 24, 2023 at 04:14:56PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.48 release.
> There are 15 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.
SRSO mitigations are probably not in the slightest bit relevant for me,
but I didn't get a chance to retest the previous stable release after
the build got unbricked for RISC-V, so:
Tested-by: Conor Dooley <conor.dooley@microchip.com>
Fix for the build issue I saw should be on it's way to Linus today, so
I guess the original fix you were backporting & its fix should end up
back in your queue soonTM.
Thanks,
Conor.
>
> Responses should be made by Sat, 26 Aug 2023 14:14:28 +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.48-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
>
> -------------
> Pseudo-Shortlog of commits:
>
> Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Linux 6.1.48-rc1
>
> Borislav Petkov (AMD) <bp@alien8.de>
> x86/srso: Correct the mitigation status when SMT is disabled
>
> Peter Zijlstra <peterz@infradead.org>
> objtool/x86: Fixup frame-pointer vs rethunk
>
> Petr Pavlu <petr.pavlu@suse.com>
> x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG
>
> Borislav Petkov (AMD) <bp@alien8.de>
> x86/srso: Disable the mitigation on unaffected configurations
>
> Borislav Petkov (AMD) <bp@alien8.de>
> x86/CPU/AMD: Fix the DIV(0) initial fix attempt
>
> Sean Christopherson <seanjc@google.com>
> x86/retpoline: Don't clobber RFLAGS during srso_safe_ret()
>
> Peter Zijlstra <peterz@infradead.org>
> x86/static_call: Fix __static_call_fixup()
>
> Borislav Petkov (AMD) <bp@alien8.de>
> x86/srso: Explain the untraining sequences a bit more
>
> Peter Zijlstra <peterz@infradead.org>
> x86/cpu: Cleanup the untrain mess
>
> Peter Zijlstra <peterz@infradead.org>
> x86/cpu: Rename srso_(.*)_alias to srso_alias_\1
>
> Peter Zijlstra <peterz@infradead.org>
> x86/cpu: Rename original retbleed methods
>
> Peter Zijlstra <peterz@infradead.org>
> x86/cpu: Clean up SRSO return thunk mess
>
> Peter Zijlstra <peterz@infradead.org>
> x86/alternative: Make custom return thunk unconditional
>
> Peter Zijlstra <peterz@infradead.org>
> x86/cpu: Fix up srso_safe_ret() and __x86_return_thunk()
>
> Peter Zijlstra <peterz@infradead.org>
> x86/cpu: Fix __x86_return_thunk symbol type
>
>
> -------------
>
> Diffstat:
>
> Documentation/admin-guide/hw-vuln/srso.rst | 4 +-
> Makefile | 4 +-
> arch/x86/include/asm/entry-common.h | 1 +
> arch/x86/include/asm/nospec-branch.h | 28 +++---
> arch/x86/kernel/cpu/amd.c | 1 +
> arch/x86/kernel/cpu/bugs.c | 28 +++++-
> arch/x86/kernel/static_call.c | 13 +++
> arch/x86/kernel/traps.c | 2 -
> arch/x86/kernel/vmlinux.lds.S | 20 ++--
> arch/x86/kvm/svm/svm.c | 2 +
> arch/x86/lib/retpoline.S | 141 ++++++++++++++++++++---------
> tools/objtool/arch/x86/decode.c | 2 +-
> tools/objtool/check.c | 21 +++--
> 13 files changed, 182 insertions(+), 85 deletions(-)
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-25 12:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 14:14 [PATCH 6.1 00/15] 6.1.48-rc1 review Greg Kroah-Hartman
2023-08-24 14:14 ` [PATCH 6.1 01/15] x86/cpu: Fix __x86_return_thunk symbol type Greg Kroah-Hartman
2023-08-24 14:14 ` [PATCH 6.1 02/15] x86/cpu: Fix up srso_safe_ret() and __x86_return_thunk() Greg Kroah-Hartman
2023-08-24 14:14 ` [PATCH 6.1 03/15] x86/alternative: Make custom return thunk unconditional Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 04/15] x86/cpu: Clean up SRSO return thunk mess Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 05/15] x86/cpu: Rename original retbleed methods Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 06/15] x86/cpu: Rename srso_(.*)_alias to srso_alias_\1 Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 07/15] x86/cpu: Cleanup the untrain mess Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 08/15] x86/srso: Explain the untraining sequences a bit more Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 09/15] x86/static_call: Fix __static_call_fixup() Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 10/15] x86/retpoline: Dont clobber RFLAGS during srso_safe_ret() Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 11/15] x86/CPU/AMD: Fix the DIV(0) initial fix attempt Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 12/15] x86/srso: Disable the mitigation on unaffected configurations Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 13/15] x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 14/15] objtool/x86: Fixup frame-pointer vs rethunk Greg Kroah-Hartman
2023-08-24 14:15 ` [PATCH 6.1 15/15] x86/srso: Correct the mitigation status when SMT is disabled Greg Kroah-Hartman
2023-08-24 21:31 ` [PATCH 6.1 00/15] 6.1.48-rc1 review Florian Fainelli
2023-08-25 3:05 ` Florian Fainelli
2023-08-25 1:30 ` SeongJae Park
2023-08-25 2:40 ` Joel Fernandes
2023-08-25 7:05 ` Naresh Kamboju
2023-08-25 7:15 ` Harshit Mogalapalli
2023-08-25 7:45 ` Christian Brauner
2023-08-25 8:10 ` Greg Kroah-Hartman
2023-08-25 8:48 ` Naresh Kamboju
2023-08-25 16:29 ` Harshit Mogalapalli
2023-08-25 9:33 ` Naresh Kamboju
2023-08-25 9:26 ` Sudip Mukherjee (Codethink)
2023-08-26 8:45 ` Salvatore Bonaccorso
2023-08-25 9:40 ` Naresh Kamboju
2023-08-25 10:15 ` Jon Hunter
2023-08-25 12:16 ` Conor Dooley [this message]
2023-08-25 12:33 ` Takeshi Ogasawara
2023-08-25 15:40 ` Guenter Roeck
2023-08-25 18:12 ` Shuah Khan
2023-08-26 1:23 ` Bagas Sanjaya
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=20230825-radish-gong-b42f53b3e6ad@wendy \
--to=conor.dooley@microchip.com \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.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 \
/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;
as well as URLs for NNTP newsgroup(s).