Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752233AbbEGPmT (ORCPT ); Thu, 7 May 2015 11:42:19 -0400 Received: from mail-qk0-f175.google.com ([209.85.220.175]:35302 "EHLO mail-qk0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751886AbbEGPmR (ORCPT ); Thu, 7 May 2015 11:42:17 -0400 Date: Thu, 7 May 2015 11:42:12 -0400 From: Tejun Heo To: Kyungmin Park Cc: linux-mm@kvack.org, Andrew Morton , "\\\"Rafael J. Wysocki\\\"" , David Rientjes , Johannes Weiner , Oleg Nesterov , Cong Wang , LKML , linux-pm@vger.kernel.org Subject: Re: [RFC PATCH] PM, freezer: Don't thaw when it's intended frozen processes Message-ID: <20150507154212.GA12245@htj.duckdns.org> References: <20150507064557.GA26928@july> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150507064557.GA26928@july> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1092 Lines: 28 Hello, On Thu, May 07, 2015 at 03:45:57PM +0900, Kyungmin Park wrote: > From: Kyungmin Park > > Some platform uses freezer cgroup for speicial purpose to schedule out some applications. but after suspend & resume, these processes are thawed and running. They shouldn't be able to leave the freezer tho. Resuming does wake up all tasks but freezing() test would still evaulate to true for the ones frozen by cgroup freezer and they will stay inside the freezer. > but it's inteneded and don't need to thaw it. > > To avoid it, does it possible to modify resume code and don't thaw it when resume? does it resonable? I need to think more about it but as an *optimization* we can add freezing() test before actually waking tasks up during resume, but can you please clarify what you're seeing? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/