From: Michael Haeuptle <michael.haeuptle@hpe.com>
To: dev@dpdk.org
Cc: xiao.w.wang@intel.com, stable@dpdk.org
Subject: [dpdk-dev] [PATCH] eal: Fixes VFIO/sysfs race condition
Date: Mon, 6 Apr 2020 22:23:23 +0000 [thread overview]
Message-ID: <20200406222323.18609-1-michael.haeuptle@hpe.com> (raw)
This fix treats a 0 return value from vfio_open_group_fd
in vfio_get_group_fd as the intended error condition instead
of putting an incorrect 0 file descriptor in the vfio_group table.
Sometimes, the creation of device files in sysfs is not
instantaneously causing vfio_open_groupfd to return 0.
This has been observed when hot removing/adding multiple
NVMe devices (>=4).
Fixes: 340b7bb8d583 ("vfio: extend data structure for multi container")
Cc: xiao.w.wang@intel.com
Cc: stable@dpdk.org
Signed-off-by: Michael Haeuptle <michael.haeuptle@hpe.com>
---
lib/librte_eal/linux/eal_vfio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/librte_eal/linux/eal_vfio.c b/lib/librte_eal/linux/eal_vfio.c
index 4502aefed..1979f6fdd 100644
--- a/lib/librte_eal/linux/eal_vfio.c
+++ b/lib/librte_eal/linux/eal_vfio.c
@@ -379,7 +379,7 @@ vfio_get_group_fd(struct vfio_config *vfio_cfg,
}
vfio_group_fd = vfio_open_group_fd(iommu_group_num);
- if (vfio_group_fd < 0) {
+ if (vfio_group_fd <= 0) {
RTE_LOG(ERR, EAL, "Failed to open group %d\n", iommu_group_num);
return -1;
}
--
2.18.2
next reply other threads:[~2020-04-06 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 22:23 Michael Haeuptle [this message]
2020-04-21 16:19 ` [dpdk-dev] [PATCH] eal: Fixes VFIO/sysfs race condition David Marchand
-- strict thread matches above, loose matches on Subject: below --
2020-04-06 22:16 Michael Haeuptle
2020-03-31 16:56 Michael Haeuptle
2020-04-01 8:50 ` Stojaczyk, Dariusz
2020-04-02 10:10 ` Burakov, Anatoly
2020-04-06 13:25 ` David Marchand
2020-04-06 19:15 ` Haeuptle, Michael
2020-04-06 20:08 ` David Marchand
2020-03-31 16:51 Michael Haeuptle
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=20200406222323.18609-1-michael.haeuptle@hpe.com \
--to=michael.haeuptle@hpe.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=xiao.w.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.