From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [RFC][PATCH -mm 4/6] Freezer: Prevent new tasks from inheriting TIF_FREEZE set Date: Tue, 10 Jul 2007 08:03:42 +0200 Message-ID: <200707100803.43799.rjw@sisk.pl> References: <200707092229.08898.rjw@sisk.pl> <200707092234.55437.rjw@sisk.pl> <20070709232113.GG1967@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070709232113.GG1967@elf.ucw.cz> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Pavel Machek Cc: Matthew Garrett , Miklos Szeredi , pm list , Oleg Nesterov List-Id: linux-pm@vger.kernel.org On Tuesday, 10 July 2007 01:21, Pavel Machek wrote: > Hi! > > > From: Rafael J. Wysocki > > > > Tasks should go to the refrigerator only if explicitly requested to do that by > > the freezer and not as a result of inheriting the TIF_FREEZE flag set from the > > parent. Make it happen. > > Umm, what prevents userspace task from escaping freezer this way? Does > tasklist_lock prevent new tasks and thus this race? I think so. Greetings, Rafael -- "Premature optimization is the root of all evil." - Donald Knuth