linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: linux-nfs@vger.kernel.org, ffilz@us.ibm.com,
	Fred Isaman <iisaman@netapp.com>
Subject: Re: fixes for 3.8
Date: Mon, 26 Nov 2012 11:24:20 -0500	[thread overview]
Message-ID: <20121126162420.GD11860@fieldses.org> (raw)
In-Reply-To: <20121126154735.GA11860@fieldses.org>

On Mon, Nov 26, 2012 at 10:47:35AM -0500, bfields wrote:
> On Mon, Nov 26, 2012 at 09:39:51AM -0500, J. Bruce Fields wrote:
> > The following are some fixes I plan to queue up for 3.8, mostly problems
> > found while looking at the v4 xdr code.
> 
> I also added corresponding tests to
> 
> 	git://linux-nfs.org/~bfields/pynfs.git

There are also a few more commits there that weed out false positives
(or tests that look possibly technically correct but so trivial as to
not be worth complaining about).  In most cases the tests are still
there if you know the right tag to task for, they just aren't run by
default.  I think it's really important that we don't make people wade
through a lot of noise to get to the important failures.

Frank, could you check if you still get spurious warnings or failures
against Ganesha?

At this point, against a linux server,

  ./nfs4.0/testserver.py server:/dir --rundeps --maketree all

has 8 failures, of which 4 look like legitimate server bugs.  The
remaining 4 depend on who I'm running as: as root, some permissions
tests fail due to root bypassing access checks on mode-0 objects.  As a
regular user the special-device tests fail or can't run.  I don't have a
plan for those yet.

--b.

      reply	other threads:[~2012-11-26 16:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 14:39 fixes for 3.8 J. Bruce Fields
2012-11-26 14:39 ` [PATCH 1/8] nfsd: fix v4 reply caching J. Bruce Fields
2012-11-26 14:39 ` [PATCH 2/8] nfsd4: no, we're not going to check tags for utf8 J. Bruce Fields
2012-11-26 14:39 ` [PATCH 3/8] nfsd4: simplify reading of opnum J. Bruce Fields
2012-11-26 14:39 ` [PATCH 4/8] nfsd4: reorganize write decoding J. Bruce Fields
2012-11-26 14:39 ` [PATCH 5/8] nfsd4: move more write parameters into xdr argument J. Bruce Fields
2012-11-26 14:39 ` [PATCH 6/8] nfsd4: delay filling in write iovec array till after xdr decoding J. Bruce Fields
2012-11-26 14:39 ` [PATCH 7/8] nfsd4: downgrade some fs/nfsd/nfs4state.c BUG's J. Bruce Fields
2012-11-26 14:39 ` [PATCH 8/8] nfsd4: return badname on use "." or "..", or "/" J. Bruce Fields
2012-11-26 15:47 ` fixes for 3.8 J. Bruce Fields
2012-11-26 16:24   ` 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=20121126162420.GD11860@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bfields@redhat.com \
    --cc=ffilz@us.ibm.com \
    --cc=iisaman@netapp.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).