From: Benny Halevy <bhalevy@panasas.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "J. Bruce Fields" <bfields@redhat.com>,
NFS list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/2] decode_cb_op_status fix
Date: Thu, 13 Jan 2011 11:23:56 +0200 [thread overview]
Message-ID: <4D2EC4AC.9090205@panasas.com> (raw)
Chuck, it looks like the following patch introduced a couple in
handling of the operation status.
85a5648 NFSD: Update XDR decoders in NFSv4 callback client
The first patch in this series fixes the bugs and the second
reintroduces the handling of nfserr into decode_cb_op_status
as it used to be in decode_cb_op_hdr, since I think it's simpler
with respect to the current usage (vs. theoretical generic use of
decode_cb_op_status to decode the status and return it in an output var).
Benny
next reply other threads:[~2011-01-13 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 9:23 Benny Halevy [this message]
2011-01-13 9:25 ` [PATCH 1/2] NFSD: use nfserr for status after decode_cb_op_status Benny Halevy
2011-01-18 22:13 ` Chuck Lever
2011-01-13 9:25 ` [PATCH 2/2] NFSD: do common error handling in decode_cb_op_status Benny Halevy
2011-01-18 22:20 ` Chuck Lever
2011-01-18 23:19 ` J. Bruce Fields
2011-01-18 21:57 ` [PATCH 0/2] decode_cb_op_status fix J. Bruce Fields
2011-01-18 21:59 ` Chuck Lever
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=4D2EC4AC.9090205@panasas.com \
--to=bhalevy@panasas.com \
--cc=bfields@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).