From: David Heidelberg Without WARN_ONCE, the logs get spammed immediately after the boot, on devices as OnePlus 6T (Snapdragon 845). Fixes: 7179b2256315 ("mm/vmalloc: warn on invalid vmalloc gfp flags") Signed-off-by: David Heidelberg --- I'm not 100% sure this is the right solution, but having WARN_ONCE or rate limited warnings here helps a lot on devices as OnePlus 6 (sdm845). Please let me know what you think. --- mm/vmalloc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 49e0b68768d73..2a3ee17093d6e 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@ -3934,8 +3934,8 @@ static gfp_t vmalloc_fix_flags(gfp_t flags) gfp_t invalid_mask = flags & ~GFP_VMALLOC_SUPPORTED; flags &= GFP_VMALLOC_SUPPORTED; - WARN(1, "Unexpected gfp: %#x (%pGg). Fixing up to gfp: %#x (%pGg). Fix your code!\n", - invalid_mask, &invalid_mask, flags, &flags); + WARN_ONCE(1, "Unexpected gfp: %#x (%pGg). Fixing up to gfp: %#x (%pGg). Fix your code!\n" + invalid_mask, &invalid_mask, flags, &flags); return flags; } --- base-commit: 0c1c7a6a83feaf2cf182c52983ffe330ffb50280 change-id: 20251118-only-one-vmalloc-b8d997045791 Best regards, -- David Heidelberg