patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Li Qiang <liq3ea@163.com>
Cc: stable@dpdk.org, "Xu, Rosen" <rosen.xu@intel.com>,
	"Zhang, Tianfei" <tianfei.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"liq3ea@gmail.com" <liq3ea@gmail.com>
Subject: Re: [dpdk-stable] [PATCH v3] drivers: ifpga_rawdev: fix fd leak in rte_fpga_do_pr
Date: Thu, 02 May 2019 23:39:49 +0200	[thread overview]
Message-ID: <1646069.sVXKPgHgFL@xps> (raw)
In-Reply-To: <0E78D399C70DA940A335608C6ED296D73A6B02B5@SHSMSX104.ccr.corp.intel.com>

> > In rte_fpga_do_pr() function, if 'stat' return error the 'file_fd' is never closed
> > thus leading a fd leak. This patch avoids this.
> > 
> > Coverity issue: 279441
> > Fixes: ef1e8ede3da59e("raw/ifpga: add Intel FPGA bus rawdev driver")
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Li Qiang <liq3ea@163.com>
> 
> Acked-by: Rosen Xu <rosen.xu@intel.com>

Applied, thanks




  reply	other threads:[~2019-05-02 21:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16  5:05 Li Qiang
2019-04-16  7:02 ` Xu, Rosen
2019-05-02 21:39   ` Thomas Monjalon [this message]
2019-04-16  7:52 Li Qiang

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=1646069.sVXKPgHgFL@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=liq3ea@163.com \
    --cc=liq3ea@gmail.com \
    --cc=rosen.xu@intel.com \
    --cc=stable@dpdk.org \
    --cc=tianfei.zhang@intel.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).