Bug 21898

Summary:	If options NFS is not in the kernel, mountd can cause a kernel panic
Product:	Base System	Reporter:	ingham <ingham>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.1.1-STABLE
Hardware:	Any
OS:	Any

Description ingham 2000-10-11 01:00:01 UTC

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.

Comment 1 iedowse freebsd_committer

2001-11-17 19:37:01 UTC

State Changed
From-To: open->feedback


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?

Comment 2 iedowse freebsd_committer

2001-11-19 23:01:44 UTC

State Changed
From-To: feedback->closed


Submitter has not seen the problem recently.