vdpa/mlx5: Avoid using reslock in event_handler

Browse source

[ Upstream commit 0dbc1b4ae0 ]

event_handler runs under atomic context and may not acquire reslock. We
can still guarantee that the handler won't be called after suspend by
clearing nb_registered, unregistering the handler and flushing the
workqueue.

Signed-off-by: Eli Cohen <elic@nvidia.com>
Message-Id: <20221114131759.57883-5-elic@nvidia.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>

...

This commit is contained in:

Eli Cohen 2022-11-14 15:17:55 +02:00 • committed by Greg Kroah-Hartman

parent 6dbffca77f

commit 909b96557b

1 changed files with 4 additions and 12 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

16

drivers/vdpa/mlx5/net/mlx5_vnet.c

View file