* [PATCH] vmalloc: Update __vmalloc_node_noprof() documentation
@ 2025-10-13 17:42 Uladzislau Rezki (Sony)
2025-10-14 10:49 ` Baoquan He
0 siblings, 1 reply; 2+ messages in thread
From: Uladzislau Rezki (Sony) @ 2025-10-13 17:42 UTC (permalink / raw)
To: linux-mm, Andrew Morton; +Cc: Michal Hocko, Baoquan He, LKML, Uladzislau Rezki
The kernel-doc for the __vmalloc_node_noprof() incorrectly states
that __GFP_NOFAIL reclaim modifier is not supported. In fact it has
been supported since commit 9376130c390a ("mm/vmalloc: add support
for __GFP_NOFAIL").
To avoid duplication and future drift, point this helper's doc to
__vmalloc_node_range_noprof() for details and the full description.
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
---
mm/vmalloc.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 9a63c91c6150..c31fa69cc530 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -4027,11 +4027,8 @@ void *__vmalloc_node_range_noprof(unsigned long size, unsigned long align,
* Allocate enough pages to cover @size from the page level allocator with
* @gfp_mask flags. Map them into contiguous kernel virtual space.
*
- * Reclaim modifiers in @gfp_mask - __GFP_NORETRY, __GFP_RETRY_MAYFAIL
- * and __GFP_NOFAIL are not supported
- *
- * Any use of gfp flags outside of GFP_KERNEL should be consulted
- * with mm people.
+ * Semantics of @gfp_mask(including reclaim/retry modifiers such as
+ * __GFP_NOFAIL) are the same as in __vmalloc_node_range_noprof().
*
* Return: pointer to the allocated memory or %NULL on error
*/
--
2.47.3
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] vmalloc: Update __vmalloc_node_noprof() documentation
2025-10-13 17:42 [PATCH] vmalloc: Update __vmalloc_node_noprof() documentation Uladzislau Rezki (Sony)
@ 2025-10-14 10:49 ` Baoquan He
0 siblings, 0 replies; 2+ messages in thread
From: Baoquan He @ 2025-10-14 10:49 UTC (permalink / raw)
To: Uladzislau Rezki (Sony); +Cc: linux-mm, Andrew Morton, Michal Hocko, LKML
On 10/13/25 at 07:42pm, Uladzislau Rezki (Sony) wrote:
> The kernel-doc for the __vmalloc_node_noprof() incorrectly states
> that __GFP_NOFAIL reclaim modifier is not supported. In fact it has
> been supported since commit 9376130c390a ("mm/vmalloc: add support
> for __GFP_NOFAIL").
>
> To avoid duplication and future drift, point this helper's doc to
> __vmalloc_node_range_noprof() for details and the full description.
>
> Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> ---
> mm/vmalloc.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
Reviewed-by: Baoquan He <bhe@redhat.com>
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 9a63c91c6150..c31fa69cc530 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -4027,11 +4027,8 @@ void *__vmalloc_node_range_noprof(unsigned long size, unsigned long align,
> * Allocate enough pages to cover @size from the page level allocator with
> * @gfp_mask flags. Map them into contiguous kernel virtual space.
> *
> - * Reclaim modifiers in @gfp_mask - __GFP_NORETRY, __GFP_RETRY_MAYFAIL
> - * and __GFP_NOFAIL are not supported
> - *
> - * Any use of gfp flags outside of GFP_KERNEL should be consulted
> - * with mm people.
> + * Semantics of @gfp_mask(including reclaim/retry modifiers such as
> + * __GFP_NOFAIL) are the same as in __vmalloc_node_range_noprof().
> *
> * Return: pointer to the allocated memory or %NULL on error
> */
> --
> 2.47.3
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-10-14 10:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-10-13 17:42 [PATCH] vmalloc: Update __vmalloc_node_noprof() documentation Uladzislau Rezki (Sony)
2025-10-14 10:49 ` Baoquan He
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox