Searched hist:197459 (Results 1 - 2 of 2) sorted by relevance
| /freebsd-9.3-release/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/ | ||
| H A D | zfs_znode.h | diff 197459 Thu Sep 24 14:02:25 MDT 2009 pjd Before calling vflush(FORCECLOSE) mark file system as unmounted so the following vnops will fail. This is very important, because without this change vnode could be reclaimed at any point, even if we increased usecount. The only way to ensure that vnode won't be reclaimed was to lock it, which would be very hard to do in ZFS without changing a lot of code. With this change simply increasing usecount is enough to be sure vnode won't be reclaimed from under us. To be precise it can still be reclaimed but we won't be able to see it, because every try to enter ZFS through VFS will result in EIO. The only function that cannot return EIO, because it is needed for vflush() is zfs_root(). Introduce ZFS_ENTER_NOERROR() macro that only locks z_teardown_lock and never returns EIO. MFC after: 3 days |
| /freebsd-9.3-release/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/ | ||
| H A D | zfs_vfsops.c | diff 197459 Thu Sep 24 14:02:25 MDT 2009 pjd Before calling vflush(FORCECLOSE) mark file system as unmounted so the following vnops will fail. This is very important, because without this change vnode could be reclaimed at any point, even if we increased usecount. The only way to ensure that vnode won't be reclaimed was to lock it, which would be very hard to do in ZFS without changing a lot of code. With this change simply increasing usecount is enough to be sure vnode won't be reclaimed from under us. To be precise it can still be reclaimed but we won't be able to see it, because every try to enter ZFS through VFS will result in EIO. The only function that cannot return EIO, because it is needed for vflush() is zfs_root(). Introduce ZFS_ENTER_NOERROR() macro that only locks z_teardown_lock and never returns EIO. MFC after: 3 days |
Completed in 176 milliseconds