linux-kernel - Re: [patch] PM: suspend/resume debugging should depend on SOFTWARE

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:	Sat, 25 Nov 2006 16:08:21 +0000
From:	Alan <alan@...rguk.ukuu.org.uk>
To:	Pavel Machek <pavel@....cz>
Cc:	Adrian Bunk <bunk@...sta.de>, Linus Torvalds <torvalds@...l.org>,
	Chuck Ebbert <76306.1226@...puserve.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, seife@...e.de
Subject: Re: [patch] PM: suspend/resume debugging should depend on
 SOFTWARE_SUSPEND

> Hmm... how common are these machines? We are using unpatched kernel
> for suse10.2... OTOH we only support machines from the whitelist, all

I've always said IDE and software suspend are unsafe. The more work I do
the more clearly this is/was the case.

The really nasty "resume eats your disk" cases I know about are
thankfully for older systems - VIA KT133 and similar era chipsets.
There is a recent nasty - Jmicron goes totally to **** on resume because
of resume quirks not being run but it goes so spectacularly wrong it
doesn't seem to get far enough to corrupt.

Lots of other controllers don't work correctly on resume but thats much
less of a problem and with UDMA misclocking generally turns into a CRC
error storm and stop.

Andrew has about 2/3rds of the bits I've done now, will push the rest
when I've done a little more testing/checking. At that point libata ought
to be resume safe. Someone who cares about drivers/ide legacy support can
then copy the work over.

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