linux-kernel - Re: [PATCH] Thaw userspace and kernel space separately.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 28 Oct 2006 20:04:47 -0400
From:	Bill Davidsen <davidsen@....com>
To:	Pavel Machek <pavel@....cz>
CC:	Andrew Morton <akpm@...l.org>, "Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Thaw userspace and kernel space separately.

Pavel Machek wrote:
> Hi!
> 
>> Modify process thawing so that we can thaw kernel space without thawing
>> userspace, and thaw kernelspace first. This will be useful in later
>> patches, where I intend to get swsusp thawing kernel threads only before
>> seeking to free memory.
>>
>> Signed-off-by: Nigel Cunningham <nigel@...pend2.net>
> 
> NAK. "May be useful in future" is not good reason to merge it now. (If
> you did not want it merged, just mark it so).

I hope Nigel will keep working at it, since low memory machines like old 
laptops would benefit from suspend are a reality. It can be kept as a 
separate patch somewhere, like suspend2, which people can patch in to 
enhance the example code currently in the kernel.

-- 
Bill Davidsen <davidsen@....com>
   Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
-
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/