[Bug 261603] sysctl kern.vnode disabled in 2003, can we re-enable now?
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261603] sysctl kern.vnode disabled in 2003, can we re-enable now?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261603] sysctl kern.vnode disabled in 2003, can we re-enable now?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261603] sysctl kern.vnode disabled in 2003, can we re-enable now?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 31 Jan 2022 12:58:46 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261603 Bug ID: 261603 Summary: sysctl kern.vnode disabled in 2003, can we re-enable now? Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: risner@stdio.com sysctl kern.vnode was disabled in commit: https://github.com/freebsd/freebsd-src/commit/acb18acfec97aa7fe26ff48f80a5c3f89c9b542d At the time the concern was with diskless machines and general it may be dangerous in its requirements for locked down memory on large RAM systems. NetBSD and OpenBSD both appear to have kern.vnode from looking at lsof's dialects. So it appears to be safe there in there implementation. Currently the lsof team is waiting on this to be enabled to merge a change to the FreeBSD dialect to use more ABI calls instead of /dev/kmem reads. That leaves the FreeBSD port of lsof unable to read zfs file's locations. There may be other ports that are difficult to maintain because this sysctl is disabled. -- You are receiving this mail because: You are the assignee for the bug.