diff options
| author | Steve French <stfrench@microsoft.com> | 2020-02-06 16:04:59 -0600 |
|---|---|---|
| committer | Steve French <stfrench@microsoft.com> | 2020-02-06 17:21:23 -0600 |
| commit | 2391ca41b476078da5cf72c2fe82ae9f03da8b38 (patch) | |
| tree | a725478e0c9573feafbbc5e1b98c7bf33c9f8cdb /fs | |
| parent | e3e056c35108661e418c803adfc054bf683426e7 (diff) | |
smb3: add one more dynamic tracepoint missing from strict fsync path
We didn't have a dynamic trace point for catching errors in
file_write_and_wait_range error cases in cifs_strict_fsync.
Since not all apps check for write behind errors, it can be
important for debugging to be able to trace these error
paths.
Suggested-and-reviewed-by: Pavel Shilovsky <pshilov@microsoft.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
Diffstat (limited to 'fs')
| -rw-r--r-- | fs/cifs/file.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/fs/cifs/file.c b/fs/cifs/file.c index 99ea7b2a06a5..bc9516ab4b34 100644 --- a/fs/cifs/file.c +++ b/fs/cifs/file.c @@ -2593,8 +2593,10 @@ int cifs_strict_fsync(struct file *file, loff_t start, loff_t end, struct cifs_sb_info *cifs_sb = CIFS_SB(inode->i_sb); rc = file_write_and_wait_range(file, start, end); - if (rc) + if (rc) { + trace_cifs_fsync_err(inode->i_ino, rc); return rc; + } xid = get_xid(); |