From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> To: Tejun Heo <tj@kernel.org> Cc: Prateek Sood <prsood@codeaurora.org>, Peter Zijlstra <peterz@infradead.org>, 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 Date: Wed, 10 Jan 2018 14:10:40 -0800 [thread overview] Message-ID: <20180110221040.GO9671@linux.vnet.ibm.com> (raw) In-Reply-To: <20180110214101.GE3460072@devbig577.frc2.facebook.com> 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
WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Cc: Prateek Sood <prsood-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>, Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>, 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 Subject: Re: [PATCH] cgroup/cpuset: fix circular locking dependency Date: Wed, 10 Jan 2018 14:10:40 -0800 [thread overview] Message-ID: <20180110221040.GO9671@linux.vnet.ibm.com> (raw) In-Reply-To: <20180110214101.GE3460072-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@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
next prev parent reply other threads:[~2018-01-10 22:12 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-28 1:22 cgroup/for-next: WARNING: possible circular locking dependency detected in cpuset_write_resmask Andrei Vagin 2017-11-28 11:35 ` [PATCH] cgroup/cpuset: fix circular locking dependency Prateek Sood 2017-12-04 5:14 ` Prateek Sood 2017-12-04 5:14 ` Prateek Sood 2017-12-04 20:22 ` Tejun Heo 2017-12-04 20:22 ` Tejun Heo 2017-12-04 22:58 ` Tejun Heo 2017-12-04 23:01 ` Peter Zijlstra 2017-12-04 23:01 ` Peter Zijlstra 2017-12-08 9:40 ` Prateek Sood 2017-12-08 11:45 ` Prateek Sood 2017-12-08 11:45 ` Prateek Sood 2017-12-11 15:32 ` Tejun Heo 2017-12-11 15:32 ` Tejun Heo 2017-12-13 14:28 ` Prateek Sood 2017-12-13 15:40 ` Tejun Heo 2017-12-15 8:54 ` Prateek Sood 2017-12-15 8:54 ` Prateek Sood 2017-12-15 13:22 ` Tejun Heo 2017-12-15 19:06 ` Prateek Sood 2017-12-19 7:26 ` [PATCH] cgroup: Fix deadlock in cpu hotplug path Prateek Sood 2017-12-19 7:26 ` Prateek Sood 2017-12-19 13:39 ` Tejun Heo 2017-12-11 15:20 ` [PATCH] cgroup/cpuset: fix circular locking dependency Tejun Heo 2017-12-11 15:20 ` Tejun Heo 2017-12-13 7:50 ` Prateek Sood 2017-12-13 7:50 ` Prateek Sood 2017-12-13 16:06 ` Tejun Heo 2017-12-15 19:04 ` Prateek Sood 2017-12-15 19:04 ` Prateek Sood 2017-12-28 20:37 ` Prateek Sood 2017-12-28 20:37 ` Prateek Sood 2018-01-02 16:16 ` Tejun Heo 2018-01-02 17:44 ` Paul E. McKenney 2018-01-02 17:44 ` Paul E. McKenney 2018-01-02 18:01 ` Paul E. McKenney 2018-01-08 12:28 ` Tejun Heo 2018-01-08 12:28 ` Tejun Heo 2018-01-08 13:47 ` [PATCH wq/for-4.16 1/2] workqueue: separate out init_rescuer() Tejun Heo 2018-01-08 13:47 ` Tejun Heo 2018-01-08 13:47 ` [PATCH wq/for-4.16 2/2] workqueue: allow WQ_MEM_RECLAIM on early init workqueues Tejun Heo 2018-01-08 13:47 ` Tejun Heo 2018-01-08 22:52 ` [PATCH] cgroup/cpuset: fix circular locking dependency Paul E. McKenney 2018-01-08 22:52 ` Paul E. McKenney 2018-01-09 0:31 ` Paul E. McKenney 2018-01-09 3:42 ` Tejun Heo 2018-01-09 3:42 ` Tejun Heo 2018-01-09 4:20 ` Paul E. McKenney 2018-01-09 13:44 ` Tejun Heo 2018-01-09 15:21 ` Paul E. McKenney 2018-01-09 15:21 ` Paul E. McKenney 2018-01-09 15:37 ` Tejun Heo 2018-01-09 16:00 ` Paul E. McKenney 2018-01-09 16:00 ` Paul E. McKenney 2018-01-10 20:08 ` Paul E. McKenney 2018-01-10 21:41 ` Tejun Heo 2018-01-10 21:41 ` Tejun Heo 2018-01-10 22:10 ` Paul E. McKenney [this message] 2018-01-10 22:10 ` Paul E. McKenney 2018-01-15 12:02 ` Prateek Sood 2018-01-15 12:02 ` Prateek Sood 2018-01-16 16:27 ` Tejun Heo
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20180110221040.GO9671@linux.vnet.ibm.com \ --to=paulmck@linux.vnet.ibm.com \ --cc=avagin@gmail.com \ --cc=cgroups@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=peterz@infradead.org \ --cc=prsood@codeaurora.org \ --cc=sramana@codeaurora.org \ --cc=tj@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.