Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1319408yba; Wed, 24 Apr 2019 20:01:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqypZvuK8k4sQVXp7U2awsJpF/6U7AJdJnOdesXwAgpzZaPMdkKH6EQExzUuofMxZuKN7f5e X-Received: by 2002:aa7:982f:: with SMTP id q15mr5586380pfl.244.1556161272148; Wed, 24 Apr 2019 20:01:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556161272; cv=none; d=google.com; s=arc-20160816; b=eyIa3sipD2DdPnr7D55I3lnTAQCspusbTKyK3dcfOpnjryDovPBk+Z/+IB5/ZCDX4E mrnYYGnXr+orrCDcjUzvQe+cpdTwdbBz2C4YwrpvygSZO8Pl1cEJnW+pK/4zdFtgbOuo Eg/0PbcvnG9dEEoU4E5mm0dxPCwcaWuI+jivMT13j4ZpvgPKvzAq54HsTPBu0NjUbUsM Rs6LtpguRLOgijgZZDbJqLRNY5f+yh4engsVPvfAEK2NvfhycyDLoa1iXuiRkvyxWya5 +X+tUkPPZCg3etHUOedlZomkf3X/arsB6wLgB1gmKWcjnxKm2oRjZpaPrsQTOpPMorw7 HyxQ== 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=CFcsAXN25hCczwuYM243QmjwcIz9LRjZYzXWgZcxE2U=; b=FfWaUX/18vyE8mDrqFPlqezrB9wzkXQ7MexlaXdMBbylu9VY8cfakdHht7iMPaMT3N eEixyDgfLL9YYKPjTMY5tOvWsO6DRBQY9hVJYBe81/UGBM5WTNvneRlhRpEh7v3/uTxL ao2bpd9kf8V0vgTu03bM1k7lXOTpEpQcLCU3Cjs5FShtiNXGhfNxNvUhrdqMqbVGjhU3 fC2UgewQcgJ+PZZvfKmhtbGqnwkXFpfDAWLdLbtLzSRLqscnIaPkqDSlzK4j4h72zpvt hgxdoUzpTrxOeT0pJUizkpE8H38PN9C4wb0pPEz5rFxuPg0VgZ8nm4+QZK5aMj0ryKUg QAVg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=PuQJeYcd; 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 a13si21577669pfn.70.2019.04.24.20.00.41; Wed, 24 Apr 2019 20:01:12 -0700 (PDT) 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=PuQJeYcd; 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 S2392397AbfDXRiW (ORCPT + 99 others); Wed, 24 Apr 2019 13:38:22 -0400 Received: from mail.kernel.org ([198.145.29.99]:37474 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2392381AbfDXRiS (ORCPT ); Wed, 24 Apr 2019 13:38:18 -0400 Received: from localhost (62-193-50-229.as16211.net [62.193.50.229]) (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 4A46D218B0; Wed, 24 Apr 2019 17:38:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556127497; bh=zHSCUcAtNlSPFebN/+vW9er446FTkkzct/Tnmfi+F2k=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=PuQJeYcdjowUrBtAZqZuOtAkeNAzrKZqXf04/GDGcbPpwLM6/kyErKjgOaUWN5nNu JBuIatiKSBitIewsKEOrRC4kPBA3UUb5xKzJAdje9aXEM3z1H8C+98sahluCGQRjkc rotrSmrJydXo8ZfQ18BxJri/AEi1/DEnt1TbAFro= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, zhong jiang , Yang yingliang , Michal Hocko , David Hildenbrand , Oscar Salvador , Andrew Morton , Linus Torvalds Subject: [PATCH 5.0 112/115] mm/memory_hotplug: do not unlock after failing to take the device_hotplug_lock Date: Wed, 24 Apr 2019 19:10:48 +0200 Message-Id: <20190424170931.214760929@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190424170924.797924502@linuxfoundation.org> References: <20190424170924.797924502@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 commit 37803841c92d7b327147e0b1be3436423189e1cf upstream. When adding memory by probing a memory block in the sysfs interface, there is an obvious issue where we will unlock the device_hotplug_lock when we failed to takes it. That issue was introduced in 8df1d0e4a265 ("mm/memory_hotplug: make add_memory() take the device_hotplug_lock"). We should drop out in time when failing to take the device_hotplug_lock. Link: http://lkml.kernel.org/r/1554696437-9593-1-git-send-email-zhongjiang@huawei.com Fixes: 8df1d0e4a265 ("mm/memory_hotplug: make add_memory() take the device_hotplug_lock") Signed-off-by: zhong jiang Reported-by: Yang yingliang Acked-by: Michal Hocko Reviewed-by: David Hildenbrand Reviewed-by: Oscar Salvador Cc: Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman --- drivers/base/memory.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/base/memory.c +++ b/drivers/base/memory.c @@ -505,7 +505,7 @@ static ssize_t probe_store(struct device 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,