commit | 2391ca41b476078da5cf72c2fe82ae9f03da8b38 | [log] [tgz] |
---|---|---|
author | Steve French <stfrench@microsoft.com> | Thu Feb 06 16:04:59 2020 -0600 |
committer | Steve French <stfrench@microsoft.com> | Thu Feb 06 17:21:23 2020 -0600 |
tree | a725478e0c9573feafbbc5e1b98c7bf33c9f8cdb | |
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>