From: Benny Halevy <bhalevy@panasas.com>
To: " J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, pnfs@linux-nfs.org,
Benny Halevy <bhalevy@panasas.com>
Subject: [PATCH 2/6] nfsd: dprint each op status in nfsd4_proc_compound
Date: Mon, 15 Dec 2008 19:40:49 +0200 [thread overview]
Message-ID: <1229362849-9727-1-git-send-email-bhalevy@panasas.com> (raw)
In-Reply-To: <49469601.7020101@panasas.com>
Signed-off-by: Benny Halevy <bhalevy@panasas.com>
---
fs/nfsd/nfs4proc.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
index 669461e..9fa60a3 100644
--- a/fs/nfsd/nfs4proc.c
+++ b/fs/nfsd/nfs4proc.c
@@ -946,6 +946,11 @@ encode_op:
nfsd4_encode_operation(resp, op);
status = op->status;
}
+
+ dprintk("nfsv4 compound op %p opcnt %d #%d: %d: status %d\n",
+ args->ops, args->opcnt, resp->opcnt, op->opnum,
+ be32_to_cpu(status));
+
if (cstate->replay_owner) {
nfs4_put_stateowner(cstate->replay_owner);
cstate->replay_owner = NULL;
--
1.6.0.2
next prev parent reply other threads:[~2008-12-15 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 17:38 [PATCH 0/6] NFSD: minor cleanups for 2.6.29 Benny Halevy
2008-12-15 17:40 ` [PATCH 1/6] nfsd: add etoosmall to nfserrno Benny Halevy
2008-12-15 17:40 ` Benny Halevy [this message]
2008-12-15 17:41 ` [PATCH 3/6] nfsd: git rid of nfs4_cb_null_ops declaration Benny Halevy
2008-12-15 17:41 ` [PATCH 4/6] nfsd: delete wrong file comment from nfsd/nfs4xdr.c Benny Halevy
2008-12-15 17:42 ` [PATCH 5/6] nfsd: last_byte_offset Benny Halevy
2008-12-15 18:33 ` Chuck Lever
2008-12-17 10:09 ` Benny Halevy
2008-12-17 20:24 ` Chuck Lever
2008-12-18 15:20 ` Fredric Isaman
2008-12-15 17:42 ` [PATCH 6/6] nfsd: get rid of NFSD_VERSION Benny Halevy
2009-01-07 22:38 ` [PATCH 0/6] NFSD: minor cleanups for 2.6.29 J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1229362849-9727-1-git-send-email-bhalevy@panasas.com \
--to=bhalevy@panasas.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=pnfs@linux-nfs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox