public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Srikrishan Malik <srimalik@in.ibm.com>
Cc: bfields@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] Fail the test if number of supported attrs are more than expected.
Date: Tue, 7 Oct 2014 09:46:13 -0400	[thread overview]
Message-ID: <20141007134613.GB23258@fieldses.org> (raw)
In-Reply-To: <1407994346-18244-1-git-send-email-srimalik@in.ibm.com>

Sorry for the delay.

Returning unrequested attributes sounds like unlikely behavior, but may
as well check for it, sure....  Applying.

--b.

On Thu, Aug 14, 2014 at 11:02:26AM +0530, Srikrishan Malik wrote:
> Signed-off-by: Srikrishan Malik <srimalik@in.ibm.com>
> ---
>  nfs4.0/servertests/st_getattr.py |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/nfs4.0/servertests/st_getattr.py b/nfs4.0/servertests/st_getattr.py
> index a55b923..6a4acdd 100644
> --- a/nfs4.0/servertests/st_getattr.py
> +++ b/nfs4.0/servertests/st_getattr.py
> @@ -43,10 +43,14 @@ def _try_empty(t, c, path):
>  def _try_supported(t, env, path):
>      c = env.c1
>      mandatory = sum([attr.mask for attr in env.attr_info if attr.mandatory])
> +    all = sum([attr.mask for attr in env.attr_info])
>      supported = c.supportedAttrs(path)
>      if mandatory & supported != mandatory:
>          t.fail("GETATTR(FATTR4_SUPPORTED_ATTRS) did not return "
>                 "all mandatory attributes")
> +    if supported > all:
> +        t.fail("GETATTR(FATTR4_SUPPORTED_ATTRS) returned more than expected "
> +               "supported attributes for the protocol")
>  
>  def _try_long(env, path):
>      c = env.c1
> -- 
> 1.7.1
> 

      reply	other threads:[~2014-10-07 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14  5:32 [PATCH] Fail the test if number of supported attrs are more than expected Srikrishan Malik
2014-10-07 13:46 ` J. Bruce Fields [this message]

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=20141007134613.GB23258@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bfields@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=srimalik@in.ibm.com \
    /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