summaryrefslogtreecommitdiff
path: root/scripts/faddr2line
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@redhat.com>2020-12-01 01:46:14 +0300
committerChuck Lever <chuck.lever@oracle.com>2020-12-09 17:39:37 +0300
commit70b87f77294d16d3e567056ba4c9ee2b091a5b50 (patch)
tree557e788075d69a9eb9248a8cc6aeb3486dd5c348 /scripts/faddr2line
parent4a9d81caf841cd2c0ae36abec9c2963bf21d0284 (diff)
downloadlinux-70b87f77294d16d3e567056ba4c9ee2b091a5b50.tar.xz
nfsd: only call inode_query_iversion in the I_VERSION case
inode_query_iversion() can modify i_version. Depending on the exported filesystem, that may not be safe. For example, if you're re-exporting NFS, NFS stores the server's change attribute in i_version and does not expect it to be modified locally. This has been observed causing unnecessary cache invalidations. The way a filesystem indicates that it's OK to call inode_query_iverson() is by setting SB_I_VERSION. So, move the I_VERSION check out of encode_change(), where it's used only in GETATTR responses, to nfsd4_change_attribute(), which is also called for pre- and post- operation attributes. (Note we could also pull the NFSEXP_V4ROOT case into nfsd4_change_attribute() as well. That would actually be a no-op, since pre/post attrs are only used for metadata-modifying operations, and V4ROOT exports are read-only. But we might make the change in the future just for simplicity.) Reported-by: Daire Byrne <daire@dneg.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'scripts/faddr2line')
0 files changed, 0 insertions, 0 deletions