From: Saurabh Singhal <saurabhs@arista.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Jingjing Wu <jingjing.wu@intel.com>,
Beilei Xing <beilei.xing@intel.com>
Cc: dev@dpdk.org, Saurabh Singhal <saurabhs@arista.com>
Subject: [PATCH v2] net/iavf: unregister intr handler before FD close
Date: Wed, 6 Sep 2023 04:47:49 -0700 [thread overview]
Message-ID: <20230906114750.74496-1-saurabhs@arista.com> (raw)
In-Reply-To: <DM4PR11MB59948C0DE908D32B3311C44FD7EFA@DM4PR11MB5994.namprd11.prod.outlook.com>
Unregister VFIO interrupt handler before the interrupt fd gets closed in
case iavf_dev_init() returns an error.
dpdk creates a standalone thread named eal-intr-thread for processing
interrupts for the PCI devices. The interrupt handler callbacks are
registered by the VF driver(iavf, in this case).
When we do a PCI probe of the network interfaces, we register an
interrupt handler, open a vfio-device fd using ioctl, and an eventfd in
dpdk. These interrupt sources are registered in a global linked list
that the eal-intr-thread keeps iterating over for handling the
interrupts. In our internal testing, we see eal-intr-thread crash in
these two ways:
Error adding fd 660 epoll_ctl, Operation not permitted
or
Error adding fd 660 epoll_ctl, Bad file descriptor
epoll_ctl() returns EPERM if the target fd does not support poll.
It returns EBADF when the epoll fd itself is closed or the target fd is
closed.
When the first type of crash happens, we see that the fd 660 is
anon_inode:[vfio-device] which does not support poll.
When the second type of crash happens, we could see from the fd map of
the crashing process that the fd 660 was already closed.
This means the said fd has been closed and in certain cases may have
been reassigned to a different device by the operating system but the
eal-intr-thread does not know about it.
We observed that these crashes were always accompanied by an error in
iavf_dev_init() after rte_intr_callback_register() and
iavf_enable_irq0() have already happened. In the error path, the
intr_handle_fd was being closed but the interrupt handler wasn't being
unregistered.
The fix is to unregister the interrupt handle in the
iavf_dev_init() error path.
Ensure proper cleanup if iavf_security_init() or
iavf_security_ctx_create() fail. Earlier, we were leaking memory by
simply returning from iavf_dev_init().
Signed-off-by: Saurabh Singhal <saurabhs@arista.com>
---
.mailmap | 1 +
drivers/net/iavf/iavf_ethdev.c | 22 ++++++++++++++++++++--
2 files changed, 21 insertions(+), 2 deletions(-)
diff --git a/.mailmap b/.mailmap
index 864d33ee46..4dac53011b 100644
--- a/.mailmap
+++ b/.mailmap
@@ -1227,6 +1227,7 @@ Satananda Burla <sburla@marvell.com>
Satha Rao <skoteshwar@marvell.com> <skoteshwar@caviumnetworks.com>
Satheesh Paul <psatheesh@marvell.com>
Sathesh Edara <sedara@marvell.com>
+Saurabh Singhal <saurabhs@arista.com>
Savinay Dharmappa <savinay.dharmappa@intel.com>
Scott Branden <scott.branden@broadcom.com>
Scott Daniels <daniels@research.att.com>
diff --git a/drivers/net/iavf/iavf_ethdev.c b/drivers/net/iavf/iavf_ethdev.c
index f2fc5a5621..b7ed22889a 100644
--- a/drivers/net/iavf/iavf_ethdev.c
+++ b/drivers/net/iavf/iavf_ethdev.c
@@ -133,6 +133,8 @@ static int iavf_dev_rx_queue_intr_enable(struct rte_eth_dev *dev,
uint16_t queue_id);
static int iavf_dev_rx_queue_intr_disable(struct rte_eth_dev *dev,
uint16_t queue_id);
+static void iavf_dev_interrupt_handler(void *param);
+static inline void iavf_disable_irq0(struct iavf_hw *hw);
static int iavf_dev_flow_ops_get(struct rte_eth_dev *dev,
const struct rte_flow_ops **ops);
static int iavf_set_mc_addr_list(struct rte_eth_dev *dev,
@@ -2709,13 +2711,13 @@ iavf_dev_init(struct rte_eth_dev *eth_dev)
ret = iavf_security_ctx_create(adapter);
if (ret) {
PMD_INIT_LOG(ERR, "failed to create ipsec crypto security instance");
- return ret;
+ goto flow_init_err;
}
ret = iavf_security_init(adapter);
if (ret) {
PMD_INIT_LOG(ERR, "failed to initialized ipsec crypto resources");
- return ret;
+ goto security_init_err;
}
}
@@ -2728,7 +2730,23 @@ iavf_dev_init(struct rte_eth_dev *eth_dev)
return 0;
+security_init_err:
+ iavf_security_ctx_destroy(adapter);
+
flow_init_err:
+ iavf_disable_irq0(hw);
+
+ if (vf->vf_res->vf_cap_flags & VIRTCHNL_VF_OFFLOAD_WB_ON_ITR) {
+ /* disable uio intr before callback unregiser */
+ rte_intr_disable(intr_handle);
+
+ /* unregister callback func from eal lib */
+ rte_intr_callback_unregister(intr_handle,
+ iavf_dev_interrupt_handler, dev);
+ } else {
+ rte_eal_alarm_cancel(iavf_dev_alarm_handler, dev);
+ }
+
rte_free(eth_dev->data->mac_addrs);
eth_dev->data->mac_addrs = NULL;
--
2.41.0
next prev parent reply other threads:[~2023-09-06 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 13:01 [PATCH] " Saurabh Singhal
2023-09-06 5:24 ` Zhang, Qi Z
2023-09-06 11:47 ` Saurabh Singhal [this message]
2023-09-06 14:05 ` [PATCH v2] " Stephen Hemminger
2023-09-07 1:41 ` Zhang, Qi Z
2023-09-07 3:15 ` [PATCH v4] " Saurabh Singhal
2023-09-11 0:55 ` 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=20230906114750.74496-1-saurabhs@arista.com \
--to=saurabhs@arista.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=thomas@monjalon.net \
/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).