From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: piastryyy@gmail.com, pshilov@microsoft.com,
stable@vger.kernel.org, stfrench@microsoft.com
Subject: Re: FAILED: patch "[PATCH] CIFS: Force revalidate inode when dentry is stale" failed to apply to 4.4-stable tree
Date: Mon, 14 Oct 2019 23:14:30 -0400 [thread overview]
Message-ID: <20191015031430.GK31224@sasha-vm> (raw)
In-Reply-To: <1571069849229168@kroah.com>
On Mon, Oct 14, 2019 at 06:17:29PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.4-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From c82e5ac7fe3570a269c0929bf7899f62048e7dbc Mon Sep 17 00:00:00 2001
>From: Pavel Shilovsky <piastryyy@gmail.com>
>Date: Mon, 30 Sep 2019 10:06:19 -0700
>Subject: [PATCH] CIFS: Force revalidate inode when dentry is stale
>
>Currently the client indicates that a dentry is stale when inode
>numbers or type types between a local inode and a remote file
>don't match. If this is the case attributes is not being copied
>from remote to local, so, it is already known that the local copy
>has stale metadata. That's why the inode needs to be marked for
>revalidation in order to tell the VFS to lookup the dentry again
>before openning a file. This prevents unexpected stale errors
>to be returned to the user space when openning a file.
>
>Cc: <stable@vger.kernel.org>
>Signed-off-by: Pavel Shilovsky <pshilov@microsoft.com>
>Signed-off-by: Steve French <stfrench@microsoft.com>
I also took a108471b5730b ("cifs: Check uniqueid for SMB2+ and return
-ESTALE if necessary") and queued both for 4.4.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-10-15 3:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 16:17 FAILED: patch "[PATCH] CIFS: Force revalidate inode when dentry is stale" failed to apply to 4.4-stable tree gregkh
2019-10-15 3:14 ` Sasha Levin [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=20191015031430.GK31224@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=piastryyy@gmail.com \
--cc=pshilov@microsoft.com \
--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;
as well as URLs for NNTP newsgroup(s).