From: patchwork-bot+netdevbpf@kernel.org
To: Rong Zhang <i@rong.moe>
Cc: hawk@kernel.org, ilias.apalodimas@linaro.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, almasrymina@google.com,
toke@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: page_pool: Remove zone/policy GFP flags when allocating XArray entries
Date: Sat, 22 Aug 2026 20:40:11 +0000 [thread overview]
Message-ID: <178743121165.1821669.13695262349197988811.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260821-page-pool-xa-drop-dma32-v1-1-6eab295c3478@rong.moe>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 21 Aug 2026 01:41:25 +0800 you wrote:
> Net drivers request GFP flags according to both the current context and
> the device constraints, but the XArray entry itself is by no mean used
> by the device. Passing though device constraints to XArray allocation is
> a bug and will be warned and fixed up by slab, e.g.:
>
> Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0x82820 (GFP_ATOMIC|__GFP_NOWARN|__GFP_NOMEMALLOC). Fix your code!
> CPU: 2 UID: 0 PID: 1071629 Comm: kworker/u80:1 Not tainted 7.2.0-rc7+ #1 PREEMPT(lazy)
> Hardware name: LENOVO 21Q4/LNVNB161216, BIOS PXCN27WW 10/20/2025
> Workqueue: mt76 mt792x_pm_wake_work [mt792x_lib]
> Call Trace:
> <TASK>
> dump_stack_lvl+0x6e/0x90
> kmalloc_fix_flags+0x4d/0x6a
> refill_objects+0x10a/0x330
> __pcs_replace_empty_main+0x292/0x5c0
> kmem_cache_alloc_lru_noprof+0x4c2/0x680
> ? __xas_nomem+0x3a/0x120
> __xas_nomem+0x3a/0x120
> __xa_alloc+0xd4/0x190
> page_pool_dma_map+0xef/0x400
> __page_pool_alloc_netmems_slow+0xed/0x480
> ? lock_release+0x280/0x490
> page_pool_alloc_frag_netmem+0xe0/0x3a0
> page_pool_alloc_frag+0xe/0x20
> mt76_dma_rx_fill_buf+0x1f6/0x580 [mt76]
> mt76_dma_rx_reset+0x1cf/0x230 [mt76]
> mt792x_wpdma_reset+0x183/0x1b0 [mt792x_lib]
> mt792x_wpdma_reinit_cond+0x5e/0xa0 [mt792x_lib]
> mt792xe_mcu_drv_pmctrl+0x28/0x60 [mt792x_lib]
> mt792x_mcu_drv_pmctrl+0x3e/0x90 [mt792x_lib]
> mt792x_pm_wake_work+0x2d/0x1d0 [mt792x_lib]
> ? process_one_work+0x20e/0x600
> process_one_work+0x230/0x600
> ? process_one_work+0x256/0x600
> worker_thread+0x1ec/0x3c0
> ? rescuer_thread+0x610/0x610
> kthread+0xf2/0x130
> ? kthread_affine_node+0x140/0x140
> ret_from_fork+0x2a5/0x380
> ? kthread_affine_node+0x140/0x140
> ret_from_fork_asm+0x11/0x20
> </TASK>
>
> [...]
Here is the summary with links:
- net: page_pool: Remove zone/policy GFP flags when allocating XArray entries
https://git.kernel.org/netdev/net/c/039f248a6cc1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-22 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 17:41 [PATCH] net: page_pool: Remove zone/policy GFP flags when allocating XArray entries Rong Zhang
2026-08-20 20:01 ` Toke Høiland-Jørgensen
2026-08-22 20:40 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178743121165.1821669.13695262349197988811.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=i@rong.moe \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toke@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.