diff options
| author | pjd <pjd@FreeBSD.org> | 2007-04-01 13:08:05 +0000 |
|---|---|---|
| committer | pjd <pjd@FreeBSD.org> | 2007-04-01 13:08:05 +0000 |
| commit | b078229dadca84619da1e229598a8fa2b3af2a02 (patch) | |
| tree | 8ef9a56efaed990b7ed2b7e4224dc94523a2568c /sys | |
| parent | 9ab068af59ebf9bb174628c4515ac6a92c10c950 (diff) | |
| download | FreeBSD-src-b078229dadca84619da1e229598a8fa2b3af2a02.zip FreeBSD-src-b078229dadca84619da1e229598a8fa2b3af2a02.tar.gz | |
I think the code I'm removing here is completely bogus.
vfs_flags field is used for VFCF_* flags which are given at file system
driver creation time (via VFS_SET(9)) macro.
What this code did was bascially this:
If file system registers itself with VFCF_UNICODE flag (stores file names
as Unicode), it will gain MNT_SOFTDEP flag (UFS soft-updates).
If file system registers itself with VFCF_LOOPBACK flag (aliases some other
mounted FS), it will gain MNT_SUIDDIR flag (special handling of SUID on
dirs).
The latter will be quite dangerous, but those flags are reset later in
vfs_domount().
MFC after: 1 month
Diffstat (limited to 'sys')
| -rw-r--r-- | sys/kern/vfs_mount.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/sys/kern/vfs_mount.c b/sys/kern/vfs_mount.c index fc44e6c..2f80230 100644 --- a/sys/kern/vfs_mount.c +++ b/sys/kern/vfs_mount.c @@ -482,9 +482,6 @@ vfs_mount_alloc(struct vnode *vp, struct vfsconf *vfsp, mp->mnt_vfc = vfsp; vfsp->vfc_refcount++; /* XXX Unlocked */ mp->mnt_stat.f_type = vfsp->vfc_typenum; - MNT_ILOCK(mp); - mp->mnt_flag |= vfsp->vfc_flags & MNT_VISFLAGMASK; - MNT_IUNLOCK(mp); mp->mnt_gen++; strlcpy(mp->mnt_stat.f_fstypename, vfsp->vfc_name, MFSNAMELEN); mp->mnt_vnodecovered = vp; |
