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: <200905260029.25847.oliver@neukum.org>
Date:	Tue, 26 May 2009 00:29:24 +0200
From:	Oliver Neukum <oliver@...kum.org>
To:	nigel@...onice.net
Cc:	Pavel Machek <pavel@....cz>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	linux-pm@...ts.linux-foundation.org,
	tuxonice-devel@...ts.tuxonice.net, linux-kernel@...r.kernel.org
Subject: Re: [TuxOnIce-devel] [RFC] TuxOnIce

Am Montag, 25. Mai 2009 23:39:17 schrieb Nigel Cunningham:
> > If there's not enough swap available, swsusp should freeze, realize
> > there's no swap, unfreeze and continue. I do not see reliability
> > problem there.
>
> If there's not enough storage available (I'm also thinking of the file
> allocator Oliver wants), freeing some memory may get you in a position

No, I do want a dedicated partition. Going to a filesystem is just hiding
the problem. Filesystems can return -ENOSPC.
I also want my sytem to reliably hibernate if the filesystem to hold
the image happens to be remounted ro or to be undergoing a filesystem
check.

For full reliability you simply need a reservation. In addition that's
the fastest solution, too. A simple linear write to an unfragmented
area.
The typical system today has three orders of magnitude more disk
than ram. Do you really have a sytem you want to hibernate that has
less than 2two orders of magnitude more disk than ram?

	Regards
		Oliver

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ