From: Dongli Zhang <dongli.zhang@oracle.com>
To: Weiming Shi <bestswngs@gmail.com>, netdev@vger.kernel.org
Cc: willemdebruijn.kernel@gmail.com, jasowang@redhat.com,
pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
xmei5@asu.edu, linux-kernel@vger.kernel.org,
Si-Wei Liu <si-wei.liu@oracle.com>,
mst@redhat.com
Subject: Re: [PATCH net] tun: free page on build_skb failure in tun_xdp_one()
Date: Thu, 21 May 2026 14:02:42 -0700 [thread overview]
Message-ID: <525ef370-d0d7-4b6a-a338-328824f5b018@oracle.com> (raw)
In-Reply-To: <20260521163312.1479805-2-bestswngs@gmail.com>
On 2026-05-21 9:33 AM, Weiming Shi wrote:
> When build_skb() fails in tun_xdp_one(), the function sets ret to
> -ENOMEM and jumps to the out label, which returns without freeing the
> page that vhost_net_build_xdp() allocated for the frame. As with the
> short-frame rejection path, tun_sendmsg() discards the per-buffer error
> and still returns total_len, so vhost_tx_batch() takes the success path
> and never frees the page. Each build_skb() failure in a batch leaks one
> page-frag chunk.
>
> Free the page before taking the error path, matching the put_page() the
> other error exits of tun_xdp_one() already perform.
>
> Fixes: 043d222f93ab ("tuntap: accept an array of XDP buffs through sendmsg()")
> Reported-by: Xiang Mei <xmei5@asu.edu>
> Assisted-by: Claude:claude-opus-4-7
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
> ---
> drivers/net/tun.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> index b183189f1853..39e9f3390c91 100644
> --- a/drivers/net/tun.c
> +++ b/drivers/net/tun.c
> @@ -2437,6 +2437,7 @@ static int tun_xdp_one(struct tun_struct *tun,
> build:
> skb = build_skb(xdp->data_hard_start, buflen);
> if (!skb) {
> + put_page(virt_to_head_page(xdp->data));
> ret = -ENOMEM;
> goto out;
> }
The bug fix applies to both TAP and TUN.
TAP has a single patch, while TUN has two separate patches. I'm not sure which
approach is better.
[PATCH net] tap: free page on error paths in tap_get_user_xdp()
https://lore.kernel.org/netdev/20260521163230.1478627-2-bestswngs@gmail.com
[PATCH net] tun: free page on short-frame rejection in tun_xdp_one()
https://lore.kernel.org/all/20260520160020.375349-2-bestswngs@gmail.com
[PATCH net] tun: free page on build_skb failure in tun_xdp_one()
https://lore.kernel.org/netdev/20260521163312.1479805-2-bestswngs@gmail.com/
The bug fix looks good to me.
Reviewed-by: Dongli Zhang <dongli.zhang@oracle.com>
+ Michael and Si-Wei for FYI regarding vhost as well.
Thank you very much!
Dongli Zhang
next prev parent reply other threads:[~2026-05-21 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 16:33 Weiming Shi
2026-05-21 21:02 ` Dongli Zhang [this message]
2026-05-22 13:40 ` Willem de Bruijn
2026-05-22 17:20 ` patchwork-bot+netdevbpf
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=525ef370-d0d7-4b6a-a338-328824f5b018@oracle.com \
--to=dongli.zhang@oracle.com \
--cc=bestswngs@gmail.com \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=si-wei.liu@oracle.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xmei5@asu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®