smb:server: fix possible use after free problems
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | smb: server: remove separate empty_recvmsg_queuefs/ | +8 | 0 replies | |
| 2/4 | smb: server: make sure we call ib_dma_unmap_single() only if we called ib_dma_map_single alreadyfs/ | +9 | 0 replies | |
| 3/4 | smb: server: let recv_done() consitently call put_recvmsg/smb_direct_disconnect_rdma_connectionfs/ | +13 | 0 replies | |
| 4/4 | smb: server: let recv_done() avoid touching data_transfer after cleanup/movefs/ | +7 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] smb:server: fix possible use after free problems
While refactoring the client and server smbdirect code I noticed a few problems where we might hit use after free style problems.
In order to allow backports I decided to fix the problems before trying to move things to common code.
The client has similar problems, I've sent a separate patchset for the client already.
Stefan Metzmacher (4):
smb: server: remove separate empty_recvmsg_queue
smb: server: make sure we call ib_dma_unmap_single() only if we called
ib_dma_map_single already
smb: server: let recv_done() consitently call
put_recvmsg/smb_direct_disconnect_rdma_connection
smb: server: let recv_done() avoid touching data_transfer after
cleanup/move
fs/smb/server/transport_rdma.c | 97 ++++++++++++---------------------- 1 file changed, 35 insertions(+), 62 deletions(-)
Signature · 1 line
2.43.0