diff options
author | Danilo Krummrich <dakr@kernel.org> | 2024-08-13 00:34:35 +0200 |
---|---|---|
committer | Danilo Krummrich <dakr@kernel.org> | 2024-09-10 14:15:07 +0200 |
commit | db8c7e4c95acc68f1e1cd51e0a7f1532c69a23c9 (patch) | |
tree | 89621b8c5d84eef223efdc1f7aaa1cbf3bebd25c /fs/btrfs/free-space-tree.c | |
parent | 38ca63f483e8b741983c4402252e6ed1b048e58f (diff) |
mm: krealloc: clarify valid usage of __GFP_ZEROmm/krealloc
Properly document that if __GFP_ZERO logic is requested, callers must
ensure that, starting with the initial memory allocation, every subsequent
call to this API for the same memory allocation is flagged with
__GFP_ZERO. Otherwise, it is possible that __GFP_ZERO is not fully
honored by this API.
Link: https://lkml.kernel.org/r/20240812223707.32049-2-dakr@kernel.org
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Acked-by: David Rientjes <rientjes@google.com>
Cc: Christoph Lameter <cl@linux.com>
Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Pekka Enberg <penberg@kernel.org>
Cc: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'fs/btrfs/free-space-tree.c')
0 files changed, 0 insertions, 0 deletions