From: Andrey Ignatov <rdna@fb.com>
To: David Ahern <dsahern@kernel.org>
Cc: <daniel@iogearbox.net>, <ast@kernel.org>,
<netdev@vger.kernel.org>, David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH bpf] libbpf: Only check mode flags in get_xdp_id
Date: Mon, 20 Apr 2020 09:27:15 -0700 [thread overview]
Message-ID: <20200420162715.GA91440@rdna-mbp> (raw)
In-Reply-To: <20200420161843.46606-1-dsahern@kernel.org>
David Ahern <dsahern@kernel.org> [Mon, 2020-04-20 09:18 -0700]:
> From: David Ahern <dsahern@gmail.com>
>
> The commit in the Fixes tag changed get_xdp_id to only return prog_id
> if flags is 0, but there are other XDP flags than the modes - e.g.,
> XDP_FLAGS_UPDATE_IF_NOEXIST. Since the intention was only to look at
> MODE flags, clear other ones before checking if flags is 0.
>
> Fixes: f07cbad29741 ("libbpf: Fix bpf_get_link_xdp_id flags handling")
> Signed-off-by: David Ahern <dsahern@gmail.com>
> Cc: Andrey Ignatov <rdna@fb.com>
Makes sense. Thanks.
Acked-by: Andrey Ignatov <rdna@fb.com>
> ---
> tools/lib/bpf/netlink.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/lib/bpf/netlink.c b/tools/lib/bpf/netlink.c
> index 342acacf7cda..692749d87348 100644
> --- a/tools/lib/bpf/netlink.c
> +++ b/tools/lib/bpf/netlink.c
> @@ -352,6 +352,8 @@ int bpf_get_link_xdp_egress_info(int ifindex, struct xdp_link_info *info,
>
> static __u32 get_xdp_id(struct xdp_link_info *info, __u32 flags)
> {
> + flags &= XDP_FLAGS_MODES;
> +
> if (info->attach_mode != XDP_ATTACHED_MULTI && !flags)
> return info->prog_id;
> if (flags & XDP_FLAGS_DRV_MODE)
> --
> 2.20.1
>
--
Andrey Ignatov
next prev parent reply other threads:[~2020-04-20 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 16:18 [PATCH bpf] libbpf: Only check mode flags in get_xdp_id David Ahern
2020-04-20 16:27 ` Andrey Ignatov [this message]
2020-04-23 5:08 ` Alexei Starovoitov
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=20200420162715.GA91440@rdna-mbp \
--to=rdna@fb.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
/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