page_pool: always add GFP_NOWARN for ATOMIC allocations

[ Upstream commit f3b52167a0cb23b27414452fbc1278da2ee884fc ]

Driver authors often forget to add GFP_NOWARN for page allocation
from the datapath. This is annoying to users as OOMs are a fact
of life, and we pretty much expect network Rx to hit page allocation
failures during OOM. Make page pool add GFP_NOWARN for ATOMIC allocations
by default.

Reviewed-by: Mina Almasry <almasrymina@google.com>
Link: https://patch.msgid.link/20250912161703.361272-1-kuba@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>

diff --git a/net/core/page_pool.c b/net/core/page_pool.c
index 19c92aa04e5491d634db9a4f255fccf9739b7329..e224d2145eed97fe0515c049ebe5ffc30fc2fa9b 100644 (file)
--- a/net/core/page_pool.c
+++ b/net/core/page_pool.c
@@ -596,6 +596,12 @@ static noinline netmem_ref __page_pool_alloc_netmems_slow(struct page_pool *pool
        netmem_ref netmem;
        int i, nr_pages;
 
+       /* Unconditionally set NOWARN if allocating from NAPI.
+        * Drivers forget to set it, and OOM reports on packet Rx are useless.
+        */
+       if ((gfp & GFP_ATOMIC) == GFP_ATOMIC)
+               gfp |= __GFP_NOWARN;
+
        /* Don't support bulk alloc for high-order pages */
        if (unlikely(pp_order))
                return page_to_netmem(__page_pool_alloc_page_order(pool, gfp));