public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
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 000/194] 6.1.47-rc1 review
Date: Tue, 22 Aug 2023 15:41:13 +0000	[thread overview]
Message-ID: <20230822154113.GA74437@google.com> (raw)
In-Reply-To: <20230821225853.GB651285@google.com>

On Mon, Aug 21, 2023 at 10:58:53PM +0000, Joel Fernandes wrote:
> On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.47 release.
> > There are 194 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, 23 Aug 2023 19:40:45 +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.47-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
> 
> For RCU,
> Tested-by: Joel Fernandes (Google) <joel@joelfernandes.org>

I am getting the following warning which started after my last
successful 6.1.47-rc1 run. Looks like others already reported it, but
I am just archiving my finding here:

Thanks.

[    2.169887] ------------[ cut here ]------------
[    2.170593] missing return thunk: __alt_instructions_end+0x2256/0x227c-srso_untrain_ret+0x0/0x2: e9 c7 a0 ed fe
[    2.171678] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/alternative.c:572 apply_returns+0x1fb/0x230
[    2.173592] Modules linked in:
[    2.174625] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.47-rc1-g9beeea9636e6 #299
[    2.175608] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[    2.176593] RIP: 0010:apply_returns+0x1fb/0x230
[    2.177592] Code: a5 01 00 0f 85 ef fe ff ff 49 89 d8 b9 05 00 00 00 4c 89 f2 48 89 de 48 c7 c7 60 3e 9d ad c6 05 fa 2c a5 01 01 e8 45 2d 04 00 <0f> 0b e9 c7 fe ff ff c7 84 24 89 00 00 00 cc cc cc cc 42 c7 84 04
[    2.179589] RSP: 0000:ffffffffadc03e28 EFLAGS: 00010286
[    2.180592] RAX: 0000000000000000 RBX: ffffffffae5292f2 RCX: 0000000000000000
[    2.181591] RDX: 0000000000000003 RSI: 0000000000000001 RDI: 00000000ffffffff
[    2.182595] RBP: 0000000000000000 R08: 00000000ffffdfff R09: 00000000ffffdfff
[    2.184589] R10: ffffffffadc574a0 R11: ffffffffadc574a0 R12: ffffffffadc03e40
[    2.185591] R13: ffffffffae520414 R14: ffffffffad4033be R15: ffffffffae5203f0
[    2.186650] FS:  0000000000000000(0000) GS:ffff953a5ca00000(0000) knlGS:0000000000000000
[    2.187637] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    2.188592] CR2: ffff953a5fa01000 CR3: 000000001ee0c000 CR4: 00000000000006f0
[    2.189639] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    2.191589] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[    2.192593] Call Trace:
[    2.194683]  <TASK>
[    2.195595]  ? __warn+0x78/0xc0
[    2.197592]  ? apply_returns+0x1fb/0x230
[    2.198593]  ? report_bug+0xe6/0x170
[    2.199592]  ? console_unlock+0x1a3/0x210
[    2.200594]  ? handle_bug+0x3c/0x70
[    2.201594]  ? exc_invalid_op+0x13/0x60
[    2.202594]  ? asm_exc_invalid_op+0x16/0x20
[    2.203595]  ? retbleed_return_thunk+0x7e/0x7e
[    2.205593]  ? apply_returns+0x1fb/0x230
[    2.206594]  ? apply_returns+0x1fb/0x230
[    2.207596]  alternative_instructions+0x43/0xf2
[    2.208672]  arch_cpu_finalize_init+0x28/0x47
[    2.210595]  start_kernel+0x5f9/0x6a5
[    2.211597]  secondary_startup_64_no_verify+0xe0/0xeb
[    2.213649]  </TASK>> 


  reply	other threads:[~2023-08-22 15:41 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 19:39 [PATCH 6.1 000/194] 6.1.47-rc1 review Greg Kroah-Hartman
2023-08-21 22:58 ` Joel Fernandes
2023-08-22 15:41   ` Joel Fernandes [this message]
2023-08-21 23:35 ` Takeshi Ogasawara
2023-08-22  3:00 ` Bagas Sanjaya
2023-08-22 10:55 ` Naresh Kamboju
2023-08-22 15:27   ` Salvatore Bonaccorso
2023-08-22 15:51     ` Greg Kroah-Hartman
2023-08-22 17:27       ` Greg Kroah-Hartman
2023-08-22 11:01 ` SeongJae Park
2023-08-22 14:08 ` Shuah Khan
2023-08-22 20:23 ` Florian Fainelli
2023-08-22 23:55 ` Ron Economos
2023-08-23  0:49 ` Guenter Roeck
2023-08-23  7:03   ` Greg Kroah-Hartman
2023-08-23  8:17     ` Naresh Kamboju
2023-08-23  8:27       ` Greg Kroah-Hartman
2023-08-23 13:30       ` Guenter Roeck
2023-08-23 15:50         ` Greg Kroah-Hartman
2023-08-24 13:35           ` Greg Kroah-Hartman
2023-08-24 15:08             ` Guenter Roeck
2023-08-24 15:15               ` Greg Kroah-Hartman
2023-08-24 15:58                 ` Guenter Roeck
2023-08-24 16:40                   ` Greg Kroah-Hartman
2023-08-23 13:28     ` Guenter Roeck
2023-08-23  8:54 ` Sudip Mukherjee (Codethink)
2023-08-23  9:26   ` Greg Kroah-Hartman
2023-08-23 10:32     ` Naresh Kamboju
2023-08-23 13:30       ` Guenter Roeck
2023-08-23 14:37     ` Sudip Mukherjee
2023-08-23  9:35 ` Conor Dooley
2023-08-23 13:37   ` Guenter Roeck
2023-08-23 15:24   ` Greg Kroah-Hartman

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=20230822154113.GA74437@google.com \
    --to=joel@joelfernandes.org \
    --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