public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
	lorenzo@kernel.org
Subject: Re: [PATCH bpf] libbpf: Fix bpf_xdp_query() in old kernels
Date: Mon, 27 Feb 2023 23:40:17 +0000	[thread overview]
Message-ID: <167754121711.19048.9342789016120820880.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230227224943.1153459-1-yhs@fb.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Mon, 27 Feb 2023 14:49:43 -0800 you wrote:
> Commit 04d58f1b26a4("libbpf: add API to get XDP/XSK supported features")
> added feature_flags to struct bpf_xdp_query_opts. If a user uses
> bpf_xdp_query_opts with feature_flags member, the bpf_xdp_query()
> will check whether 'netdev' family exists or not in the kernel.
> If it does not exist, the bpf_xdp_query() will return -ENOENT.
> 
> But 'netdev' family does not exist in old kernels as it is
> introduced in the same patch set as Commit 04d58f1b26a4.
> So old kernel with newer libbpf won't work properly with
> bpf_xdp_query() api call.
> 
> [...]

Here is the summary with links:
  - [bpf] libbpf: Fix bpf_xdp_query() in old kernels
    https://git.kernel.org/bpf/bpf-next/c/c8ee37bde402

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-02-27 23:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 22:49 [PATCH bpf] libbpf: Fix bpf_xdp_query() in old kernels Yonghong Song
2023-02-27 23:35 ` Andrii Nakryiko
2023-02-27 23:44   ` Yonghong Song
2023-02-28  9:05   ` Lorenzo Bianconi
2023-02-27 23: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=167754121711.19048.9342789016120820880.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=lorenzo@kernel.org \
    --cc=martin.lau@kernel.org \
    --cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox