From: Borislav Petkov <bp@alien8.de>
To: Joan Bruguera <joanbrugueram@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Wake-up from suspend to RAM broken under `retbleed=stuff`
Date: Sun, 8 Jan 2023 22:27:45 +0100 [thread overview]
Message-ID: <Y7s1Ubyxfdz9V+sp@zn.tnic> (raw)
In-Reply-To: <20230108171159.1311342-1-joanbrugueram@gmail.com>
On Sun, Jan 08, 2023 at 05:11:59PM +0000, Joan Bruguera wrote:
> Arch Linux kernel config (and I leave any new options at their defaults):
> https://aur.archlinux.org/cgit/aur.git/plain/config?h=linux-mainline&id=20ffc62e08f6b0d48a088bccb6e0c3606b88083a
That .config works here.
> I need to either disable the BPF LSM or apply this patch to boot it:
> https://lore.kernel.org/lkml/20230107051456.8800-1-joanbrugueram@gmail.com/
> I suspend with `systemctl suspend`. Waking up hangs with `retbleed=stuff`
> and works without it.
I booted another, more modern guest which has systemd to see whether a different
userspace could be the issue but it works too.
> For verification I booted Fedora-Cloud-Base-Rawhide-20230107.n.0.x86_64.qcow2
> (from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Cloud):
> qemu-system-x86_64 -nodefaults -enable-kvm -smp 1 -m 1024 -vga std \
> -hda Fedora-Cloud-Base-Rawhide-20230107.n.0.x86_64.qcow2 \
> -serial stdio -monitor tcp:127.0.0.1:55555,server,nowait
> I appended `retbleed=stuff,force init=/bin/sh` to the kernel command line,
> suspended through sysfs and then wrote `system_wakeup` on the QEMU monitor.
I guess I'll try that next.
And maybe try that on an Intel machine - I'm using an AMD one but the ",force"
thing enables the same stuffing on AMD too even if it is not the fitting
mitigation for it.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-01-08 21:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 3:07 Wake-up from suspend to RAM broken under `retbleed=stuff` Joan Bruguera
2023-01-08 11:33 ` Borislav Petkov
2023-01-08 17:11 ` Joan Bruguera
2023-01-08 21:27 ` Borislav Petkov [this message]
2023-01-08 22:27 ` Joan Bruguera
2023-01-09 4:05 ` Joan Bruguera
2023-01-11 11:20 ` Peter Zijlstra
2023-01-11 11:39 ` Andrew Cooper
2023-01-11 11:45 ` Jan Beulich
2023-01-11 22:06 ` Andrew Cooper
2023-01-11 11:52 ` Juergen Gross
2023-01-11 12:59 ` Peter Zijlstra
2023-01-11 17:56 ` Rafael J. Wysocki
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=Y7s1Ubyxfdz9V+sp@zn.tnic \
--to=bp@alien8.de \
--cc=joanbrugueram@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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