zhong jiang 37803841c9 mm/memory_hotplug: do not unlock after failing to take the device_hotplug_lock ... 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 8df1d0e4a2 ("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: 8df1d0e4a2 ("mm/memory_hotplug: make add_memory() take the device_hotplug_lock") Signed-off-by: zhong jiang <zhongjiang@huawei.com> Reported-by: Yang yingliang <yangyingliang@huawei.com> Acked-by: Michal Hocko <mhocko@suse.com> Reviewed-by: David Hildenbrand <david@redhat.com> Reviewed-by: Oscar Salvador <osalvador@suse.de> Cc: <stable@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2019-04-19 09:46:04 -07:00
..
firmware_loader	…
power	PM / Domains: Avoid a potential deadlock	2019-03-19 22:58:04 +01:00
regmap	…
test	…
Kconfig	…
Makefile	…
arch_topology.c	…
attribute_container.c	…
base.h	…
bus.c	…
cacheinfo.c	…
class.c	…
component.c	…
container.c	…
core.c	…
cpu.c	…
dd.c	…
devcon.c	…
devcoredump.c	…
devres.c	…
devtmpfs.c	…
driver.c	…
firmware.c	…
hypervisor.c	…
init.c	…
isa.c	…
map.c	…
memory.c	mm/memory_hotplug: do not unlock after failing to take the device_hotplug_lock	2019-04-19 09:46:04 -07:00
module.c	…
node.c	…
pinctrl.c	…
platform-msi.c	…
platform.c	…
property.c	…
soc.c	…
swnode.c	drivers: base: swnode: Make two functions static	2019-03-19 16:37:56 +01:00
syscore.c	…
topology.c	…
transport_class.c	…