Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Henning Schild <henning.schild@siemens.com>,
	stable@vger.kernel.org, Ronnie Sahlberg <lsahlber@redhat.com>,
	Pavel Shilovsky <pshilov@microsoft.com>,
	Steve French <stfrench@microsoft.com>
Subject: Re: backport of cifs patch to 4.4.x and 4.9.x
Date: Fri, 15 May 2020 15:40:56 +0200	[thread overview]
Message-ID: <20200515134056.GA2051562@kroah.com> (raw)
In-Reply-To: <20200515133159.GE29995@sasha-vm>

On Fri, May 15, 2020 at 09:31:59AM -0400, Sasha Levin wrote:
> On Fri, May 15, 2020 at 02:57:48PM +0200, Greg KH wrote:
> > On Fri, May 15, 2020 at 01:44:20PM +0200, Henning Schild wrote:
> > > Hi,
> > > 
> > > please backport the following path to 4.4.x and 4.9.x
> > > 
> > > subject: cifs: Fix a race condition with cifs_echo_request
> > > hash: f2caf901c1b7ce65f9e6aef4217e3241039db768
> > 
> > It does not apply cleanly, can you provide a working backport so that we
> > can queue it up properly?
> 
> I've queued these two for 4.9 and 4.4:
> 
> f2caf901c1b7 ("cifs: Fix a race condition with cifs_echo_request")
> 76e752701a8a ("cifs: Check for timeout on Negotiate stage")

Thanks!

  reply	other threads:[~2020-05-15 13:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 11:44 backport of cifs patch to 4.4.x and 4.9.x Henning Schild
2020-05-15 12:57 ` Greg KH
2020-05-15 13:19   ` [PATCH 4.4.y] cifs: Fix a race condition with cifs_echo_request Henning Schild
2020-05-15 13:20   ` [PATCH 4.9.y] " Henning Schild
2020-05-15 13:23   ` backport of cifs patch to 4.4.x and 4.9.x Henning Schild
2020-05-15 13:31   ` Sasha Levin
2020-05-15 13:40     ` Greg KH [this message]
2020-05-15 17:31     ` [EXTERNAL] " Pavel Shilovskiy

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=20200515134056.GA2051562@kroah.com \
    --to=greg@kroah.com \
    --cc=henning.schild@siemens.com \
    --cc=lsahlber@redhat.com \
    --cc=pshilov@microsoft.com \
    --cc=sashal@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