DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "jerinj@marvell.com" <jerinj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] bpf: fix to allow ptr stack program type
Date: Mon, 12 Aug 2019 08:49:34 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258018115CEAE@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <20190809162919.5967-1-jerinj@marvell.com>

Hi Jerin,

> 
> bpf_validate does not allow to execute
> RTE_BPF_ARG_PTR_STACK for no reason.

I believe there is a reason,
ARG_PTR_STACK is reserved for memory within BPF program internal stack only.
User that calls BPF program should never pass parameter with that type.
If the user allocates parameter for bpf function on the stack, he can
still use RTE_BPF_ARG_PTR for it.
Konstantin

> Fix it by enhancing the prog_arg.type check.
> 
> Fixes: 6e12ec4c4d6d ("bpf: add more checks")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> ---
>  lib/librte_bpf/bpf_validate.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/lib/librte_bpf/bpf_validate.c b/lib/librte_bpf/bpf_validate.c
> index 0cf41fa27..c75777b6d 100644
> --- a/lib/librte_bpf/bpf_validate.c
> +++ b/lib/librte_bpf/bpf_validate.c
> @@ -2216,6 +2216,7 @@ bpf_validate(struct rte_bpf *bpf)
> 
>  	/* check input argument type, don't allow mbuf ptr on 32-bit */
>  	if (bpf->prm.prog_arg.type != RTE_BPF_ARG_RAW &&
> +			bpf->prm.prog_arg.type != RTE_BPF_ARG_PTR_STACK &&
>  			bpf->prm.prog_arg.type != RTE_BPF_ARG_PTR &&
>  			(sizeof(uint64_t) != sizeof(uintptr_t) ||
>  			bpf->prm.prog_arg.type != RTE_BPF_ARG_PTR_MBUF)) {
> --
> 2.22.0


  reply	other threads:[~2019-08-12  8:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 16:29 jerinj
2019-08-12  8:49 ` Ananyev, Konstantin [this message]
2019-08-12 10:34   ` Jerin Jacob Kollanukkaran
2019-08-12 11:37     ` Ananyev, Konstantin
2019-08-13  3:31       ` Jerin Jacob Kollanukkaran
2019-08-13  6:50         ` Ananyev, Konstantin

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=2601191342CEEE43887BDE71AB977258018115CEAE@irsmsx105.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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;
as well as URLs for NNTP newsgroup(s).