diff options
author | Andy Adamson <andros@netapp.com> | 2013-08-14 11:59:16 -0400 |
---|---|---|
committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2013-09-03 15:25:09 -0400 |
commit | dc24826bfca8d788d05f625208f06d90be5560b3 (patch) | |
tree | cc6fa221202666ac694581061caf373b431ff9bd /net | |
parent | 4de6caa270afaa381dd3373e9e6d148b1090e0ec (diff) | |
download | op-kernel-dev-dc24826bfca8d788d05f625208f06d90be5560b3.zip op-kernel-dev-dc24826bfca8d788d05f625208f06d90be5560b3.tar.gz |
NFS avoid expired credential keys for buffered writes
We must avoid buffering a WRITE that is using a credential key (e.g. a GSS
context key) that is about to expire or has expired. We currently will
paint ourselves into a corner by returning success to the applciation
for such a buffered WRITE, only to discover that we do not have permission when
we attempt to flush the WRITE (and potentially associated COMMIT) to disk.
Use the RPC layer credential key timeout and expire routines which use a
a watermark, gss_key_expire_timeo. We test the key in nfs_file_write.
If a WRITE is using a credential with a key that will expire within
watermark seconds, flush the inode in nfs_write_end and send only
NFS_FILE_SYNC WRITEs by adding nfs_ctx_key_to_expire to nfs_need_sync_write.
Note that this results in single page NFS_FILE_SYNC WRITEs.
Signed-off-by: Andy Adamson <andros@netapp.com>
[Trond: removed a pr_warn_ratelimited() for now]
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions