diff options
| author | zhong jiang <zhongjiang@huawei.com> | 2019-04-08 12:07:17 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-04-25 19:40:20 +0200 |
| commit | d2ab99403ee00d8014e651728a4702ea1ae5e52c (patch) | |
| tree | 7f697973980a03e9a6c2eca663d96f48c2a7d033 /Kbuild | |
| parent | affada726cad2402804ec29fc000276c7dc23b95 (diff) | |
| download | linux-stable-d2ab99403ee00d8014e651728a4702ea1ae5e52c.tar.gz linux-stable-d2ab99403ee00d8014e651728a4702ea1ae5e52c.tar.bz2 linux-stable-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 'Kbuild')
0 files changed, 0 insertions, 0 deletions