Bug 1654 - [PATCH] In procfs, vattr doesn't contain correct value of `va_fsid'.
Summary: [PATCH] In procfs, vattr doesn't contain correct value of `va_fsid'.
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1996-09-20 07:10 UTC by miz
Modified: 1999-11-17 21:33 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description miz 1996-09-20 07:10:07 UTC 
The function `procfs_getattr()' in procfs doesn't set the value of
vap->va_fsid, so we cannot get valid information about procfs.

Fix: 

Add this line to the function `procfs_getattr()' (in procfs/procfs_vnops.c):

	vap->va_fsid = pfs->pfs_vnode->v_mount->mnt_stat.f_fsid.val[0];
How-To-Repeat: For example...

# mount -t procfs /proc /proc
# mount -t procfs /proc /mnt
# umount /mnt
# mount
/dev/wd0a on / (local)
mfs:20 on /tmp (asynchronous, local)
/dev/wd0e on /usr (local)
/dev/wd0f on /home (local)
kernfs on /kern (local, read-only)
procfs on /mnt (local)
Comment 1 Poul-Henning Kamp freebsd_committer freebsd_triage 1998-05-23 10:27:57 UTC 
State Changed
From-To: open->suspended

filesystem committer needed
Comment 2 Poul-Henning Kamp freebsd_committer freebsd_triage 1999-11-17 21:33:31 UTC 
State Changed
From-To: suspended->closed

fixed, thanks!