Quoting Jani Nikula (2021-01-28 13:23:48)
A number of our CI systems are hitting redzone overwritten errors after s2idle, with the errors introduced between v5.11-rc4 and v5.11-rc5. See snippet below, full logs for one affected machine at [1].
Known issue?
Fwiw, I think this should be fixed by
commit 08d60e5999540110576e7c1346d486220751b7f9 Author: John Ogness john.ogness@linutronix.de Date: Sun Jan 24 21:33:28 2021 +0106
printk: fix string termination for record_print_text()
Commit f0e386ee0c0b ("printk: fix buffer overflow potential for print_text()") added string termination in record_print_text(). However it used the wrong base pointer for adding the terminator. This led to a 0-byte being written somewhere beyond the buffer.
Use the correct base pointer when adding the terminator.
Fixes: f0e386ee0c0b ("printk: fix buffer overflow potential for print_text()") Reported-by: Sven Schnelle svens@linux.ibm.com Signed-off-by: John Ogness john.ogness@linutronix.de Signed-off-by: Petr Mladek pmladek@suse.com Link: https://lore.kernel.org/r/20210124202728.4718-1-john.ogness@linutronix.de
din should be rolled forward, but there's yet another regression in rc6 breaking suspend on all machines. -Chris