summaryrefslogtreecommitdiff
path: root/kernel/trace/trace.c
diff options
context:
space:
mode:
authorPavel Shilovsky <piastryyy@gmail.com>2019-09-30 10:06:19 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-10-17 13:41:05 -0700
commit91fdb3cf4cf50c13dfb8dca7824f17aceec68a73 (patch)
tree300f5c9f5d9a3b8a6aaca96443b84326ca5d9009 /kernel/trace/trace.c
parent4701063a62a69fbdef49a25e505c510040dab1bd (diff)
CIFS: Force revalidate inode when dentry is stale
[ Upstream commit c82e5ac7fe3570a269c0929bf7899f62048e7dbc ] 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> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'kernel/trace/trace.c')
0 files changed, 0 insertions, 0 deletions