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 12:33:07 +0100 [thread overview]
Message-ID: <Y7qp80cK+r247eCU@zn.tnic> (raw)
In-Reply-To: <20230108030748.158120-1-joanbrugueram@gmail.com>
On Sun, Jan 08, 2023 at 03:07:48AM +0000, Joan Bruguera wrote:
> Wake-up from suspend to RAM seems broken under `retbleed=stuff`
> (the recently introduced call depth tracking mitigation, see:
> https://lore.kernel.org/lkml/f9fd86acac4f49bc8f90b403978e9df3@AcuMS.aculab.com/t/)
> I can replicate it on both real hardware and QEMU (with and without KVM).
>
> It can replicate it by booting a fairly standard mainline kernel
Which version exactly?
> on QEMU with `init=/bin/bash` and then suspending to RAM with:
> echo "deep" > /sys/power/mem_sleep
> echo "mem" > /sys/power/state
> Then executing `system_wakeup` on the QEMU monitor causes the crash.
You probably need to share .config too because my tailored .config built with
latest tip/master works fine here.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-01-08 11:33 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 [this message]
2023-01-08 17:11 ` Joan Bruguera
2023-01-08 21:27 ` Borislav Petkov
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=Y7qp80cK+r247eCU@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