From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752146AbeAJVlM (ORCPT + 1 other); Wed, 10 Jan 2018 16:41:12 -0500 Received: from mail-qk0-f179.google.com ([209.85.220.179]:43208 "EHLO mail-qk0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751486AbeAJVlK (ORCPT ); Wed, 10 Jan 2018 16:41:10 -0500 X-Google-Smtp-Source: ACJfBotSz1jUk+JB7qJid62b56IsUCgoju35/WrDrciCLGokHBLzKQWFIT7Yv/5B2Qktr1zytcWVOQ== Date: Wed, 10 Jan 2018 13:41:01 -0800 From: Tejun Heo To: "Paul E. McKenney" Cc: Prateek Sood , Peter Zijlstra , avagin@gmail.com, mingo@kernel.org, linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, sramana@codeaurora.org Subject: Re: [PATCH] cgroup/cpuset: fix circular locking dependency Message-ID: <20180110214101.GE3460072@devbig577.frc2.facebook.com> References: <20180108122823.GL3668920@devbig577.frc2.facebook.com> <20180108225238.GN9671@linux.vnet.ibm.com> <20180109003127.GA30224@linux.vnet.ibm.com> <20180109034211.GC3668920@devbig577.frc2.facebook.com> <20180109042016.GR9671@linux.vnet.ibm.com> <20180109134448.GE3668920@devbig577.frc2.facebook.com> <20180109152112.GT9671@linux.vnet.ibm.com> <20180109153752.GI3668920@devbig577.frc2.facebook.com> <20180109160022.GW9671@linux.vnet.ibm.com> <20180110200821.GA22541@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180110200821.GA22541@linux.vnet.ibm.com> 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 Return-Path: Hello, Paul. On Wed, Jan 10, 2018 at 12:08:21PM -0800, Paul E. McKenney wrote: > And one additional question... How are we pushing this upstream? By > default, I would push things starting this late into the merge window > following the next one (v4.17), but would be more than willing to make > an exception given that this fixes a valid real-world complaint. I put the workqueue part in the fixes branch. If there's gonna be another rc, I'm gonna push it to Linus. If not, I'll push when the next window opens. I think either way should be fine. > For that matter, if you would rather push my commit along with your pair > of commits, that works for me! Either way, please just let me know. Oh, let's push these through their respective trees. Please take the RCU one through the usual RCU tree. Thank you very much. -- tejun