Re: [PATCH net v2 1/2] net: do not run out of frags in alloc_skb_with_frags()
From: Eric Dumazet
Date: Tue Nov 10 2026 - 15:06:15 EST
Le mar. 10 nov. 2026 à 09:31, Haishuang Yan
<yanhaishuang@xxxxxxxxxxxxxxxxxxxx> a écrit :
>
> alloc_skb_with_frags() rejects data_len above
> MAX_SKB_FRAGS * (PAGE_SIZE << order) up front, but two things can then
> make it need more than MAX_SKB_FRAGS frags, so it fails with -ENOBUFS
> for a data_len that passed the check:
>
> - It rounds the order down for the tail, so a tail of N pages is split
> into one frag per bit set in N. With order 3 and 4K pages, a 516536
> byte packet is 15 * 32K plus a 25016 byte tail, which becomes
> 16K + 8K + 4K, so 18 frags are needed although every page allocation
> succeeded. Sizes between about 480K and 540K can be affected.
>
> - When a high-order allocation fails, it lowers the order for this and
> every later chunk without checking that the frags left can still hold
> the rest. With order 3, a failure on the first chunk leaves room for
> at most 17 * 16K, so anything above 278528 bytes fails. These
> allocations are made without direct reclaim, so they fail whenever no
> order-3 page is free at that moment.
>
> Both came with the commit below. Before it, the limit was MAX_SKB_FRAGS
> pages, which fit at any order.
>
> tun hits this when vhost-net hands it a GSO packet of such a size from a
> guest. Nothing on the host limits the size of a guest's GSO packet to
> 64K: virtio_net_hdr has no total length, and tun_get_user() sizes the
> skb from the descriptor chain. Today's virtio-net drivers stay at 64K,
> but a guest can send bigger packets by raising its own TSO limit, and
> the host must not depend on the guest for that. Worse, vhost-net treats
> -ENOBUFS from sendmsg() as transient: handle_tx_copy() puts the
> descriptor back and retries it, so the vhost worker spins at 100% on
> the same packet and the device stops passing traffic in both
> directions.
This part is really a vhost-net/tun issue: handle_tx_copy() will spin
the same way on -ENOBUFS/-ENOMEM from real memory pressure, including
when the new direct reclaim attempt fails. Please trim this from the
changelog (or keep one sentence), this patch is about frag accounting
in alloc_skb_with_frags(), the retry loop deserves its own fix.
Also, this changelog is far too long. Ask your LLM to reduce it.
On an unmodified host, tun_get_user() returned -ENOBUFS
> about 620,000 times per second, the tap's rx_dropped counter climbed at
> the same rate, and this went on with no traffic until the VM was
> destroyed.
>
> This patch only fixes the frag accounting for packets that pass the
> data_len check. A larger frame from a guest can still make
> tun_alloc_skb() fail in alloc_skb() and vhost-net retry it; that is a
> separate problem in tun.
>
> Keep rounding the tail down when the remaining frags allow it, and use
> one page rounded up for the whole tail otherwise. This is never larger
> than the full-size chunks already used. When a high-order allocation
> fails, only lower the order if the frags left can still hold the rest.
> If they can't, try the same order once more with the caller's direct
> reclaim (with __GFP_NORETRY, so no OOM killer), and fail only if that
> fails too. An allocation that succeeds today takes the same path; the
> extra attempt only happens where it would have failed.
>
> The tail case was triggered while prototyping >64K TSO for virtio-net,
> with a one-line guest virtio_net change raising its TSO limit; the host
> was unmodified. The fallback case was pointed out in review of v1. The
> fix was tested with that reproducer, with page allocation fault
> injection on the vhost worker, and with the KUnit test in the next
> patch.
>
> Fixes: 09c2c90705bb ("net: allow alloc_skb_with_frags() to allocate bigger packets")
> Signed-off-by: Haishuang Yan <yanhaishuang@xxxxxxxxxxxxxxxxxxxx>
> ---
> Base: net a45dbf182137 ("ipvlan: make outbound skb headers writable").
> The tests below were run on net-next 303d91a15925, where
> alloc_skb_with_frags() is identical. KUnit on net 30c71476d842: net_core
> 20/20 (kunit.py, UML x86_64); with only patch 2 applied, the new test fails
> with err -105. allmodconfig W=1 build of net/core/ (arm64) on net
> a45dbf182137 with no warnings.
>
> Reproducer: x86_64 KVM host (i7-14700) running net-next 303d91a15925 with no
> local changes; vhost-net, a tap NIC with mrg_rxbuf=on and rx_queue_size=1024.
> The guest (net-next too) has a local one-line virtio_net change setting
> netif_set_tso_max_size(dev, GSO_MAX_SIZE), plus
> `ip link set dev ethX gso_max_size 524280 gso_ipv4_max_size 524280`; then
> a 10 s iperf3 guest -> host.
>
> Tail case, without this patch: iperf3 fails, one vhost worker stays at
> 99.9% CPU, tun_get_user() returns -105 (31014 times in 50 ms, kretprobe),
> the tap's rx_dropped goes up by 34M during the run and keeps climbing at
> ~690k/s with no traffic, and the guest can no longer ping the host until
> the VM is destroyed. With this patch: ~100 Gbit/s, no drops, and the vhost
> worker is idle afterwards; tun_get_user() handled 246783 packets, 237937
> of them between 480K and 540K, and none failed.
>
> Fallback case: CONFIG_FAIL_PAGE_ALLOC with min-order=3, ignore-gfp-wait=Y
> and task-filter set on the vhost workers, so only the order-3 attempts
> without direct reclaim fail. Failures of tun_get_user() during the run:
>
> probability tail fix only this patch
> 0% 99.0 Gbit/s, 0 96.0 Gbit/s, 0
> 5% 92.7 Gbit/s, 240418 99.8 Gbit/s, 0
> 20% 72.3 Gbit/s, 1152801 101.6 Gbit/s, 0
> 50% 0.1 Gbit/s, 4077173 99.5 Gbit/s, 0
> 100% iperf3 fails, 10573852 98.9 Gbit/s, 0
>
> With this patch the order-3 pages that the first attempt doesn't get come
> from the retry with direct reclaim (3546571 of them at 100%). Not tested:
> the retry failing as well, i.e. real memory pressure, and other callers
> of alloc_skb_with_frags() than tun.
>
> net/core/skbuff.c | 30 ++++++++++++++++++++++++++++--
> 1 file changed, 28 insertions(+), 2 deletions(-)
>
> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> index a7d555b3d2f28..da9025e6f0c3c 100644
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
> @@ -6906,15 +6906,41 @@ struct sk_buff *alloc_skb_with_frags(unsigned long header_len,
> while (data_len) {
> if (nr_frags == MAX_SKB_FRAGS)
> goto failure;
> - while (order && PAGE_ALIGN(data_len) < (PAGE_SIZE << order))
> - order--;
> + if (order && PAGE_ALIGN(data_len) < (PAGE_SIZE << order)) {
> + unsigned long pages = DIV_ROUND_UP(data_len, PAGE_SIZE);
> +
> + /* If splitting the rest into smaller pages would need
> + * more frags than we have left, use one larger page.
> + */
> + if (hweight_long(pages) > MAX_SKB_FRAGS - nr_frags)
> + order = order_base_2(pages);
> + else
> + order = ilog2(pages);
> + }
>
> if (order) {
> + unsigned long smaller = PAGE_SIZE << (order - 1);
> + bool can_shrink;
> +
> + /* Only fall back to smaller pages if the frags left
> + * can still hold the rest. If not, try this order
> + * once more with the caller's direct reclaim.
> + */
> + can_shrink = DIV_ROUND_UP(data_len, smaller) <=
> + MAX_SKB_FRAGS - nr_frags;
> +
> page = alloc_pages((gfp_mask & ~__GFP_DIRECT_RECLAIM) |
> __GFP_COMP |
> __GFP_NOWARN,
> order);
> + if (!page && !can_shrink &&
> + gfpflags_allow_blocking(gfp_mask))
> + page = alloc_pages(gfp_mask | __GFP_COMP |
> + __GFP_NOWARN | __GFP_NORETRY,
> + order);
> if (!page) {
> + if (!can_shrink)
> + goto failure;
> order--;
> continue;
> }
can_shrink is only needed when the first alloc_pages() failed, but you
compute it for every chunk, with a 64bit divide since the divisor is
not a constant.
Please move all this in the slow path, and use a shift. Something like
(untested):
if (order) {
page = alloc_pages((gfp_mask & ~__GFP_DIRECT_RECLAIM) |
__GFP_COMP |
__GFP_NOWARN,
order);
if (unlikely(!page)) {
unsigned int shift = PAGE_SHIFT + order - 1;
/* Can smaller pages hold the rest ? */
if (((data_len - 1) >> shift) + 1 <=
MAX_SKB_FRAGS - nr_frags) {
order--;
continue;
}
if (!gfpflags_allow_blocking(gfp_mask))
goto failure;
page = alloc_pages(gfp_mask | __GFP_COMP |
__GFP_NOWARN | __GFP_NORETRY,
order);
if (!page)
goto failure;
}
} else {
I find this also easier to follow than the
(!page && !can_shrink && ...) sequence.
The tail part looks good to me.