Fix-use-after-free-when-a-port-is-removed
Status from this message: applied to nvme-5.15.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | nvmet: Fix use-after-free when a port is removeddrivers/ | +2 | 0 replies | |
| 2/3 | nvmet_rdma: Fix use-after-free when a port is removeddrivers/ | +24 | 0 replies | |
| 3/3 | nvmet_tcp: Fix use-after-free when a port is removeddrivers/ | +16 | 0 replies |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Max Gurtovoy |
|---|---|
| 1/3 | R-b |
| 2/3 | R-b |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] Fix-use-after-free-when-a-port-is-removed
Hi all,
This series fixes an issue when a port is removed through configfs. This issue is a use-after-free bug for any command that dereferences req->port (like in nvmet_parse_io_cmd) after releasing the port.
The first patch fix the issue after the controller finished the connection flow and the second and the third patches fix it during connection creation time at nvmet-rdma and nvmet-tcp drivers.
Israel Rukshin (3):
nvmet: Fix use-after-free when a port is removed
nvmet_rdma: Fix use-after-free when a port is removed
nvmet_tcp: Fix use-after-free when a port is removed
drivers/nvme/target/configfs.c | 2 ++ drivers/nvme/target/rdma.c | 24 ++++++++++++++++++++++++ drivers/nvme/target/tcp.c | 16 ++++++++++++++++ 3 files changed, 42 insertions(+)
Signature · 7 lines
2.16.3 _______________________________________________ Linux-nvme mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-nvme