From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752119AbeAJWMg (ORCPT + 1 other); Wed, 10 Jan 2018 17:12:36 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:33896 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751062AbeAJWMf (ORCPT ); Wed, 10 Jan 2018 17:12:35 -0500 Date: Wed, 10 Jan 2018 14:10:40 -0800 From: "Paul E. McKenney" To: Tejun Heo 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 Reply-To: paulmck@linux.vnet.ibm.com References: <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> <20180110214101.GE3460072@devbig577.frc2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180110214101.GE3460072@devbig577.frc2.facebook.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 x-cbid: 18011022-2213-0000-0000-00000258772B X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00008356; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000245; SDB=6.00973153; UDB=6.00493064; IPR=6.00753104; BA=6.00005772; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00018969; XFM=3.00000015; UTC=2018-01-10 22:09:58 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18011022-2214-0000-0000-000058B78FA2 Message-Id: <20180110221040.GO9671@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-01-10_12:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1801100303 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Wed, Jan 10, 2018 at 01:41:01PM -0800, Tejun Heo wrote: > 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. Works for me! > Thank you very much. And to you! Thanx, Paul From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Paul E. McKenney" Subject: Re: [PATCH] cgroup/cpuset: fix circular locking dependency Date: Wed, 10 Jan 2018 14:10:40 -0800 Message-ID: <20180110221040.GO9671@linux.vnet.ibm.com> References: <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> <20180110214101.GE3460072@devbig577.frc2.facebook.com> Reply-To: paulmck-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20180110214101.GE3460072-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org> Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Tejun Heo Cc: Prateek Sood , Peter Zijlstra , avagin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, sramana-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org On Wed, Jan 10, 2018 at 01:41:01PM -0800, Tejun Heo wrote: > 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. Works for me! > Thank you very much. And to you! Thanx, Paul