linux-kernel - Re: [PATCH -mm] Allow selective freezing of the system for different events

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: <20070427232222.1ea7797d.akpm@linux-foundation.org>
Date:	Fri, 27 Apr 2007 23:22:22 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	ego@...ibm.com
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, Ingo Molnar <mingo@...e.hu>,
	Oleg Nesterov <oleg@...sign.ru>, Pavel Machek <pavel@....cz>,
	Pekka Enberg <penberg@...helsinki.fi>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -mm] Allow selective freezing of the system for
 different events

On Sat, 28 Apr 2007 07:04:46 +0530 Gautham R Shenoy <ego@...ibm.com> wrote:

> This patch
> * Provides an interface to selectively freeze the system for different events.
> * Allows tasks to exempt themselves or other tasks from specific freeze
>   events.
> * Allow nesting of freezer calls. For eg:
> 
> 	freeze_processes(EVENT_A);
> 	/* Do something with respect to event A */
> 	.
> 	.
> 	.
> 	freeze_processes(EVENT_B);
> 	/* Do something with respect to event B */
> 	.
> 	.
> 	.
> 	thaw_processes(EVENT_B);
> 	.
> 	.
> 	.
> 	thaw_processes(EVENT_B);
> 
> This type of behaviour would be required when cpu hotplug would start
> using the process freezer, where EVENT_A would be SUSPEND and EVENT_B
> would be HOTPLUG_CPU.
> 
> This patch applies on the top of 2.6.21-rc7-mm2 + Rafael's freezer
> changes from http://lkml.org/lkml/2007/4/27/302.

I think I'll duck this.  We have more than enough kthread/freezer/etc work
queued for 2.6.22.  Let's please for now concentrate on reviewing and
testing the existing changes.  Once that has all landed and settled in,
let's start thinking about the next round.


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