The quilt patch titled
Subject: mm: (k)vrealloc: document concurrency restrictions
has been removed from the -mm tree. Its filename was
mm-vmalloc-implement-vrealloc-fix-2.patch
This patch was dropped because it was folded into mm-vmalloc-implement-vrealloc.patch
------------------------------------------------------
From: Danilo Krummrich <dakr@xxxxxxxxxx>
Subject: mm: (k)vrealloc: document concurrency restrictions
Date: Thu, 25 Jul 2024 14:54:37 +0200
Document that concurrent calls to vrealloc() with itself or vfree() for
the same memory allocation are not permitted, since it leads to undefined
behavior.
Consequently, the same applies for kvrealloc(), hence also document it
for kvrealloc().
Link: https://lkml.kernel.org/r/20240725125442.4957-1-dakr@xxxxxxxxxx
Signed-off-by: Danilo Krummrich <dakr@xxxxxxxxxx>
Suggested-by: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Suggested-by: Uladzislau Rezki <urezki@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/vmalloc.c | 3 +++
1 file changed, 3 insertions(+)
--- a/mm/vmalloc.c~mm-vmalloc-implement-vrealloc-fix-2
+++ a/mm/vmalloc.c
@@ -4045,6 +4045,9 @@ EXPORT_SYMBOL(vzalloc_node_noprof);
* If @p is %NULL, vrealloc() behaves exactly like vmalloc(). If @size is 0 and
* @p is not a %NULL pointer, the object pointed to is freed.
*
+ * This function must not be called concurrently with itself or vfree() for the
+ * same memory allocation.
+ *
* Return: pointer to the allocated memory; %NULL if @size is zero or in case of
* failure
*/
_
Patches currently in -mm which might be from dakr@xxxxxxxxxx are
mm-vmalloc-implement-vrealloc.patch
mm-vmalloc-implement-vrealloc-fix-3.patch
mm-vmalloc-implement-vrealloc-fix-4.patch
mm-kvmalloc-align-kvrealloc-with-krealloc.patch
mm-kvmalloc-align-kvrealloc-with-krealloc-fix.patch
mm-kvmalloc-align-kvrealloc-with-krealloc-fix-2.patch
mm-kvmalloc-align-kvrealloc-with-krealloc-fix-3.patch
mm-krealloc-consider-spare-memory-for-__gfp_zero.patch
mm-krealloc-clarify-valid-usage-of-__gfp_zero.patch
