From: Maciej Fijalkowski <maciejromanfijalkowski@gmail.com>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
"Björn Töpel" <bjorn.topel@intel.com>,
magnus.karlsson@intel.com, magnus.karlsson@gmail.com,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf 1/2] xsk: fix to reject invalid flags in xsk_bind
Date: Fri, 8 Mar 2019 10:59:44 +0100 [thread overview]
Message-ID: <20190308105907.00000518@gmail.com> (raw)
In-Reply-To: <20190308075727.19358-2-bjorn.topel@gmail.com>
On Fri, 8 Mar 2019 08:57:26 +0100
Björn Töpel <bjorn.topel@gmail.com> wrote:
> From: Björn Töpel <bjorn.topel@intel.com>
>
> Passing a non-existing flag in the sxdp_flags member of struct
> sockaddr_xdp was, incorrectly, silently ignored. This patch addresses
> that behavior, and rejects any non-existing flags.
>
> We have examined existing user space code, and to our best knowledge,
> no one is relying on the current incorrect behavior. AF_XDP is still
> in its infancy, so from our perspective, the risk of breakage is very
> low, and addressing this problem now is important.
>
> Fixes: 965a99098443 ("xsk: add support for bind for Rx")
> Signed-off-by: Björn Töpel <bjorn.topel@intel.com>
> ---
> net/xdp/xsk.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/net/xdp/xsk.c b/net/xdp/xsk.c
> index 6697084e3fdf..a14e8864e4fa 100644
> --- a/net/xdp/xsk.c
> +++ b/net/xdp/xsk.c
> @@ -407,6 +407,10 @@ static int xsk_bind(struct socket *sock, struct sockaddr *addr, int addr_len)
> if (sxdp->sxdp_family != AF_XDP)
> return -EINVAL;
>
> + flags = sxdp->sxdp_flags;
> + if (flags & ~(XDP_SHARED_UMEM | XDP_COPY | XDP_ZEROCOPY))
> + return -EINVAL;
> +
What about setting more than one flag at a time? Is it allowed/make any sense?
After a quick look it seems that they exclude each other, e.g. you can't force
a zero copy and copy mode at the same time. And for XDP_SHARED_UMEM two
remaining flags can't be set.
So maybe check here also that only one particular flag is set by doing:
if (hweight32(flags & (XDP_SHARED_UMEM | XDP_COPY | XDP_ZEROCOPY)) > 1)
return -EINVAL;
just like we do it for IFLA_XDP_FLAGS in net/core/rtnetlink.c?
> mutex_lock(&xs->mutex);
> if (xs->dev) {
> err = -EBUSY;
> @@ -425,7 +429,6 @@ static int xsk_bind(struct socket *sock, struct sockaddr *addr, int addr_len)
> }
>
> qid = sxdp->sxdp_queue_id;
> - flags = sxdp->sxdp_flags;
>
> if (flags & XDP_SHARED_UMEM) {
> struct xdp_sock *umem_xs;
next prev parent reply other threads:[~2019-03-08 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 7:57 [PATCH bpf 0/2] xsk: fix non-existing flag/option behavior Björn Töpel
2019-03-08 7:57 ` [PATCH bpf 1/2] xsk: fix to reject invalid flags in xsk_bind Björn Töpel
2019-03-08 9:59 ` Maciej Fijalkowski [this message]
2019-03-08 10:11 ` Björn Töpel
2019-03-08 10:46 ` Maciej Fijalkowski
2019-03-08 11:06 ` Björn Töpel
2019-03-08 13:26 ` Daniel Borkmann
2019-03-08 7:57 ` [PATCH bpf 2/2] xsk: fix to reject invalid options in Tx descriptor Björn Töpel
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=20190308105907.00000518@gmail.com \
--to=maciejromanfijalkowski@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--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