From: Thomas Monjalon <thomas@monjalon.net>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, michel@digirati.com.br, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] bpf: fix invalid array size
Date: Thu, 27 Jun 2019 23:16:04 +0200 [thread overview]
Message-ID: <1574152.yE7rOHmIcX@xps> (raw)
In-Reply-To: <20190621142649.14125-1-konstantin.ananyev@intel.com>
21/06/2019 16:26, Konstantin Ananyev:
> Array ins_chk in lib/librte_bpf/bpf_validate.c has 255 entries.
> So the instruction with opcode == 255 will reading beyond array
> boundaries.
> For more details please refer to:
> https://bugs.dpdk.org/show_bug.cgi?id=283
>
> Fixes: 6e12ec4c4d6d ("bpf: add more checks")
> Cc: stable@dpdk.org
>
> Reported-by: Michel Machado <michel@digirati.com.br>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-06-27 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 14:26 Konstantin Ananyev
2019-06-27 21:16 ` Thomas Monjalon [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=1574152.yE7rOHmIcX@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=michel@digirati.com.br \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).