Subject: kern/467: mnt_stat.f_fstypename not filled in early enough
To: None <gnats-admin>
From: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
List: netbsd-bugs
Date: 09/08/1994 14:05:38
>Number:         467
>Category:       kern
>Synopsis:       mnt_stat.f_fstypename not filled in early enough
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Sep  8 14:05:34 1994
>Originator:     der Mouse
>Organization:
	Dis-
>Release:        NetBSD/sparc 1.0_BETA
>Environment:
	Irrelevant, as far as I can tell [SPARC IPC, if it matters]
>Description:
	The f_fstypename[] values from getmntinfo() are sometimes
	blank.  I have traced this all the way back to the kernel; the
	problem appears to be that some filesystems don't fill in this
	field until a VOP_STATFS is done - which isn't done if
	MNT_NOWAIT is specified.  This is not very important at
	present, but if either of the two sets of changes I've seen to
	mount to avoid remounting filesystems when -a is used is
	adopted, it becomes much more important, because they use this
	field (this is why I classed this pr "serious").
>How-To-Repeat:
	Boot single-user
	# mount -t kernfs kernfs /kern
	# mount             # notice blank "type" field for /kern
	# df                # or anything else to force the VOP_STATFS
	# mount             # notice "type" field is now correct
>Fix:
	Presumably, make sure all filesystems fill in the
	f_fstypename[] field at mount time.  The filesystems I've had
	trouble with are kernfs, procfs, fdesc, and null.  ufs seems to
	be okay; I think nfs is too, but am not sure.

					der Mouse

			    mouse@collatz.mcrcim.mcgill.edu
>Audit-Trail:
>Unformatted:


------------------------------------------------------------------------------