public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/2] nfsv4 compound status
Date: Mon, 31 Mar 2008 17:35:23 +0300	[thread overview]
Message-ID: <47F0F6AB.3030302@panasas.com> (raw)

Two patches in this patchset implement what we discussed last month:
http://linux-nfs.org/pipermail/nfsv4/2008-February/007945.html

[PATCH 1/2] nfs: return negative error value from nfs{,4}_stat_to_errno

    All use sites for nfs{,4}_stat_to_errno negate their return value.
    It's more efficient to return a negative error from the stat_to_errno convertors
    rather than negating its return value everywhere. This also produces slightly
    smaller code.

[PATCH 2/2] nfs: use compound hdr.status to override op status.

    The compound header status must be equivalent to the
    status of the last operation in the compound results.
    In certain cases like lack of resources or xdr decoding error,
    the nfs server may return a non-zero status in the compound header
    which is not returned by any operation.  In this case we would
    notice that today when looking for the respective operations
    code in the results and we return -EIO when we cannot find it.
    This patch fixes that by returning the status available in the
    comound header instead.

    This patch also fixes 3 call sites where we looked at the comound
    hdr.status in the success case which is useless (yet benign).
    These are nfs4_xdr_dec_{fsinfo,setclientid,setclientid_confirm}

Benny

             reply	other threads:[~2008-03-31 14:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 14:35 Benny Halevy [this message]
2008-03-31 14:39 ` [PATCH 1/2] nfs: return negative error value from nfs{,4}_stat_to_errno Benny Halevy
2008-03-31 14:48 ` [PATCH 2/2] nfs: use compound hdr.status to override op status Benny Halevy
2008-03-31 22:25   ` Trond Myklebust
     [not found]     ` <1207002349.15341.15.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-04-01  9:37       ` Benny Halevy
2008-04-01  9:41         ` [PATCH 2/2 v1] " Benny Halevy
2008-05-09 22:21           ` [PATCH 1/1 v2] " Benny Halevy
2008-05-09 23:32           ` Benny Halevy
2008-05-10  6:11             ` Benny Halevy
2008-05-09 23:38           ` [PATCH " Benny Halevy
2008-05-10 17:24             ` Trond Myklebust
2008-05-11 23:21               ` [PATCH v3] " Benny Halevy
2008-05-11 23:26                 ` Trond Myklebust
2008-05-12  1:54                   ` Benny Halevy
2008-07-03 17:49                 ` [PATCH 0/2 v4] nfs: return nfs4 compound header status on op header decoding error Benny Halevy
2008-07-03 17:52                   ` [PATCH 1/2] " Benny Halevy
2008-07-03 18:42                   ` [PATCH 2/2] nfs: remove incorrect usage of nfs4 compound response hdr.status Benny Halevy
2008-07-15 21:57                   ` [PATCH 0/2 v4] nfs: return nfs4 compound header status on op header decoding error Trond Myklebust
2008-07-16  8:21                     ` Benny Halevy
2008-07-16 12:57                       ` Trond Myklebust
2008-07-16 13:22                         ` Benny Halevy
2008-07-17 12:09                           ` Trond Myklebust
2008-07-17 13:20                             ` Benny Halevy
2008-07-21 16:59                     ` [PATCH] nfs: return compound hdr.status when there are no op replies Benny Halevy

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=47F0F6AB.3030302@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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