From nobody@FreeBSD.ORG  Tue Oct 10 16:55:09 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id E9BF037B502; Tue, 10 Oct 2000 16:55:09 -0700 (PDT)
Message-Id: <20001010235509.E9BF037B502@hub.freebsd.org>
Date: Tue, 10 Oct 2000 16:55:09 -0700 (PDT)
From: ingham@i-pi.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: If options NFS is not in the kernel, mountd can cause a kernel panic
X-Send-Pr-Version: www-1.0

>Number:         21898
>Category:       kern
>Synopsis:       If options NFS is not in the kernel, mountd can cause a kernel panic
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 10 17:00:01 PDT 2000
>Closed-Date:    Mon Nov 19 15:01:44 PST 2001
>Last-Modified:  Mon Nov 19 15:02:14 PST 2001
>Originator:     Kenneth Ingham
>Release:        4.1.1-STABLE
>Organization:
Kenneth Ingham Consulting, LLC
>Environment:
FreeBSD wanmail2.ara.com 4.1.1-STABLE FreeBSD 4.1.1-STABLE #1: Tue Oct 10 23:24:37 MDT 2000     ingham@wanmail2.ara.com:/usr/src/sys/compile/WANMAIL  i386

>Description:
With the following /etc/exports file, the system would crash with a message about kernel malloc (sorry, I did not write it down) at boot time when mountd started.
/var -network 63.99.12 -mask 255.255.255.128

Given that I did not have NFS configured into the kernel, it is reasonable that something go wrong.  However, I'd prefer an appropriate message instead of a crash.
>How-To-Repeat:
See the full description above.
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: iedowse 
State-Changed-When: Sat Nov 17 11:37:01 PST 2001 
State-Changed-Why:  

If you don't have NFS in the kernel, mountd is supposed to try 
and kldload the nfs module. Maybe you had a stale module that 
it found, or had only NFS client support compiled in? Can this 
problem report be closed? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21898 
State-Changed-From-To: feedback->closed 
State-Changed-By: iedowse 
State-Changed-When: Mon Nov 19 15:01:44 PST 2001 
State-Changed-Why:  

Submitter has not seen the problem recently. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21898 
>Unformatted:
