From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752763AbdGEVxs (ORCPT <rfc822;w@1wt.eu>);
        Wed, 5 Jul 2017 17:53:48 -0400
Received: from mail.linuxfoundation.org ([140.211.169.12]:57684 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752502AbdGEVxq (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 5 Jul 2017 17:53:46 -0400
Date: Wed, 5 Jul 2017 14:53:34 -0700
From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org,
        Andrey Ryabinin <aryabinin@virtuozzo.com>,
        Michal Hocko <mhocko@kernel.org>, Vlastimil Babka <vbabka@suse.cz>,
        Vladimir Davydov <vdavydov.dev@gmail.com>,
        Peter Zijlstra <peterz@infradead.org>
Subject: Re: [patch V2 0/2] mm/memory_hotplug: Cure potential deadlocks vs.
 cpu hotplug lock
Message-Id: <20170705145334.d73a30dda944855349e522ed@linux-foundation.org>
In-Reply-To: <20170704093232.995040438@linutronix.de>
References: <20170704093232.995040438@linutronix.de>
X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 04 Jul 2017 11:32:32 +0200 Thomas Gleixner <tglx@linutronix.de> 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?