Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933117AbbELOkj (ORCPT ); Tue, 12 May 2015 10:40:39 -0400 Received: from mail-qg0-f52.google.com ([209.85.192.52]:35860 "EHLO mail-qg0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932776AbbELOkg (ORCPT ); Tue, 12 May 2015 10:40:36 -0400 Date: Tue, 12 May 2015 10:40:32 -0400 From: Tejun Heo To: Krzysztof Kozlowski Cc: Kyungmin Park , linux-mm , Andrew Morton , "\\Rafael J. Wysocki\\" , David Rientjes , Johannes Weiner , Oleg Nesterov , Cong Wang , LKML , Linux PM list Subject: Re: [RFC PATCH] PM, freezer: Don't thaw when it's intended frozen processes Message-ID: <20150512144032.GN11388@htj.duckdns.org> References: <20150507064557.GA26928@july> <20150507154212.GA12245@htj.duckdns.org> <20150508152513.GB28439@htj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: 1268 Lines: 37 On Mon, May 11, 2015 at 03:33:10PM +0900, Krzysztof Kozlowski wrote: > > Yes, they should and I'm not sure why what you're saying is happening > > because freezing() test done from the frozen tasks themselves should > > keep them in the freezer. Which kernel version did you test? Can you > > please verify it against a recent kernel? > > I tested it on v4.1-rc3 and next-20150508. > > Task was moved to frozen cgroup: > ----- > root@localhost:/sys/fs/cgroup/freezer/frozen# grep . * > cgroup.clone_children:0 > cgroup.procs:2750 > freezer.parent_freezing:0 > freezer.self_freezing:1 > freezer.state:FROZEN > notify_on_release:0 > tasks:2750 > tasks:2773 > ----- > > Unfortunately during system resume the process was woken up. The "if > (frozen(p))" check was true. Is it expected behaviour? It isn't optimal but doesn't break anything either. Whether a task stays in the freezer or not is solely decided by freezing() test by the task itself. Being woken up spuriously doesn't break anything. 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/