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  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:	Tue, 17 Nov 2009 08:53:00 +0100
From:	Stefan Richter <>
To:	Ben Hutchings <>
CC:	Andrew Morton <>,, LKML <>,,
	Wouter van Heyst <>,
	Pierre Ossman <>
Subject: Re: [PATCH] mmc: add module parameter to set whether cards are assumed

Ben Hutchings wrote:
> In general, it is not possible to tell whether a card present in an MMC
> slot after resume is the same that was there before suspend.

That's true for virtually all storage devices, not just MMC.

> So there are two possible behaviours, each of which will cause data
> loss in some cases:
> CONFIG_MMC_UNSAFE_RESUME=n (default): Cards are assumed to be removed
> during suspend.  Any filesystem on them must be unmounted before
> suspend; otherwise, buffered writes will be lost.
> CONFIG_MMC_UNSAFE_RESUME=y: Cards are assumed to remain present during
> suspend.  They must not be swapped during suspend; otherwise, buffered
> writes will be flushed to the wrong card.
> Currently the choice is made at compile time and this allows that to be
> overridden at module load time.

Can't the kernel flush the write buffer at suspend time, so that you can
remove this choice for good?
Stefan Richter
-=====-==--= =-== =---=
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists