DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] pci: remove unnecessary access() check
Date: Wed, 9 Oct 2019 10:11:18 +0200	[thread overview]
Message-ID: <CAJFAV8wJ9Sen59RBQYs=osANBp90wTxLD+PpofHeRj9XppOzCw@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8weXPO3zWzkv5eFxrxTMSX=vd2TpA68EyrQNi4t4WPB8A@mail.gmail.com>

On Mon, Aug 19, 2019 at 11:58 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Tue, Aug 13, 2019 at 5:38 PM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > Just open the sysfs file and handle failure, rather than
> > using access(). This eliminates Coverity warnings about
> > "time of check versus time of use"; although for this sysfs
> > file that is not really an issue anyway.
> >
> > Coverity ID: 347276

Fixed Coverity tag.
Added Fixes: + Cc: stable@dpdk.org

> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> Title prefix should be "bus/pci: " (check-git-log.sh).

Updated commit title.

>
>
> > ---
> >  drivers/bus/pci/linux/pci.c | 13 +++++++------
> >  1 file changed, 7 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/bus/pci/linux/pci.c b/drivers/bus/pci/linux/pci.c
> > index 43debaa25114..6c444aa7ae3d 100644
> > --- a/drivers/bus/pci/linux/pci.c
> > +++ b/drivers/bus/pci/linux/pci.c
> > @@ -512,18 +512,19 @@ pci_device_iommu_support_va(const struct rte_pci_device *dev)
> >                  "%s/" PCI_PRI_FMT "/iommu/intel-iommu/cap",
> >                  rte_pci_get_sysfs_path(), addr->domain, addr->bus, addr->devid,
> >                  addr->function);
> > -       if (access(filename, F_OK) == -1) {
> > -               /* We don't have an Intel IOMMU, assume VA supported*/
> > -               return true;
> > -       }
> >
> > -       /* We have an intel IOMMU */
> >         fp = fopen(filename, "r");
> >         if (fp == NULL) {
> > -               RTE_LOG(ERR, EAL, "%s(): can't open %s\n", __func__, filename);
> > +               /* We don't have an Intel IOMMU, assume VA supported*/
>
> Nit: missing a space before closing the comment.
>
> > +               if (errno == ENOENT)
> > +                       return true;
> > +
> > +               RTE_LOG(ERR, EAL, "%s(): can't open %s: %s\n",
> > +                       __func__, filename, strerror(errno));
> >                 return false;
> >         }
> >
> > +       /* We have an intel IOMMU */

s/intel/Intel/

> >         if (fscanf(fp, "%" PRIx64, &vtd_cap_reg) != 1) {
> >                 RTE_LOG(ERR, EAL, "%s(): can't read %s\n", __func__, filename);
> >                 fclose(fp);
> > --
> > 2.20.1
> >
>
> Reviewed-by: David Marchand <david.marchand@redhat.com>

Applied, thanks!



--
David Marchand


      reply	other threads:[~2019-10-09  8:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 15:38 Stephen Hemminger
2019-08-19  9:58 ` David Marchand
2019-10-09  8:11   ` David Marchand [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='CAJFAV8wJ9Sen59RBQYs=osANBp90wTxLD+PpofHeRj9XppOzCw@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).