Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp6024033ybc; Wed, 27 Nov 2019 13:35:34 -0800 (PST) X-Google-Smtp-Source: APXvYqx3KfQdA9Rsb+LMB8Y20cI/v9J+RAqXRTx9Zi1wC7CRurCkEVDfiKc3qV+tXzNWXWQftnlX X-Received: by 2002:a17:906:d93b:: with SMTP id rn27mr52678078ejb.184.1574890534758; Wed, 27 Nov 2019 13:35:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574890534; cv=none; d=google.com; s=arc-20160816; b=P5qIKPUUQOrtvbWotlT2d6V+aIT1xlaeYb9kJXygkNDJE3E2CQwCRnR7bjF3r9XKET Dy6wSwHmX+AhX9r75OhZNmqG6UtrLdK0CJpuchxQbWJ6qUSc8YSbu37fUTRylvGPdbeP 8tZF7S4nEh3DBjqEG7gbYNKUEMFA+SOLRqsueWmZcaXkszaLD5L4qBJ+aInawjWlp/Gs 6DTU0TNaS6l4lwz6Fpl6loMtqWlh8EaXI9P65mIHh5TXcQt0sRMp88gjt1Mel8Uf6Mni icUHPrhTWOl//HeumPYmKS8/YKEQqe5fnUUlJrGEOWtC1e5KAmELI3Vey2SjYuILae4P Cbhg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=8m4X382WQIMYpszcoLgEj/8kXLqdl77ELwoNlUmVqeQ=; b=upEkvYc1ydyIjvOcqVz10mmG7iX7jwoN2mFG/d/hxeAGz4mHhGzTUe52WjPK77rQQF qnIpf50GxTt7I3VTjK3o/MQlPVA9RtcVq8bdlan0i5b6xEUvHe/vJlDPKEHF0cdfaWp9 oVnML9YwcHhXZD3xsh38rW9ZNzjvXm+XEYoKvIr9Q4fok/EMxuFHSDr0bEHYmja4Zh/5 WrHLM9AlhzgVzv+p6xryibZBJlxJnPHf9z0lBhai26U1raeHAk2FQcb/y5+PlX8xpopD 7RQ9gHr53VxtPFoRldr8pZ283QbTsDJaz34guLYlA+6Y/saUUYNXlbXWpisUv5r36hCf ANag== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="rhmtre/R"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s20si10271509ejx.162.2019.11.27.13.35.10; Wed, 27 Nov 2019 13:35:34 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="rhmtre/R"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729504AbfK0Uwn (ORCPT + 99 others); Wed, 27 Nov 2019 15:52:43 -0500 Received: from mail.kernel.org ([198.145.29.99]:40434 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729982AbfK0Uwl (ORCPT ); Wed, 27 Nov 2019 15:52:41 -0500 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BB67521847; Wed, 27 Nov 2019 20:52:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1574887960; bh=2M4bqX0FVUlvTYzZ0S0NnLRYZpiCJU8Fr7rhThqDBW0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=rhmtre/RA4U4N/BDKV4eYki43NtqhfXhmwYZkPA9WHLsgdZHRldnM3LA7CcT4LTac Qh74lNn7GTrxqkuI978ymaPBiwu2ENlwgtOF+cXOEcQtclqIf29HEBdvIh/hVj7y5A +DJqKrtBtzwya7LwTu+lp+LBFSjLyCnXpQly9nBI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Yang yingliang , zhong jiang , Oscar Salvador , David Hildenbrand , Michal Hocko , Sasha Levin Subject: [PATCH 4.14 161/211] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock Date: Wed, 27 Nov 2019 21:31:34 +0100 Message-Id: <20191127203109.133669683@linuxfoundation.org> X-Mailer: git-send-email 2.24.0 In-Reply-To: <20191127203049.431810767@linuxfoundation.org> References: <20191127203049.431810767@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: zhong jiang [ Upstream commit d2ab99403ee00d8014e651728a4702ea1ae5e52c ] When adding the memory by probing memory block in sysfs interface, there is an obvious issue that we will unlock the device_hotplug_lock when fails to takes it. That issue was introduced in Commit 8df1d0e4a265 ("mm/memory_hotplug: make add_memory() take the device_hotplug_lock") We should drop out in time when fails to take the device_hotplug_lock. Fixes: 8df1d0e4a265 ("mm/memory_hotplug: make add_memory() take the device_hotplug_lock") Reported-by: Yang yingliang Signed-off-by: zhong jiang Reviewed-by: Oscar Salvador Reviewed-by: David Hildenbrand Acked-by: Michal Hocko Cc: stable Signed-off-by: Greg Kroah-Hartman Signed-off-by: Sasha Levin --- drivers/base/memory.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/base/memory.c b/drivers/base/memory.c index 8e5818e735e2f..fe1557aa9b103 100644 --- a/drivers/base/memory.c +++ b/drivers/base/memory.c @@ -519,7 +519,7 @@ memory_probe_store(struct device *dev, struct device_attribute *attr, ret = lock_device_hotplug_sysfs(); if (ret) - goto out; + return ret; nid = memory_add_physaddr_to_nid(phys_addr); ret = __add_memory(nid, phys_addr, -- 2.20.1