From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Herakliusz Lipiec <herakliusz.lipiec@intel.com>,
Keith Wiles <keith.wiles@intel.com>
Cc: dev@dpdk.org, rasland@mellanox.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v3] net/tap: fix potential buffer overrun
Date: Thu, 2 May 2019 17:31:57 +0100 [thread overview]
Message-ID: <3eadb1fe-ff44-d75e-1c77-fb916f6334fa@intel.com> (raw)
In-Reply-To: <20190429173121.1025-1-herakliusz.lipiec@intel.com>
On 4/29/2019 6:31 PM, Herakliusz Lipiec wrote:
> When secondary to primary process synchronization occours
> there is no check for number of fds which could cause buffer overrun.
>
> Bugzilla ID: 252
> Fixes: c9aa56edec8e ("net/tap: access primary process queues from secondary")
> Cc: rasland@mellanox.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
Carrying from prev version:
Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-05-02 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 16:47 [dpdk-stable] [PATCH] " Herakliusz Lipiec
2019-04-25 17:17 ` [dpdk-stable] [PATCH v2] " Herakliusz Lipiec
2019-04-29 13:32 ` [dpdk-stable] [dpdk-dev] " Burakov, Anatoly
2019-04-29 13:53 ` Ferruh Yigit
2019-04-29 14:02 ` Burakov, Anatoly
2019-04-30 10:42 ` Ferruh Yigit
2019-04-29 13:58 ` [dpdk-stable] " Wiles, Keith
2019-04-29 14:05 ` [dpdk-stable] [dpdk-dev] " Burakov, Anatoly
2019-04-29 17:31 ` [dpdk-stable] [PATCH v3] " Herakliusz Lipiec
2019-05-02 16:31 ` Ferruh Yigit [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=3eadb1fe-ff44-d75e-1c77-fb916f6334fa@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=herakliusz.lipiec@intel.com \
--cc=keith.wiles@intel.com \
--cc=rasland@mellanox.com \
--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).