From: Ferry Meng <mengferry@linux.alibaba.com>
To: stable@vger.kernel.org
Cc: Namjae Jeon <linkinjeon@kernel.org>,
Steve French <stfrench@microsoft.com>
Subject: [PATCH 6.1.y 0/2] ksmbd: fix residual active_num_conn leak on 6.1.y
Date: Tue, 12 May 2026 10:46:22 +0800 [thread overview]
Message-ID: <cover.1778553684.git.mengferry@linux.alibaba.com> (raw)
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(-)
--
2.43.5
next reply other threads:[~2026-05-12 2:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 2:46 Ferry Meng [this message]
2026-05-12 2:46 ` [PATCH 6.1.y 1/2] ksmbd: make ksmbd thread names distinct by client IP Ferry Meng
2026-05-12 2:46 ` [PATCH 6.1.y 2/2] smb: server: fix active_num_conn leak on transport allocation failure Ferry Meng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1778553684.git.mengferry@linux.alibaba.com \
--to=mengferry@linux.alibaba.com \
--cc=linkinjeon@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stfrench@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox