Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ferry Meng <mengferry@linux.alibaba.com>
Cc: stable@vger.kernel.org, Namjae Jeon <linkinjeon@kernel.org>,
	Steve French <stfrench@microsoft.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Tom Talpey <tom@talpey.com>,
	linux-cifs@vger.kernel.org
Subject: Re: [PATCH v2 6.12.y,6.6.y] ksmbd: make ksmbd thread names distinct by client IP
Date: Fri, 15 May 2026 12:12:10 +0200	[thread overview]
Message-ID: <2026051551-chlorine-credible-86a7@gregkh> (raw)
In-Reply-To: <20260512023427.90371-1-mengferry@linux.alibaba.com>

On Tue, May 12, 2026 at 10:34:27AM +0800, Ferry Meng wrote:
> From: Namjae Jeon <linkinjeon@kernel.org>
> 
> commit 5da92a251e41f824d7e6b4d54d65dcdcfd69fda3 upstream.
> 
> This patch makes ksmbd thread names distinct by client IP address.
> 
> 100943 ?        S      0:00 [ksmbd:::ffff:10.177.110.57]
>  or
> 101752 ?        S      0:00 [ksmbd:10.177.110.57]
> 
> Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
> Signed-off-by: Steve French <stfrench@microsoft.com>
> Stable-dep-of: 77ffbcac4e56 ("smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()")
> Stable-dep-of: 97f8d2648ef4 ("smb: server: fix active_num_conn leak on transport allocation failure")
> Signed-off-by: Ferry Meng <mengferry@linux.alibaba.com>
> ---
> v2: Replace verbose [backport ...] description with standard
>     Stable-dep-of: tags per stable tree convention.

Why is this needed?

Is this part of a series?  If so, what is that series?

confused,

greg k-h

      reply	other threads:[~2026-05-15 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  2:34 [PATCH v2 6.12.y,6.6.y] ksmbd: make ksmbd thread names distinct by client IP Ferry Meng
2026-05-15 10:12 ` Greg KH [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=2026051551-chlorine-credible-86a7@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@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