The patch titled
Subject: mm: warn about vfree from atomic context
has been removed from the -mm tree. Its filename was
mm-warn-about-vfree-from-atomic-context.patch
This patch was dropped because it was nacked
------------------------------------------------------
From: Christoph Hellwig <hch@xxxxxx>
Subject: mm: warn about vfree from atomic context
We can't handle vfree itself from atomic context, but callers
can explicitly use vfree_atomic instead, which defers the actual
vfree to a workqueue. Unfortunately in_atomic does not work
on non-preemptible kernels, so we can't just do the right thing
by default.
Link: http://lkml.kernel.org/r/1479474236-4139-8-git-send-email-hch@xxxxxx
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Cc: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
Cc: Joel Fernandes <joelaf@xxxxxxxxxx>
Cc: Jisheng Zhang <jszhang@xxxxxxxxxxx>
Cc: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
Cc: John Dias <joaodias@xxxxxxxxxx>
Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Cc: "H. Peter Anvin" <hpa@xxxxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/vmalloc.c | 1 +
1 file changed, 1 insertion(+)
diff -puN mm/vmalloc.c~mm-warn-about-vfree-from-atomic-context mm/vmalloc.c
--- a/mm/vmalloc.c~mm-warn-about-vfree-from-atomic-context
+++ a/mm/vmalloc.c
@@ -1530,6 +1530,7 @@ void vfree_atomic(const void *addr)
void vfree(const void *addr)
{
BUG_ON(in_nmi());
+ WARN_ON_ONCE(in_atomic());
kmemleak_free(addr);
_
Patches currently in -mm which might be from hch@xxxxxx are
mm-remove-free_unmap_vmap_area_noflush.patch
mm-remove-free_unmap_vmap_area_addr.patch
mm-refactor-__purge_vmap_area_lazy.patch
mm-mark-all-calls-into-the-vmalloc-subsystem-as-potentially-sleeping.patch
mm-turn-vmap_purge_lock-into-a-mutex.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
