From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Namjae Jeon <linkinjeon@kernel.org>,
Steve French <stfrench@microsoft.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Tom Talpey <tom@talpey.com>,
Henrique Carvalho <henrique.carvalho@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
Ferry Meng <mengferry@linux.alibaba.com>
Subject: Re: [PATCH 6.6.y] ksmbd: make ksmbd thread names distinct by client IP
Date: Mon, 11 May 2026 20:17:57 -0400 [thread overview]
Message-ID: <20260511220000.stable-reply-item008@kernel.org> (raw)
In-Reply-To: <20260511124625.52768-1-mengferry@linux.alibaba.com>
On Mon, May 11, 2026 at 08:46:25PM +0800, Ferry Meng wrote:
> [backport needed for 6.6-stable to close a residual
> active_num_conn leak. ...]
I think its needed for 6.12 too?
--
Thanks,
Sasha
prev parent reply other threads:[~2026-05-12 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 12:46 [PATCH 6.6.y] ksmbd: make ksmbd thread names distinct by client IP Ferry Meng
2026-05-12 0:17 ` Sasha Levin [this message]
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=20260511220000.stable-reply-item008@kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=henrique.carvalho@suse.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mengferry@linux.alibaba.com \
--cc=senozhatsky@chromium.org \
--cc=stable@vger.kernel.org \
--cc=stfrench@microsoft.com \
--cc=tom@talpey.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