The patch titled
Subject: kvfree(): fix misleading comment
has been added to the -mm tree. Its filename is
kvfree-fix-misleading-comment.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/kvfree-fix-misleading-comment.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/kvfree-fix-misleading-comment.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: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
Subject: kvfree(): fix misleading comment
vfree() might sleep if called not in interrupt context. So does kvfree()
too. Fix misleading kvfree()'s comment about allowed context.
Link: http://lkml.kernel.org/r/20180914130512.10394-1-aryabinin@xxxxxxxxxxxxx
Fixes: 04b8e946075d ("mm/util.c: improve kvfree() kerneldoc")
Signed-off-by: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
Reviewed-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/util.c~kvfree-fix-misleading-comment
+++ a/mm/util.c
@@ -442,7 +442,7 @@ EXPORT_SYMBOL(kvmalloc_node);
* It is slightly more efficient to use kfree() or vfree() if you are certain
* that you know which one to use.
*
- * Context: Any context except NMI.
+ * Context: Either preemptible task context or not-NMI interrupt.
*/
void kvfree(const void *addr)
{
_
Patches currently in -mm which might be from aryabinin@xxxxxxxxxxxxx are
kvfree-fix-misleading-comment.patch
mm-vmalloc-improve-vfree-kerneldoc.patch
vfree-kvfree-add-debug-might-sleeps.patch
