From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:53952 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752086AbdFLTQY (ORCPT ); Mon, 12 Jun 2017 15:16:24 -0400 Date: Mon, 12 Jun 2017 21:16:15 +0200 From: Greg KH To: Pavel Shilovskiy Cc: "stable@vger.kernel.org" , Sachin Prabhu , Steve French , Pavel Shilovsky Subject: Re: [PATCH] Call echo service immediately after socket reconnect Message-ID: <20170612191615.GA2114@kroah.com> References: <1496690121-70178-1-git-send-email-pshilov@microsoft.com> <20170612123003.GB17001@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Mon, Jun 12, 2017 at 07:08:51PM +0000, Pavel Shilovskiy wrote: > 2017-06-12 5:30 GMT-07:00 Greg KH : > > On Mon, Jun 05, 2017 at 12:15:21PM -0700, Pavel Shilovsky wrote: > >> From: Sachin Prabhu > >> > >> Commit b8c600120fc8 ("Call echo service immediately after socket > >> reconnect") upstream. > >> > >> Commit 4fcd1813e640 ("Fix reconnect to not defer smb3 session reconnect > >> long after socket reconnect") changes the behaviour of the SMB2 echo > >> service and causes it to renegotiate after a socket reconnect. However > >> under default settings, the echo service could take up to 120 seconds to > >> be scheduled. > >> > >> The patch forces the echo service to be called immediately resulting a > >> negotiate call being made immediately on reconnect. > >> > >> Signed-off-by: Sachin Prabhu > >> Reviewed-by: Pavel Shilovsky > >> Signed-off-by: Steve French > >> Acked-by: Sachin Prabhu > >> Signed-off-by: Pavel Shilovsky > >> --- > >> fs/cifs/connect.c | 24 ++++++++++++++++++------ > >> 1 file changed, 18 insertions(+), 6 deletions(-) > > > > What stable tree(s) do you want this applied to? Please be specific > > like the documentation tells you to do :) > > > > And CIFS maintainers, come on, your subject lines for patches suck, > > please use a prefix like _everyone_ else does to make it more obvious > > what part of the kernel is being touched. > > This patch is targeted for kernels below v4.9, in particular - for > v4.4 and v3.18 stable kernels. Do you want me to re-send the patch to > comply with the documentation? Please do.