[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025103116-grinning-component-3aea@gregkh>
Date: Fri, 31 Oct 2025 08:44:47 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Qingfang Deng <dqfext@...il.com>
Cc: Namjae Jeon <linkinjeon@...nel.org>, Steve French <smfrench@...il.com>,
	Sergey Senozhatsky <senozhatsky@...omium.org>,
	Tom Talpey <tom@...pey.com>, Ronnie Sahlberg <lsahlber@...hat.com>,
	Hyunchul Lee <hyc.lee@...il.com>, linux-cifs@...r.kernel.org,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	Sasha Levin <sashal@...nel.org>,
	"Jason A. Donenfeld" <Jason@...c4.com>
Subject: Re: [PATCH] ksmbd: server: avoid busy polling in accept loop
On Fri, Oct 31, 2025 at 03:32:06PM +0800, Qingfang Deng wrote:
> Hi Namjae,
> 
> On Thu, Oct 30, 2025 at 4:11 PM Namjae Jeon <linkinjeon@...nel.org> wrote:
> > > Fixes: 0626e6641f6b ("cifsd: add server handler for central processing and tranport layers")
> > > Signed-off-by: Qingfang Deng <dqfext@...il.com>
> > Applied it to #ksmbd-for-next-next.
> > Thanks!
> 
> I just found that this depends on another commit which is not in
> kernel versions earlier than v6.1:
> a7c01fa93aeb ("signal: break out of wait loops on kthread_stop()")
> 
> With the current Fixes tag, this commit will be backported to v5.15
> automatically. But without said commit, kthread_stop() cannot wake up
> a blocking kernel_accept().
> Should I change the Fixes tag, or inform linux-stable not to backport
> this patch to v5.15?
Email stable@...r.kernel.org when it lands in Linus's tree to not
backport it that far.
thanks,
greg k-h
Powered by blists - more mailing lists
 
