linux-kernel - Re: [TuxOnIce-devel] [RFC] TuxOnIce

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: <200905270110.54259.rjw@sisk.pl>
Date:	Wed, 27 May 2009 01:10:53 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	nigel@...onice.net, linux-pm@...ts.linux-foundation.org,
	tuxonice-devel@...ts.tuxonice.net, linux-kernel@...r.kernel.org,
	Pavel Machek <pavel@....cz>
Subject: Re: [TuxOnIce-devel] [RFC] TuxOnIce

On Wednesday 27 May 2009, Oliver Neukum wrote:
> Am Dienstag, 26. Mai 2009 00:58:53 schrieb Rafael J. Wysocki:
> > > No, I am afraid it is not. The average user has no clue. Even if that
> > > is not the problem, the user never knows for sure he has encountered
> > > the worst case.
> >
> > OK there, but surely it's better to have a sysfs attribute than a fixed
> > value?
> 
> Maybe I should have been more verbose.
> 
> A tunable setting is a race condition in itself. The right amount depends
> on the drivers loaded and the devices attached and possibly on the status
> of devices. Nothing of this can be determined statically.
> 
> You want hibernation to work even if the user has plugged in a new device.
> You have to calculate that amount in kernel space.

In practice, though, the drivers don't usually tell us in advance how much
memory they are going to need and I believe the only way they could do that
would be by allocating the memory from a hibernation notifier.

So, until the drivers start to use hibernation (and suspend for that matter)
notifiers, we need workarounds.

Best,
Rafael
--
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/