From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: Patrisious Haddad <phaddad@nvidia.com>,
linux-rdma@vger.kernel.org,
Michael Guralnik <michaelgur@nvidia.com>
Subject: Re: [PATCH rdma-next] RDMA/mlx5: Move events notifier registration to be after device registration
Date: Thu, 14 Nov 2024 09:54:20 -0500 [thread overview]
Message-ID: <173159606014.154263.2997995911872279251.b4-ty@kernel.org> (raw)
In-Reply-To: <d271ceeff0c08431b3cbbbb3e2d416f09b6d1621.1731496944.git.leon@kernel.org>
On Wed, 13 Nov 2024 13:23:19 +0200, Leon Romanovsky wrote:
> Move pkey change work initialization and cleanup from device resources
> stage to notifier stage, since this is the stage which handles this work
> events.
>
> Fix a race between the device deregistration and pkey change work by moving
> MLX5_IB_STAGE_DEVICE_NOTIFIER to be after MLX5_IB_STAGE_IB_REG in order to
> ensure that the notifier is deregistered before the device during cleanup.
> Which ensures there are no works that are being executed after the
> device has already unregistered which can cause the panic below.
>
> [...]
Applied, thanks!
[1/1] RDMA/mlx5: Move events notifier registration to be after device registration
https://git.kernel.org/rdma/rdma/c/ede132a5cf559f
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2024-11-14 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 11:23 [PATCH rdma-next] RDMA/mlx5: Move events notifier registration to be after device registration Leon Romanovsky
2024-11-14 14:54 ` Leon Romanovsky [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=173159606014.154263.2997995911872279251.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=michaelgur@nvidia.com \
--cc=phaddad@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