diff options
| author |   Israel Rukshin <israelr@nvidia.com> | 2021-10-06 08:09:44 +0000 |
|---|---|---|
| committer |   Christoph Hellwig <hch@lst.de> | 2021-10-20 19:16:00 +0200 |
| commit | fcf73a804c7d6bbf0ea63531c6122aa363852e04 (patch) | |
| tree | 33d5738c4869f8a10527f1c402b6cd180caae40b /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | nvmet: fix use-after-free when a port is removed (diff) | |
| download | wireguard-linux-fcf73a804c7d6bbf0ea63531c6122aa363852e04.tar.xz wireguard-linux-fcf73a804c7d6bbf0ea63531c6122aa363852e04.zip | |
nvmet-rdma: fix use-after-free when a port is removed
When removing a port, all its controllers are being removed, but there
are queues on the port that doesn't belong to any controller (during
connection time). This causes a use-after-free bug for any command
that dereferences req->port (like in nvmet_alloc_ctrl). Those queues
should be destroyed before freeing the port via configfs. Destroy the
remaining queues after the RDMA-CM was destroyed guarantees that no
new queue will be created.
Signed-off-by: Israel Rukshin <israelr@nvidia.com>
Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions