public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: a-development@posteo.de
To: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	peterz@infradead.org, David.Kaplan@amd.com,
	Andrew.Cooper3@citrix.com, jpoimboe@kernel.org,
	gregkh@linuxfoundation.org
Subject: Re: [RFC][PATCH 00/17] Fix up the recent SRSO patches
Date: Mon, 22 Apr 2024 07:01:02 +0000	[thread overview]
Message-ID: <98d6c53b244c579b7c7e28872d5cb665@posteo.net> (raw)
In-Reply-To: <20240417091200.GAZh-SYOGABCnsqpKj@fat_crate.local>

Hello. I have installed the kernel through 
https://aur.archlinux.org/packages/linux-mainline and noticed that SRSO 
is disabled. "Speculative Return Stack Overflow: IBPB-extending 
microcode not applied!"

cat /sys/devices/system/cpu/vulnerabilities/spec_rstack_overflow
Vulnerable: Safe RET, no microcode

So far, I have been succesfully suspending the one night I used it.

Assuming this is per-default, I've installed the kernel module for my 
PCIe Capture card and testing it.

Any new instructions?

Thanks

On 17.04.2024 11:12, Borislav Petkov wrote:
> On Wed, Apr 17, 2024 at 08:08:53AM +0000, a-development@posteo.de 
> wrote:
>> Today I failed to suspend, and the spec_rstack thing was off.
>> 
>> https://up.tail.ws/txt/non-working-suspend-2.txt
> 
> Ok, but please do not top-post. Put your reply underneath the next
> you're replying to and remove the rest of the quoted text like I just
> did.
> 
> So this could be caused by the proprietary module or something else.
> 
> If you want this debugged, you'd have to try to reproduce it with the
> latest upstream kernel from here:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> 
> after having removed the propietary module.
> 
> HTH.

  reply	other threads:[~2024-04-22  7:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27 18:58 [RFC][PATCH 00/17] Fix up the recent SRSO patches a-development
2024-01-27 19:19 ` Borislav Petkov
2024-01-27 19:27   ` a-development
2024-01-27 19:41     ` Borislav Petkov
2024-01-29 18:18       ` a-development
2024-03-26 22:21         ` Borislav Petkov
2024-04-16  6:48           ` a-development
2024-04-16  8:45             ` Borislav Petkov
2024-04-16 20:14               ` a-development
2024-04-17  8:08                 ` a-development
2024-04-17  9:12                   ` Borislav Petkov
2024-04-22  7:01                     ` a-development [this message]
2024-01-27 19:28   ` a-development
  -- strict thread matches above, loose matches on Subject: below --
2023-08-09  7:12 Peter Zijlstra
2023-08-09  9:04 ` Nikolay Borisov
2023-08-09 10:04 ` Andrew.Cooper3
2023-08-09 11:58   ` Peter Zijlstra

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=98d6c53b244c579b7c7e28872d5cb665@posteo.net \
    --to=a-development@posteo.de \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=David.Kaplan@amd.com \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.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