OpenSolaris

Note: ON PIT have a fix available for testing from Jeff.A.Smith 

Webnfs v 1.0.7 is showing a testcase failure in every one of it's 16 testcases when run on Nevada Build 71 (nv_72)
The failures produce three separate error messages which are shown below.

We can not produce these fails when we substitute Nevada build 71 into the same environment
i.e. Same testsuite version and Hardware. Therefore we believer the problem lies within the ON workspace.

We believe this putback:

6216103 assertion failed: curdata->ex_seccnt > 0 seen again

Files:
update: usr/closed/cmd/mdb/common/modules/nfs/nfs4_exp_mdb.c
update: usr/src/uts/common/fs/nfs/nfs4_srv_ns.c
update: usr/src/uts/common/fs/nfs/nfs_export.c
update: usr/src/uts/common/nfs/export.h


is responsible for the failure which occurs on all hardware combinations
sparc & x86. There is no case where any of these tests passed.


ERROR:
sec_nego3 gasguzzler nfssec.conf tcp] check SecMode failed ...
AFFECT:
run_v3tcp
run_v3tcp
run_v3udp
run_v2tcp
run_v2udp
run_multi_v3
run_multi_v2


ERROR:
[nego3_01nullp gasguzzler nfssec.conf tcp] did NOT fail ...
expected to get (No such file or directory).
AFFECT:
run_01nullp3
run_01nullp3


ERROR:
[nego3_x82 gasguzzler nfssec.conf udp] did NOT fail ...
expected to get (I/O error).
AFFECT:
run_01nullp2
run_u3_x82
run_t2_x82
run_t3_x81-00
run_u2_x81-00
run_00nullp3
run_00nullp2
run_x83_00nullp3
run_x82_00nullp2
run_x82_00nullp2


A full list of results with journals can be accessed here:
http://diablo.ireland:8080/electron/servlet/ElectronWrapper?option=menu_results_search&Proceed=YES&TestObject=snv_72(ON)&Testsuite=webnfs&Sort1=ts.NAME
Just to be clear, the webnfs server code was never modified to
understand implicitly allowed flavors when NFS4 was
integrated into Solaris 10.  The changes putback under
6216103 are behaving correctly.

The misbehavior (corrected by 6216103 putback) was actually
masking a webnfs design deficiency.  See evaluation for more
details.

Don't use the public option on a dir that has shared descendants.  This
will ensure that no implicitly allowed flavors are inherited into the
public export.  The NFS server's webnfs code does not distinguish
explict from implicit flavors because it was never modified to 
interact with the NFSv4 namespace correctly back when NFS4 support
was integrated into Solaris.

See comments section for location of fixed binaries based on the onnv_72
snapshot.

N/A