Regression test results for linux-2.6.18-rc4-CITI_NFS4_ALL-1 (and before)

[Bryce Harrington]

On Tue, Aug 22, 2006 at 05:30:20PM -0700, Bryce Harrington wrote:
> On Mon, Aug 21, 2006 at 09:50:54PM -0400, J. Bruce Fields wrote:
> > http://www.citi.umich.edu/projects/nfsv4/linux/kernel-patches/2.6.18-rc4-1/linux-2.6.18-rc4-CITI_NFS4_ALL-1.diff
> > 
> Here is the report for this patch release (and the two prior releases):
> 
>  linux-2.6.18-rc4-CITI_NFS4_ALL-1   http://crucible.osdl.org/runs/1589/
> 
> 1.  Failure during holey file test  (Bugzilla #119)
> ==================================
> Starting with the linux-2.6.18-rc2-CITI_NFS4_ALL-1 patch, Connectathon
> 04 has been failing during the "holey file test"

With a patch proposed by Steve Dickson, this issue is now fixed and
verified.  

   http://bugzilla.linux-nfs.org/show_bug.cgi?id=119

> 2.  SETCLIENTID failures  (Bugzilla #120)
> ========================
> The following cases are failing due to issues related to SETCLIENTID:
> 
>  CID3     st_setclientid.testLoseAnswer                            : FAILURE
>  CID4     st_setclientid.testAllCases                              : FAILURE
>  LKT2b    st_lockt.testBlock                                       : FAILURE
>  OPEN7c   st_open.testChar                                         : FAILURE
>  OPEN11   st_open.testLongName                                     : FAILURE

We're still seeing newpynfs failures like these, although in additional
runs I've noticed it varies exactly which test cases fail.
E.g. sometimes OPEN7c passes but OPEN8 fails, or OPEN11 passes and
OPEN13 fails.

> 3.  ACL Attr failures  (Bugzilla #121)
> =====================
> NewPyNFS's setattr tests check for several unsupported features, which
> should return NFS4ERR_ATTRNOTSUPP.  These are currently failing because
> they are instead seeing NFS4ERR_NOTSUPP:
> 
>  SATT11a  st_setattr.testUnsupportedLink                           : FAILURE
>             SETATTR with unsupported attr acl should return
>             NFS4ERR_ATTRNOTSUPP, instead got NFS4ERR_NOTSUPP

Fwiw, these are present in the nfs-server-stable and nfsd-acl git
branches, but are passing in the nfs-client-stable branch.

> 4.  Iozone crashes  (Bugzilla #122)
> ==================
> We have been seeing a variety of crashes with Iozone in recent tests.
> It appears that there is a slab corruption, followed by a NULL pointer
> dereference BUG, and then an Oops.

Trond has provided a patch which fixed this 'use-after-free' issue with
the nfs server, which we've confirmed solves the issue.  Thanks Trond!

  http://bugzilla.linux-nfs.org/show_bug.cgi?id=122

With iozone now working, we've discovered some other new issues.  I'll
post those shortly.

Bryce