ksmbd: fix residual active_num_conn leak on 6.1.y
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | ksmbd: make ksmbd thread names distinct by client IPfs/ | +13 | 0 replies | |
| 2/2 | smb: server: fix active_num_conn leak on transport allocation failurefs/ | +2 | 0 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Namjae Jeon |
|---|---|
| 1/2 | |
| 2/2 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 6.1.y 0/2] ksmbd: fix residual active_num_conn leak on 6.1.y
This series closes a residual active_num_conn leak on the 6.1.y stable
Upstream commits 77ffbcac4e56 ("smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()") and 6551300dc452 ("smb: server: fix active_num_conn leak on transport allocation failure") have already been backported to 6.1.y, but upstream 77ffbcac4e56 was built on top of 5da92a251e41 ("ksmbd: make ksmbd thread names distinct by client IP"), which removes kernel_getpeername() and the out_error: label in ksmbd_tcp_new_connection().
This series picks up the missing dependency commit and the follow-up fix so that 6.1.y has the same failure-path semantics as mainline.
Michael Bommarito (1):
smb: server: fix active_num_conn leak on transport allocation failure
Namjae Jeon (1):
ksmbd: make ksmbd thread names distinct by client IP
fs/smb/server/transport_tcp.c | 41 +++++++++++++---------------------- 1 file changed, 15 insertions(+), 26 deletions(-)
Signature · 1 line
2.43.5