From: Wei Huang <wei.huang@intel.com>
To: dev@dpdk.org, rosen.xu@intel.com, qi.z.zhang@intel.com
Cc: stable@dpdk.org, Wei Huang <wei.huang@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/2] raw/ifpga: fix coverity defects
Date: Fri, 30 Oct 2020 03:35:05 -0400 [thread overview]
Message-ID: <1604043307-20730-1-git-send-email-wei.huang@intel.com> (raw)
These two patches fix defects found by coverity scan.
Main changes from v3:
- Add coverity issue number
Main changes from v2:
- Fix coding style issue
Wei Huang (2):
raw/ifpga: terminate string filled by readlink with null
raw/ifpga: use trusted buffer to free
drivers/raw/ifpga/ifpga_rawdev.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
--
2.7.3
next reply other threads:[~2020-10-30 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 7:35 Wei Huang [this message]
2020-10-30 7:35 ` [dpdk-dev] [PATCH v3 1/2] raw/ifpga: terminate string filled by readlink with null Wei Huang
2020-10-30 7:35 ` [dpdk-dev] [PATCH v3 2/2] raw/ifpga: use trusted buffer to free Wei Huang
-- strict thread matches above, loose matches on Subject: below --
2020-10-30 0:21 [dpdk-dev] [PATCH v2 0/2] raw/ifpga: fix coverity defects Wei Huang
2020-11-02 12:23 ` Zhang, Qi Z
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=1604043307-20730-1-git-send-email-wei.huang@intel.com \
--to=wei.huang@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=rosen.xu@intel.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).