linux-kernel - Re: [4.1-rc1][Hibernation failed] bisect result included

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: <1843682.KATYecaz4u@merkaba>
Date:	Sun, 03 May 2015 20:24:04 +0200
From:	Martin Steigerwald <martin@...htvoll.de>
To:	"Chen, Yu C" <yu.c.chen@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
	"dehrenberg@...omium.org" <dehrenberg@...omium.org>,
	"Zhang, Rui" <rui.zhang@...el.com>,
	"Lu, Aaron" <aaron.lu@...el.com>
Subject: Re: [4.1-rc1][Hibernation failed]  bisect result  included

Am Sonntag, 3. Mai 2015, 15:54:39 schrieb Chen, Yu C:
> Hi,all,

Hello!

> When we are doing QA test, a hibernation failor was found on latest kernel 4.1-rc1,
> resume from hibernation failed with the following error:
> 
> PM: Hibernation image not present or could not be loaded.
> 
> Bisect shows following commit might trigger this problem:
> commit 283e7ad0241155710f99a9f39d13313a53336926
> 
> The  reason for failor is that, some distribution use klibc in initrd
> to restore the image, and klibc will provide kernel with the device 
> format of major:minor:offset,
> for example, 8:3:0 represents a swap partition, and klibc will
> echo 8:3:0 > /sys/power/resume to resume the system manually.
> However in current implementation, format of 8:3:0 will be regarded 
> as an invalid device, so restoring from hibernation failed.
> 
> Do we need to add support for device format like 8:3:0?
> I'm happy to debug more specifically if you can let me know what 
> would be of use, and I've also attached a temporary patch 
> for this problem, not sure if it is suitable,  thanks.

Wow, great.

I just reported this as well, but you bisected it already.

So seems Debian´s initramfs uses klibc. Appears so:

https://wiki.debian.org/initramfs

merkaba:/boot> lsinitramfs -l initrd.img-4.0.1-tp520-btrfs-trim-norace+ | egrep "klibc|libc.so"
-rwxr-xr-x   1 root     root      1729984 Apr 15 02:01 lib/x86_64-linux-gnu/libc.so.6
-rwxr-xr-x   1 root     root        71416 Oct  5  2014 lib/klibc-IpHGKKbZiB_yZ7GPagmQz2GwVAQ.so

It seems to contain a glibc as well.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/