From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Timmons C. Player" <timmons.player@spirent.com>, linville@tuxdriver.com
Cc: dev@dpdk.org, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/af_packet: fix fd use after free
Date: Mon, 9 Jan 2017 11:55:12 +0000 [thread overview]
Message-ID: <9109d76d-0d94-2ce4-b030-e2d819709998@intel.com> (raw)
In-Reply-To: <1483626815-476-1-git-send-email-timmons.player@spirent.com>
On 1/5/2017 2:33 PM, Timmons C. Player wrote:
> When using the same file descriptor for both rx and tx, the
> eth_dev_stop function would close the same fd twice. This
> change prevents that from happening.
>
> Signed-off-by: Timmons C. Player <timmons.player@spirent.com>
Fixes: 364e08f2bbc0 ("af_packet: add PMD for AF_PACKET-based virtual
devices")
CC:stable@dpdk.org
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
next parent reply other threads:[~2017-01-09 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1483626815-476-1-git-send-email-timmons.player@spirent.com>
2017-01-09 11:55 ` Ferruh Yigit [this message]
2017-01-09 12:04 ` Ferruh Yigit
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=9109d76d-0d94-2ce4-b030-e2d819709998@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=linville@tuxdriver.com \
--cc=stable@dpdk.org \
--cc=timmons.player@spirent.com \
/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).