The patch titled Subject: mm/vmalloc.c: remove might_sleep() in __remove_vm_area() has been added to the -mm tree. Its filename is mm-remove-might_sleep-in-__remove_vm_area.patch This patch should soon appear at http://ozlabs.org/~akpm/mmots/broken-out/mm-remove-might_sleep-in-__remove_vm_area.patch and later at http://ozlabs.org/~akpm/mmotm/broken-out/mm-remove-might_sleep-in-__remove_vm_area.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/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Roman Gushchin <guro@xxxxxx> Subject: mm/vmalloc.c: remove might_sleep() in __remove_vm_area() __remove_vm_area() has a redundant might_sleep() call, which isn't really required, because the only place it can sleep is vfree() and it already contains might_sleep_if(!in_interrupt()). Link: http://lkml.kernel.org/r/20190417230219.GA5538@xxxxxxxxxxxxxxxxxxxxxxxxxx Signed-off-by: Roman Gushchin <guro@xxxxxx> Suggested-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> Cc: Johannes Weiner <hannes@xxxxxxxxxxx> Cc: Vlastimil Babka <vbabka@xxxxxxx> Cc: Matthew Wilcox <willy@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/vmalloc.c | 2 -- 1 file changed, 2 deletions(-) --- a/mm/vmalloc.c~mm-remove-might_sleep-in-__remove_vm_area +++ a/mm/vmalloc.c @@ -1482,8 +1482,6 @@ static struct vm_struct *__remove_vm_are { struct vm_struct *vm = va->vm; - might_sleep(); - spin_lock(&vmap_area_lock); va->vm = NULL; va->flags &= ~VM_VM_AREA; _ Patches currently in -mm which might be from guro@xxxxxx are mm-remove-might_sleep-in-__remove_vm_area.patch