linux-kernel - Re: next-20211015: suspend to ram on x86-32 broken

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YW07O8ZPLVnbGLR7@hirez.programming.kicks-ass.net>
Date:   Mon, 18 Oct 2021 11:15:39 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Pavel Machek <pavel@....cz>
Cc:     tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, x86@...nel.org,
        hpa@...or.com, linux-kernel@...r.kernel.org, rafael@...nel.org,
        len.brown@...el.com, linux-pm@...r.kernel.org,
        sfr@...b.auug.org.au, gor@...ux.ibm.com
Subject: Re: next-20211015: suspend to ram on x86-32 broken

On Mon, Oct 18, 2021 at 10:13:00AM +0200, Pavel Machek wrote:
> Hi!
> > It said
> > 
> > commit 8850cb663b5cda04d33f9cfbc38889d73d3c8e24 (HEAD)
> > Author: Peter Zijlstra <peterz@...radead.org>
> > Date:   Tue Sep 21 22:16:02 2021 +0200
> > 
> >     sched: Simplify wake_up_*idle*()
> > 
> > is first bad commit.
> 
> And reverting that one on the top of -next indeed fixes resume on
> thinkpad x60.

Can you try with just reverting the smp.c hunk and leaving the sched
hunk in place? I've got a hotplug lock related splat in my inbox from
late last week that I didn't get around to yet, I suspect they're
related.