From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Michael Baum <michaelba@nvidia.com>
Cc: stable@dpdk.org, Matan Azrad <matan@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [PATCH 19.11] net/mlx5: fix port event cleaning order
Date: Thu, 17 Nov 2022 08:40:06 +0100 [thread overview]
Message-ID: <CAATJJ0LzXeE5pHYdU7ybACe=BebG3YmNi6Q+LA6TAt0mevjDVg@mail.gmail.com> (raw)
In-Reply-To: <20221116121328.935537-1-michaelba@nvidia.com>
On Wed, Nov 16, 2022 at 1:13 PM Michael Baum <michaelba@nvidia.com> wrote:
>
> [ upstream commit 7ba5320baa3285bf8beca96cc025ff56b494060d ]
Applied, thanks!
> The shared IB device (sh) has per port data with filed for interrupt
> handler port_id. It used by shared interrupt handler to find the
> corresponding rte_eth device by IB port index.
> If value is equal or greater RTE_MAX_ETHPORTS it means there is no
> subhandler installed for specified IB port index.
>
> When a few ports are created under same sh, the sh is created with the
> first port and the interrupt handler port_id is initialized to
> RTE_MAX_ETHPORTS for each port.
> In port creation, the interrupt handler port_id is updated with the
> correct value. Since this updating, the mlx5_dev_interrupt_nl_cb
> function uses this port and its priv structure.
> However, when the ports are closed, this filed isn't updated and the
> interrupt handler continue working until it is uninstalled in SH
> destruction.
> If mlx5_dev_interrupt_nl_cb is called between port closing and SH
> destruction, it uses invalid port causing a crash.
>
> This patch adds interrupt handler port_id updating to the close function
> and add memory barrier to make sure it is done before priv reset.
>
> Fixes: 0906b984ff1f ("net/mlx5: fix initial link status detection")
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
> drivers/net/mlx5/mlx5.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c
> index dee018bbba..ae3ba1885e 100644
> --- a/drivers/net/mlx5/mlx5.c
> +++ b/drivers/net/mlx5/mlx5.c
> @@ -1458,6 +1458,12 @@ mlx5_dev_close(struct rte_eth_dev *dev)
> if (!c)
> claim_zero(rte_eth_switch_domain_free(priv->domain_id));
> }
> + priv->sh->port[priv->ibv_port - 1].nl_ih_port_id = RTE_MAX_ETHPORTS;
> + /*
> + * The interrupt handler port id must be reset before priv is reset
> + * since 'mlx5_dev_interrupt_nl_cb' uses priv.
> + */
> + rte_io_wmb();
> memset(priv, 0, sizeof(*priv));
> priv->domain_id = RTE_ETH_DEV_SWITCH_DOMAIN_ID_INVALID;
> /*
> @@ -2883,6 +2889,9 @@ mlx5_dev_spawn(struct rte_device *dpdk_dev,
> return eth_dev;
> error:
> if (priv) {
> + priv->sh->port[priv->ibv_port - 1].nl_ih_port_id =
> + RTE_MAX_ETHPORTS;
> + rte_io_wmb();
> if (priv->mreg_cp_tbl)
> mlx5_hlist_destroy(priv->mreg_cp_tbl, NULL, NULL);
> if (priv->sh)
> --
> 2.25.1
>
--
Christian Ehrhardt
Senior Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2022-11-17 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 12:13 Michael Baum
2022-11-17 7:40 ` Christian Ehrhardt [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='CAATJJ0LzXeE5pHYdU7ybACe=BebG3YmNi6Q+LA6TAt0mevjDVg@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).