NFSD: restore trace event lost in mismerge
authorKinglong Mee <kinglongmee@gmail.com>
Fri, 20 Mar 2015 07:56:40 +0000 (15:56 +0800)
committerJ. Bruce Fields <bfields@redhat.com>
Fri, 20 Mar 2015 16:43:06 +0000 (12:43 -0400)
31ef83dc05 "nfsd: add trace events" had a typo that dropped a trace
event and replaced it by an incorrect recursive call to
nfsd4_cb_layout_fail.  133d558216d9 "Subject: nfsd: don't recursively
call nfsd4_cb_layout_fail" fixed the crash, this restores the
tracepoint.

Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4layouts.c

index 1028a062954357c06005dc7b0d6f61a10ea6f418..0a616b51c5bb2965cb142c16897d2259d6616777 100644 (file)
@@ -587,6 +587,8 @@ nfsd4_cb_layout_fail(struct nfs4_layout_stateid *ls)
 
        rpc_ntop((struct sockaddr *)&clp->cl_addr, addr_str, sizeof(addr_str));
 
+       trace_layout_recall_fail(&ls->ls_stid.sc_stateid);
+
        printk(KERN_WARNING
                "nfsd: client %s failed to respond to layout recall. "
                "  Fencing..\n", addr_str);