linux-kernel - Fwd: kernel fault on hibernation: get_zeroed_page/swsusp

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-next>] [day] [month] [year] [list]

Message-ID: <5d4959b7-61da-8ab0-6bc6-21305d37c7aa@gmail.com>
Date:   Fri, 23 Jun 2023 19:36:21 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Andrew Morton <akpm@...ux-foundation.org>,
        Elmar Stellnberger <estellnb@...tel.org>,
        Thorsten Leemhuis <regressions@...mhuis.info>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux Memory Management <linux-mm@...ck.org>,
        Linux Stable <stable@...r.kernel.org>
Subject: Fwd: kernel fault on hibernation: get_zeroed_page/swsusp_write

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> page allocation error using kernel 6.3.7-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC, from Fr 09 Jun 2023 22:57:31, Key ID b742fa8b80420f66; see the backtrace in the dmesg
>> cat /proc/cpuinfo
> siblings	: 4
> core id		: 1
> cpu cores	: 2
> ...
> type: regression, worked with the previous kernel, namely 6.3.6, Mo 05 Jun 2023 21:37:15, Key ID b742fa8b80420f66 before updating today

And then:

> The first hibernation attempt resulted in the backtrace you can see in the dmesg above, my second hibernation attempt from a text console (vt03 or so) has worked without errors and the third one I tried to do from the GUI/X11 again; see the debug options I had turned on). On the third attempt something strange did happen. It seemed to write to disk as it should, the screen turned black but the power led and button still stayed alighted. Waking up by pressing the power button did not yield any effect, nor the SysRq keys (alas forgot to write 511 to >/proc/sys/kernel/sysrq). After a hard power reset it booted as if not hibernated. On the first hibernation attempt I could see lengthy and intermittent disk access. On the third attempt I had waited for some considerable time.

See Bugzilla for the full thread and attached infos (dmesg, journalctl,
stack trace disassembly).

Unfortunately, the reporter can't provide /proc/kcore output
and haven't performed bisection yet (he can't build custom kernel).

Anyway, I'm adding it to regzbot (as stable-specific regression) for now:

#regzbot introduced: v6.3.6..v6.3.7 https://bugzilla.kernel.org/show_bug.cgi?id=217544
#regzbot title: page allocation error (kernel fault on hibernation involving get_zeroed_page/swsusp_write)
#regzbot link: https://bugs.mageia.org/show_bug.cgi?id=32044

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217544

-- 
An old man doll... just what I always wanted! - Clara