public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	Alexei Starovoitov <ast@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	Lorenzo Bianconi <lorenzo@kernel.org>, bpf <bpf@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH] bpf: fix reference count leak in bpf_prog_test_run_xdp()
Date: Thu, 08 Jan 2026 15:01:40 +0100	[thread overview]
Message-ID: <87qzs02ofv.fsf@toke.dk> (raw)
In-Reply-To: <af090e53-9d9b-4412-8acb-957733b3975c@I-love.SAKURA.ne.jp>

Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> writes:

> syzbot is reporting
>
>   unregister_netdevice: waiting for sit0 to become free. Usage count = 2
>
> problem. A debug printk() patch found that a refcount is obtained at
> xdp_convert_md_to_buff() from bpf_prog_test_run_xdp().
>
> According to commit ec94670fcb3b ("bpf: Support specifying ingress via
> xdp_md context in BPF_PROG_TEST_RUN"), the refcount obtained by
> xdp_convert_md_to_buff() will be released by xdp_convert_buff_to_md().
>
> Therefore, we can consider that the error handling path introduced by
> commit 1c1949982524 ("bpf: introduce frags support to
> bpf_prog_test_run_xdp()") forgot to call xdp_convert_buff_to_md().
>
> Reported-by: syzbot+881d65229ca4f9ae8c84@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=881d65229ca4f9ae8c84
> Fixes: 1c1949982524 ("bpf: introduce frags support to bpf_prog_test_run_xdp()")
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> ---
> Since syzbot has no reproducer for this problem, I can't test this patch.
>
>  net/bpf/test_run.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/net/bpf/test_run.c b/net/bpf/test_run.c
> index 655efac6f133..9a16293ba14b 100644
> --- a/net/bpf/test_run.c
> +++ b/net/bpf/test_run.c
> @@ -1355,13 +1355,13 @@ int bpf_prog_test_run_xdp(struct bpf_prog *prog, const union bpf_attr *kattr,
>  
>  			if (sinfo->nr_frags == MAX_SKB_FRAGS) {
>  				ret = -ENOMEM;
> -				goto out;
> +				goto out_put_dev;
>  			}
>  
>  			page = alloc_page(GFP_KERNEL);
>  			if (!page) {
>  				ret = -ENOMEM;
> -				goto out;
> +				goto out_put_dev;
>  			}
>  
>  			frag = &sinfo->frags[sinfo->nr_frags++];
> @@ -1373,7 +1373,7 @@ int bpf_prog_test_run_xdp(struct bpf_prog *prog, const union bpf_attr *kattr,
>  			if (copy_from_user(page_address(page), data_in + size,
>  					   data_len)) {
>  				ret = -EFAULT;
> -				goto out;
> +				goto out_put_dev;
>  			}
>  			sinfo->xdp_frags_size += data_len;
>  			size += data_len;
> @@ -1388,6 +1388,7 @@ int bpf_prog_test_run_xdp(struct bpf_prog *prog, const union bpf_attr *kattr,
>  		ret = bpf_test_run_xdp_live(prog, &xdp, repeat, batch_size, &duration);
>  	else
>  		ret = bpf_test_run(prog, &xdp, repeat, &retval, &duration, true);
> +out_put_dev:
>  	/* We convert the xdp_buff back to an xdp_md before checking the return
>  	 * code so the reference count of any held netdevice will be decremented
>  	 * even if the test run failed.

Hmm, this will end up call bpf_ctx_finish() in the error path, which I'm
not sure we want?

Could we just move the xdp_convert_md_to_buff() call to after the frags
have been copied? Not sure there's technically any dependency there,
even though it does look a little off?

-Toke


  reply	other threads:[~2026-01-08 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 12:36 [PATCH] bpf: fix reference count leak in bpf_prog_test_run_xdp() Tetsuo Handa
2026-01-08 14:01 ` Toke Høiland-Jørgensen [this message]
2026-01-08 14:18   ` Tetsuo Handa
2026-01-08 14:44     ` Toke Høiland-Jørgensen
2026-01-13  2:25 ` 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=87qzs02ofv.fsf@toke.dk \
    --to=toke@redhat.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=lorenzo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    /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