diff options
| author | zhong jiang | 2019-04-08 06:07:17 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman | 2019-04-25 19:40:20 +0200 |
| commit | d2ab99403ee00d8014e651728a4702ea1ae5e52c (patch) | |
| tree | 7f697973980a03e9a6c2eca663d96f48c2a7d033 /drivers/base | |
| parent | driver core: Clarify which counterparts to use to device_add() (diff) | |
| download | kernel-qcow2-linux-d2ab99403ee00d8014e651728a4702ea1ae5e52c.tar.gz kernel-qcow2-linux-d2ab99403ee00d8014e651728a4702ea1ae5e52c.tar.xz kernel-qcow2-linux-d2ab99403ee00d8014e651728a4702ea1ae5e52c.zip | |
mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock
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 <yangyingliang@huawei.com>
Signed-off-by: zhong jiang <zhongjiang@huawei.com>
Reviewed-by: Oscar Salvador <osalvador@suse.de>
Reviewed-by: David Hildenbrand <david@redhat.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/base')
| -rw-r--r-- | drivers/base/memory.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/base/memory.c b/drivers/base/memory.c index cb8347500ce2..e49028a60429 100644 --- a/drivers/base/memory.c +++ b/drivers/base/memory.c @@ -506,7 +506,7 @@ static ssize_t 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, |