Linux NFS development
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Trond Myklebust <trondmy@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
	linux-nfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] pnfs: Fix a problem where we gratuitously start doing I/O through the MDS
Date: Tue, 23 Jul 2019 11:57:25 +0200	[thread overview]
Message-ID: <20190723095725.GB3931@kroah.com> (raw)
In-Reply-To: <219efbee81f7f22bdaf9764011cf831385837f74.camel@gmail.com>

On Thu, Jul 18, 2019 at 08:54:53PM -0400, Trond Myklebust wrote:
> Hi Sasha,
> 
> On Fri, 2019-07-19 at 00:45 +0000, Sasha Levin wrote:
> > Hi,
> > 
> > [This is an automated email]
> > 
> > This commit has been processed because it contains a "Fixes:" tag,
> > fixing commit: d03360aaf5cc pNFS: Ensure we return the error if
> > someone kills a waiting layoutget.
> > 
> > The bot has tested the following trees: v5.2.1, v5.1.18, v4.19.59.
> > 
> > v5.2.1: Build OK!
> > v5.1.18: Build OK!
> > v4.19.59: Failed to apply! Possible dependencies:
> >     400417b05f3e ("pNFS: Fix a typo in pnfs_update_layout")
> > 
> > 
> > NOTE: The patch will not be queued to stable trees until it is
> > upstream.
> > 
> > How should we proceed with this patch?
> > 
> 
> Please apply both patches.
> i.e. Please apply
> 
> 400417b05f3e ("pNFS: Fix a typo in pnfs_update_layout")
> 58bbeab425c6 ("pnfs: Fix a problem where we gratuitously start doing
> I/O through the MDS")

Now done, thanks.

greg k-h

      reply	other threads:[~2019-07-23  9:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18 19:40 [PATCH] pnfs: Fix a problem where we gratuitously start doing I/O through the MDS Trond Myklebust
2019-07-19  0:45 ` Sasha Levin
2019-07-19  0:54   ` Trond Myklebust
2019-07-23  9:57     ` 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=20190723095725.GB3931@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=trondmy@gmail.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