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 invalid memory access in port closing
Date: Fri, 18 Nov 2022 07:38:08 +0100 [thread overview]
Message-ID: <CAATJJ0+rEp_OtrhHCLjff0wmK=Z2Fjze+avaC3ro++JyVBB-cQ@mail.gmail.com> (raw)
In-Reply-To: <20221117154751.1273083-1-michaelba@nvidia.com>
On Thu, Nov 17, 2022 at 4:48 PM Michael Baum <michaelba@nvidia.com> wrote:
>
> The shared IB device (sh) has per port data updated in port creation.
> In port closing this port data is updated even when the SH still exist.
>
> However, this updating is happened after SH has been released and for
> last port it actually accesses to freed memory.
>
> This patch updates the port data before SH releasing.
>
> Fixes: 08c0b56cb304 ("net/mlx5: fix port event cleaning order")
> Cc: michaelba@nvidia.com
Applied, thanks for the ping in regard to this follow on fix, I'd have
missed it since it has no 19.11 in the subject.
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
> drivers/net/mlx5/mlx5.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c
> index ece8c5e3e1..efeeb8443b 100644
> --- a/drivers/net/mlx5/mlx5.c
> +++ b/drivers/net/mlx5/mlx5.c
> @@ -1405,6 +1405,12 @@ mlx5_dev_close(struct rte_eth_dev *dev)
> close(priv->nl_socket_rdma);
> if (priv->vmwa_context)
> mlx5_vlan_vmwa_exit(priv->vmwa_context);
> + 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();
> /*
> * Free the shared context in last turn, because the cleanup
> * routines above may use some shared fields, like
> @@ -1458,12 +1464,6 @@ 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;
> /*
> --
> 2.25.1
>
--
Christian Ehrhardt
Senior Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2022-11-18 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 15:47 Michael Baum
2022-11-18 6:38 ` 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='CAATJJ0+rEp_OtrhHCLjff0wmK=Z2Fjze+avaC3ro++JyVBB-cQ@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).