The patch titled Subject: memory hotplug: release lock on an error path has been added to the -mm tree. Its filename is memory-hotplug-release-lock-on-an-error-path.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ From: Dan Carpenter <dan.carpenter@xxxxxxxxxx> Subject: memory hotplug: release lock on an error path We need to release the mutex here before returning. Signed-off-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx> Cc: Nathan Fontenot <nfont@xxxxxxxxxxxxxx> Cc: Greg KH <greg@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxx> --- drivers/base/memory.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/base/memory.c~memory-hotplug-release-lock-on-an-error-path drivers/base/memory.c --- a/drivers/base/memory.c~memory-hotplug-release-lock-on-an-error-path +++ a/drivers/base/memory.c @@ -299,7 +299,7 @@ static int memory_block_change_state(str for (i = 0; i < sections_per_block; i++) { ret = check_page_reservations(mem->start_section_nr + i); if (ret) - return ret; + goto out; } } _ Subject: Subject: memory hotplug: release lock on an error path Patches currently in -mm which might be from dan.carpenter@xxxxxxxxxx are linux-next.patch memory-hotplug-release-lock-on-an-error-path.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html