Steve French 2391ca41b4 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>
2020-02-06 17:21:23 -06:00
..
2019-09-27 15:10:34 -07:00
2019-09-19 09:42:37 -07:00
2019-11-11 09:21:59 -05:00
2020-01-30 15:39:24 -08:00
2019-09-19 09:42:37 -07:00
2019-09-19 09:42:37 -07:00
2019-12-14 11:13:54 -08:00
\n
2020-01-30 15:37:41 -08:00
2019-09-19 09:42:37 -07:00
2020-01-14 13:28:28 -08:00
2020-01-30 15:24:24 -08:00
2019-12-01 14:00:59 -08:00
2019-11-30 10:44:49 -08:00
2019-08-07 21:51:47 -04:00
2020-01-29 19:38:34 -08:00
2020-01-29 18:53:37 -08:00
2019-10-14 15:04:01 -07:00
2020-02-01 10:36:49 -08:00
2019-12-08 14:37:36 +01:00