linux-kernel - Restoring back the system state from MMC after a successful hibernation

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: <2A3DCF3DA181AD40BDE86A3150B27B6B02F1B9BF4C@dbde02.ent.ti.com>
Date:	Tue, 21 Jul 2009 19:35:55 +0530
From:	"A, Raghu" <raghu.a@...com>
To:	"pierre@...man.eu" <pierre@...man.eu>,
	"dbrownell@...rs.sourceforge.net" <dbrownell@...rs.sourceforge.net>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Dasgupta, Romit" <romit@...com>
Subject: Restoring back the system state from MMC after a successful
 hibernation

Hi, 

I am trying a hibernate-restore procedure on my system, wherein I store the context image on a swap partition on a MMC device (/dev/mmcblk0). The hibernation process happens smoothly. However, when I try to restore back, after including "resume = /dev/mmcblk0" in the bootargs, I find that the MMC card does not get detected by the time late_initcall(software_resume) is called, as a result of which the restore does not happen.

To resolve the problem, I have included a mmc_flush_scheduled_work() call immediately after the mmc_detect_change(host, 0) call in mmc_start_host(struct mmc_host *host) function defined in linux/drivers/mmc/core/core.c, so that instead of mmc_rescan happening sometime later, it now happens right away, and the MMC card gets detected at the end of the host's .probe() callback itself.

/*****

void mmc_start_host(struct mmc_host *host)

{
        mmc_power_off(host);
        mmc_detect_change(host, 0);
        mmc_flush_scheduled_work();
}

The host's probe() routine calls mmc_add_host , which in turn calls mmc_start_host.

*****/

Is this approach correct? Or is there any other way I can get the MMC card detected before late_initcall(software_resume) happens?

Kindly CC the reply to me as I am not a part of the linux kernel mailing list.

Thanks and Regards
Raghu A.
--
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/