From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752982AbdGFGeI (ORCPT ); Thu, 6 Jul 2017 02:34:08 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:55003 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752866AbdGFGeH (ORCPT ); Thu, 6 Jul 2017 02:34:07 -0400 Date: Thu, 6 Jul 2017 08:34:00 +0200 (CEST) From: Thomas Gleixner To: Andrew Morton cc: LKML , linux-mm@kvack.org, Andrey Ryabinin , Michal Hocko , Vlastimil Babka , Vladimir Davydov , Peter Zijlstra Subject: Re: [patch V2 0/2] mm/memory_hotplug: Cure potential deadlocks vs. cpu hotplug lock In-Reply-To: <20170705145334.d73a30dda944855349e522ed@linux-foundation.org> Message-ID: References: <20170704093232.995040438@linutronix.de> <20170705145334.d73a30dda944855349e522ed@linux-foundation.org> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 5 Jul 2017, Andrew Morton wrote: > On Tue, 04 Jul 2017 11:32:32 +0200 Thomas Gleixner wrote: > > > Andrey reported a potential deadlock with the memory hotplug lock and the > > cpu hotplug lock. > > > > The following series addresses this by reworking the memory hotplug locking > > and fixing up the potential deadlock scenarios. > > Do you think we should squeeze this into 4.13-rc1, or can we afford to > take the more cautious route? The deadlocks are real and the lockdep splats are triggering on Linus head, so it should go into 4.13-rc1 if possible. Thanks, tglx