* Re: + mm-vmalloc-be-more-explicit-about-supported-gfp-flags.patch added to -mm tree
[not found] <20211020223613.z_R-mXCPH%akpm@linux-foundation.org>
@ 2021-10-21 10:18 ` Michal Hocko
0 siblings, 0 replies; only message in thread
From: Michal Hocko @ 2021-10-21 10:18 UTC (permalink / raw)
To: linux-kernel; +Cc: david, hch, idryomov, jlayton, mm-commits, neilb, urezki
On Wed 20-10-21 15:36:13, Andrew Morton wrote:
> From: Michal Hocko <mhocko@suse.com>
> Subject: mm/vmalloc: be more explicit about supported gfp flags
>
> The core of the vmalloc allocator __vmalloc_area_node doesn't say anything
> about gfp mask argument. Not all gfp flags are supported though. Be more
> explicit about constraints.
>
> Link: https://lkml.kernel.org/r/20211020082545.4830-1-mhocko@kernel.org
> Signed-off-by: Michal Hocko <mhocko@suse.com>
> Cc: Dave Chinner <david@fromorbit.com>
> Cc: Neil Brown <neilb@suse.de>
> Cc: Christoph Hellwig <hch@infradead.org>
> Cc: Uladzislau Rezki <urezki@gmail.com>
> Cc: Ilya Dryomov <idryomov@gmail.com>
> Cc: Jeff Layton <jlayton@kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
I haven't see other patches from the series to be applied to your tree
and without them this is not really correct.
> ---
>
> mm/vmalloc.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> --- a/mm/vmalloc.c~mm-vmalloc-be-more-explicit-about-supported-gfp-flags
> +++ a/mm/vmalloc.c
> @@ -2990,8 +2990,16 @@ fail:
> * @caller: caller's return address
> *
> * Allocate enough pages to cover @size from the page level
> - * allocator with @gfp_mask flags. Map them into contiguous
> - * kernel virtual space, using a pagetable protection of @prot.
> + * allocator with @gfp_mask flags. Please note that the full set of gfp
> + * flags are not supported. GFP_KERNEL would be a preferred allocation mode
> + * but GFP_NOFS and GFP_NOIO are supported as well. Zone modifiers are not
> + * supported. From the reclaim modifiers__GFP_DIRECT_RECLAIM is required (aka
> + * GFP_NOWAIT is not supported) and only __GFP_NOFAIL is supported (aka
> + * __GFP_NORETRY and __GFP_RETRY_MAYFAIL are not supported).
> + * __GFP_NOWARN can be used to suppress error messages about failures.
> + *
> + * Map them into contiguous kernel virtual space, using a pagetable
> + * protection of @prot.
> *
> * Return: the address of the area or %NULL on failure
> */
> _
>
> Patches currently in -mm which might be from mhocko@suse.com are
>
> mm-vmalloc-be-more-explicit-about-supported-gfp-flags.patch
--
Michal Hocko
SUSE Labs
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-10-21 10:18 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20211020223613.z_R-mXCPH%akpm@linux-foundation.org>
2021-10-21 10:18 ` + mm-vmalloc-be-more-explicit-about-supported-gfp-flags.patch added to -mm tree Michal Hocko
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox