New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Files appear as Directories in new SA code #9
Labels
Comments
Closed
lundman
added a commit
that referenced
this issue
Sep 2, 2015
Which the stack like: frame #2: 0xffffff800292e4a5 kernel`cache_purge frame #3: 0xffffff7f83281ee8 zfs`zfs_vnop_reclaim + 152 frame #4: 0xffffff80029468f0 kernel`vclean frame #6: 0xffffff80029463cb kernel`vnode_reclaim_internal frame #9: 0xffffff800293f4b6 kernel`vnode_create frame #10: 0xffffff7f83283c41 zfs`zfs_znode_getvnode + 513 frame #11: 0xffffff7f83288d78 zfs`zfs_zget_internal + 984 frame #12: 0xffffff7f832764c9 zfs`zfs_vfs_vget + 329 frame #13: 0xffffff800293979d kernel`namei It would seem vnop_reclaim can not call into VFS again as it already holds locks, and verifying with hfs_vnop_reclaim, they do not call cache_purge().
lundman
added a commit
that referenced
this issue
Sep 3, 2015
Which the stack like: frame #2: 0xffffff800292e4a5 kernel`cache_purge frame #3: 0xffffff7f83281ee8 zfs`zfs_vnop_reclaim + 152 frame #4: 0xffffff80029468f0 kernel`vclean frame #6: 0xffffff80029463cb kernel`vnode_reclaim_internal frame #9: 0xffffff800293f4b6 kernel`vnode_create frame #10: 0xffffff7f83283c41 zfs`zfs_znode_getvnode + 513 frame #11: 0xffffff7f83288d78 zfs`zfs_zget_internal + 984 frame #12: 0xffffff7f832764c9 zfs`zfs_vfs_vget + 329 frame #13: 0xffffff800293979d kernel`namei It would seem vnop_reclaim can not call into VFS again as it already holds locks, and verifying with hfs_vnop_reclaim, they do not call cache_purge().
lundman
added a commit
that referenced
this issue
Oct 21, 2015
Which the stack like: frame #2: 0xffffff800292e4a5 kernel`cache_purge frame #3: 0xffffff7f83281ee8 zfs`zfs_vnop_reclaim + 152 frame #4: 0xffffff80029468f0 kernel`vclean frame #6: 0xffffff80029463cb kernel`vnode_reclaim_internal frame #9: 0xffffff800293f4b6 kernel`vnode_create frame #10: 0xffffff7f83283c41 zfs`zfs_znode_getvnode + 513 frame #11: 0xffffff7f83288d78 zfs`zfs_zget_internal + 984 frame #12: 0xffffff7f832764c9 zfs`zfs_vfs_vget + 329 frame #13: 0xffffff800293979d kernel`namei It would seem vnop_reclaim can not call into VFS again as it already holds locks, and verifying with hfs_vnop_reclaim, they do not call cache_purge().
lundman
added a commit
that referenced
this issue
Jan 23, 2017
Which the stack like: frame #2: 0xffffff800292e4a5 kernel`cache_purge frame #3: 0xffffff7f83281ee8 zfs`zfs_vnop_reclaim + 152 frame #4: 0xffffff80029468f0 kernel`vclean frame #6: 0xffffff80029463cb kernel`vnode_reclaim_internal frame #9: 0xffffff800293f4b6 kernel`vnode_create frame #10: 0xffffff7f83283c41 zfs`zfs_znode_getvnode + 513 frame #11: 0xffffff7f83288d78 zfs`zfs_zget_internal + 984 frame #12: 0xffffff7f832764c9 zfs`zfs_vfs_vget + 329 frame #13: 0xffffff800293979d kernel`namei It would seem vnop_reclaim can not call into VFS again as it already holds locks, and verifying with hfs_vnop_reclaim, they do not call cache_purge().
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are not setting vnode's vtype correctly somewhere in the new SA code, or possibly the z_mode, or vap_type.
The text was updated successfully, but these errors were encountered: