From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Neil Horman <nhorman@tuxdriver.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] vfio: correct system call error checking
Date: Tue, 17 Jun 2014 20:21:29 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B01AA37370@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1403031832-28540-1-git-send-email-nhorman@tuxdriver.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Neil Horman
> Sent: Tuesday, June 17, 2014 12:04 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] vfio: correct system call error checking
>
> Noticed today that ioctl error code return checking was incorrect in some of the
> vfio code. ioctl can return a negative value if the system detects an error
> before the target device/driver can produce a return code. The dpdk vfio code
> only checks specfically for the values that it expects, which leaves it open to
> accepting unexpected error codes as success. For instance, if the vfio layer
> noted that the iommu driver hadn't finished registering yet, it would return an
> -EINVAL error code, but the dpdk would accept that as success, becuase it
> wasn't
> 0.
>
> Fix this to specifically check for < 0 error codes
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> CC: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
> lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
> b/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
> index 4de6061..65aa8ad 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
> +++ b/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
> @@ -319,16 +319,16 @@ pci_vfio_get_container_fd(void)
>
> /* check VFIO API version */
> ret = ioctl(vfio_container_fd, VFIO_GET_API_VERSION);
> - if (ret != VFIO_API_VERSION) {
> - RTE_LOG(ERR, EAL, " unknown VFIO API version!\n");
> + if ((ret < 0) || (ret != VFIO_API_VERSION)) {
> + RTE_LOG(ERR, EAL, " unknown VFIO API version! errno
> = %d\n", errno);
> close(vfio_container_fd);
> return -1;
> }
Not sure how this change improves things, since the existing check will already trigger an error on all values <0. Can you please clarify why you think this needs to be changed?
>
> /* check if we support IOMMU type 1 */
> ret = ioctl(vfio_container_fd, VFIO_CHECK_EXTENSION,
> VFIO_TYPE1_IOMMU);
> - if (!ret) {
> - RTE_LOG(ERR, EAL, " unknown IOMMU driver!\n");
> + if (ret <= 0) {
> + RTE_LOG(ERR, EAL, " unknown IOMMU driver! errno =
> %d\n", errno);
> close(vfio_container_fd);
> return -1;
> }
Ack on this change part. The previously code was incorrect according to what I read in the docs for VFIO.
/Bruce
next prev parent reply other threads:[~2014-06-17 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 19:03 Neil Horman
2014-06-17 20:21 ` Richardson, Bruce [this message]
2014-06-17 20:40 ` Neil Horman
2014-06-17 20:43 ` Richardson, Bruce
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=59AF69C657FD0841A61C55336867B5B01AA37370@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.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).