summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSteve French <stfrench@microsoft.com>2019-02-25 15:02:58 -0600
committerSteve French <stfrench@microsoft.com>2019-03-05 18:10:04 -0600
commitb0a42f2ac96e93f27704440ec55651d0570622f1 (patch)
tree04fb1fa664c86fa544d6a06b706c3ea54d39835f
parentd323c24617527f28cdb03f3bb7d8f9b62eecee80 (diff)
downloadlwn-b0a42f2ac96e93f27704440ec55651d0570622f1.tar.gz
lwn-b0a42f2ac96e93f27704440ec55651d0570622f1.zip
smb3: add missing read completion trace point
When ENODATA returned we weren't logging the read completion (not an error, but can be indicated by logging length 0) which makes looking at read traces confusing for smb3. Signed-off-by: Steve French <stfrench@microsoft.com> Reviewed-by: Ronnie Sahlberg <lsahlber@redhat.com>
-rw-r--r--fs/cifs/smb2pdu.c5
1 files changed, 4 insertions, 1 deletions
diff --git a/fs/cifs/smb2pdu.c b/fs/cifs/smb2pdu.c
index ec9abe293279..b774b43edfbd 100644
--- a/fs/cifs/smb2pdu.c
+++ b/fs/cifs/smb2pdu.c
@@ -3404,7 +3404,10 @@ SMB2_read(const unsigned int xid, struct cifs_io_parms *io_parms,
io_parms->tcon->tid, ses->Suid,
io_parms->offset, io_parms->length,
rc);
- }
+ } else
+ trace_smb3_read_done(xid, req->PersistentFileId,
+ io_parms->tcon->tid, ses->Suid,
+ io_parms->offset, 0);
free_rsp_buf(resp_buftype, rsp_iov.iov_base);
return rc == -ENODATA ? 0 : rc;
} else