mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Woojin Ji <random6.xyz@gmail.com>
Cc: yonghong.song@linux.dev, andrii@kernel.org, ast@kernel.org,
	bpf@vger.kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
	jolsa@kernel.org, kuba@kernel.org, linux-kernel@vger.kernel.org,
	martin.lau@linux.dev, memxor@gmail.com, qmo@kernel.org,
	sdf@fomichev.me, song@kernel.org
Subject: Re: [PATCH bpf v2] bpftool: Use libbpf error code for flow dissector query
Date: Wed, 03 Jun 2026 22:40:05 +0000	[thread overview]
Message-ID: <178052640576.2032852.14873699170740166631.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260603003339.33791-1-random6.xyz@gmail.com>

Hello:

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

On Wed,  3 Jun 2026 09:33:39 +0900 you wrote:
> bpf_prog_query() returns a negative errno on failure.
> query_flow_dissector() currently closes the namespace fd and then reads
> errno to decide whether -EINVAL means that the running kernel does not
> support flow dissector queries.
> 
> That errno check controls behavior, not just diagnostics: -EINVAL is
> handled as a non-fatal old-kernel case, while any other error makes bpftool
> net fail.
> 
> [...]

Here is the summary with links:
  - [bpf,v2] bpftool: Use libbpf error code for flow dissector query
    https://git.kernel.org/bpf/bpf-next/c/8a7f2bff2165

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



      parent reply	other threads:[~2026-06-03 22:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 17:03 [PATCH bpf] " Woojin Ji
2026-06-02 19:43 ` Yonghong Song
2026-06-02 19:49   ` Yonghong Song
2026-06-03  0:15     ` Woojin Ji
2026-06-03  0:33     ` [PATCH bpf v2] " Woojin Ji
2026-06-03  1:45       ` Leon Hwang
2026-06-03  3:01       ` Yonghong Song
2026-06-03  9:28         ` Quentin Monnet
2026-06-03 22: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=178052640576.2032852.14873699170740166631.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=eddyz87@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=qmo@kernel.org \
    --cc=random6.xyz@gmail.com \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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
Powered by JetHome