linux-kernel - Re: MMC/SD Root filesystem suspend/resume problems

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]

Date:	Wed, 25 Jul 2007 20:20:42 +0100
From:	Richard Purdie <rpurdie@...ys.net>
To:	Pavel Machek <pavel@....cz>
Cc:	Pierre Ossman <drzeus-mmc@...eus.cx>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: MMC/SD Root filesystem suspend/resume problems

On Wed, 2007-07-25 at 19:01 +0000, Pavel Machek wrote:
> > I enabled the MMC_UNSAFE_RESUME option and the problems I was seeing was
> > "fixed". I think having this option is a bad idea (in its current form)
> > as it doesn't actually stop filesystem corruption.
> > 
> > With the option disabled, if a filesystem is mounted when you suspend my
> > tests show the filesystem is corrupted. At least if the option is
> > enabled, the filesystem is only corrupted if you remove the card whilst
> > suspended which is more preferable.
> 
> Are we talking _corruption_ here, or are we talking 'the kind of
> corruption recoverable by fsck that happens on powerfail'?

There was more damage to the system than just a dirty bit set. Yes, fsck
could fix it but I don't think it should happen in the first place...

Richard

-
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/