stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Qian Lu <luqia@amazon.com>
Cc: stable@vger.kernel.org, trond.myklebust@hammerspace.com
Subject: Re: [PATCH 0/4] Fix NFSv4 lookup revalidation
Date: Wed, 31 Jul 2019 11:34:56 +0200	[thread overview]
Message-ID: <20190731093456.GE18269@kroah.com> (raw)
In-Reply-To: <20190731071327.28701-1-luqia@amazon.com>

On Wed, Jul 31, 2019 at 12:13:23AM -0700, Qian Lu wrote:
> Hello Greg,
> 
> Can you please consider including the following patches in the stable
> linux-4.14.y branch?
> 
> The following patch series attempts to address the issues raised by
> Stan Hu around NFSv4 lookup revalidation.
> 
> The first patch in the series should, in principle suffice to address
> the exact issue raised by Stan, however when looking at the
> implementation of nfs4_lookup_revalidate(), it becomes clear that we're
> not doing enough to revalidate the dentry itself when performing NFSv4.1
> opens either.
> 

You can not just ignore the 4.19.y kernel tree for these patches, as
when you all finally move forward from 4.14.y to 4.19.y, you would have
hit these same exact issues :(

I have also queued them up to 4.19.y.

Well, except for the last patch, that's not needed at all.

thanks,

greg k-h

  parent reply	other threads:[~2019-07-31  9:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31  7:13 [PATCH 0/4] Fix NFSv4 lookup revalidation Qian Lu
2019-07-31  7:13 ` [PATCH 1/4] NFS: Fix dentry revalidation on NFSv4 lookup Qian Lu
2019-07-31  7:13 ` [PATCH 2/4] NFS: Refactor nfs_lookup_revalidate() Qian Lu
2019-07-31  7:13 ` [PATCH 3/4] NFSv4: Fix lookup revalidate of regular files Qian Lu
2019-07-31  7:13 ` [PATCH 4/4] NFS: Remove redundant semicolon Qian Lu
2019-07-31  9:33   ` Greg KH
2019-07-31  9:34 ` Greg KH [this message]
2019-07-31 16:12   ` [PATCH 0/4] Fix NFSv4 lookup revalidation Qian Lu

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=20190731093456.GE18269@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=luqia@amazon.com \
    --cc=stable@vger.kernel.org \
    --cc=trond.myklebust@hammerspace.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;
as well as URLs for NNTP newsgroup(s).