Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756028AbdIGUiP (ORCPT ); Thu, 7 Sep 2017 16:38:15 -0400 Received: from mail-qk0-f193.google.com ([209.85.220.193]:34655 "EHLO mail-qk0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755796AbdIGUiN (ORCPT ); Thu, 7 Sep 2017 16:38:13 -0400 X-Google-Smtp-Source: AOwi7QCA9PSu3XwT2A1oMKRDg+9OpRZPxgDnPXryPZh36Z4ZHCYVW+fad69INzXuizdFiN12nTucxQ== Date: Thu, 7 Sep 2017 13:38:08 -0700 From: Tejun Heo To: Peter Zijlstra Cc: Mike Galbraith , Andy Lutomirski , Andy Lutomirski , Ingo Molnar , "linux-kernel@vger.kernel.org" , "Rafael J. Wysocki" , Thomas Gleixner Subject: Re: [PATCH] sched/cpuset/pm: Fix cpuset vs suspend-resume Message-ID: <20170907203808.GU1774378@devbig577.frc2.facebook.com> References: <20170906082520.xgvo3hewje7jvdyo@hirez.programming.kicks-ass.net> <877A43A3-AC8F-4D7C-88E4-8E3D36B1DAFA@amacapital.net> <20170906090333.7v627vdyvhe3x2cs@hirez.programming.kicks-ass.net> <20170906161422.kvqe5y6b3ng6ouyu@hirez.programming.kicks-ass.net> <1504764929.6355.5.camel@gmx.de> <20170907091338.orwxrqkbfkki3c24@hirez.programming.kicks-ass.net> <20170907092616.thsuyqklit4463wj@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170907092616.thsuyqklit4463wj@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 852 Lines: 29 Hello, On Thu, Sep 07, 2017 at 11:26:16AM +0200, Peter Zijlstra wrote: > TJ, I _think_ it was commit: > > deb7aa308ea2 ("cpuset: reorganize CPU / memory hotplug handling") Heh, that's a while ago. > That wrecked things, but there's been so much changes in this area it is > really hard to tell. Note how before that commit it would > unconditionally rebuild the domains, and you 'optimized' that ;-) > > That commit also introduced the work to do the async rebuild and failed > to do that flush on resume. > > In any case, I think we should put a fixes tag on this commit such that > it gets picked up into stable kernels. Not sure anybody will try and > backport it into 4 year old kernels, but who knows. I see & sounds good to me. I see that the patch already got applied but FWIW, Acked-by: Tejun Heo Thanks! -- tejun