Re: kern/48027: nfsserver module doesn't work

[Paul Goyette <paul%whooppee.com@localhost>]

The following reply was made to PR kern/48027; it has been noted by GNATS.

From: Paul Goyette <paul%whooppee.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/48027: nfsserver module doesn't work
Date: Mon, 8 Jul 2013 12:32:48 -0700 (PDT)

 On Mon, 8 Jul 2013, Paul Goyette wrote:
 
 > > My inclination would be to add some printfs in that initialization
 > > code to see where it does and doesn't get.
 >
 > Yes, that's the next step.  I've been trying to monitor progress via
 > syslog() calls in userland nfsd, but now need more granularity/detail.
 
 Hmmm, it seems that adding a printf() in the module initialization code 
 "fixes" the problem.  Some sort of timing issue, maybe?
 
 In any case, modunload(8) of the nfsserver module repeatable causes a 
 kernel panic as previously described. It doesn't panic immediately, and 
 in fact I've had enough time to actually confirm (with modstat(8)) that 
 the module has been unloaded.  But then it panics.  I suspect that there 
 is maybe some timer code that has not been stopped, and it still fires 
 even after the module is unloaded?
 
 Oh, I previously noted that the module init/fini code wasn't checking 
 the error status from syscall_{,dis}establish() calls.  That was not 
 correct - the status is being checked correctly.
 
 
 -------------------------------------------------------------------------
 | Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
 | Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
 | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
 | Kernel Developer |                          | pgoyette at netbsd.org  |
 -------------------------------------------------------------------------