summaryrefslogtreecommitdiffstats
path: root/fs/nfsd/xdr4.h
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@redhat.com>2011-10-13 11:37:11 -0400
committerJ. Bruce Fields <bfields@redhat.com>2011-10-17 17:50:08 -0400
commit856121b2e83bd64bffdc8de449d24c9295e92ff3 (patch)
treed60a777368fa48120a878407dd7abdcc780d2eba /fs/nfsd/xdr4.h
parent4cdc951b8611de4ce25e35c9fb8c0656150c9245 (diff)
downloadlinux-856121b2e83bd64bffdc8de449d24c9295e92ff3.tar.gz
linux-856121b2e83bd64bffdc8de449d24c9295e92ff3.tar.bz2
linux-856121b2e83bd64bffdc8de449d24c9295e92ff3.zip
nfsd4: warn on open failure after create
If we create the object and then return failure to the client, we're left with an unexpected file in the filesystem. I'm trying to eliminate such cases but not 100% sure I have so an assertion might be helpful for now. Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/nfsd/xdr4.h')
-rw-r--r--fs/nfsd/xdr4.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/nfsd/xdr4.h b/fs/nfsd/xdr4.h
index ce8c59196b4e..e3057350eea1 100644
--- a/fs/nfsd/xdr4.h
+++ b/fs/nfsd/xdr4.h
@@ -226,7 +226,8 @@ struct nfsd4_open {
u32 op_recall; /* recall */
struct nfsd4_change_info op_cinfo; /* response */
u32 op_rflags; /* response */
- int op_truncate; /* used during processing */
+ bool op_truncate; /* used during processing */
+ bool op_created; /* used during processing */
struct nfs4_openowner *op_openowner; /* used during processing */
struct nfs4_file *op_file; /* used during processing */
struct nfs4_ol_stateid *op_stp; /* used during processing */