From d0194642f9dc14f5c1d96e39536a18dd5586341a Mon Sep 17 00:00:00 2001 From: ngie Date: Thu, 20 Jul 2017 01:12:31 +0000 Subject: [PATCH] MFC r278329: Document WITNESS_COUNT and WITNESS_NO_VNODE git-svn-id: svn://svn.freebsd.org/base/stable/10@321279 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f --- share/man/man4/witness.4 | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/share/man/man4/witness.4 b/share/man/man4/witness.4 index f529ff587..90df297af 100644 --- a/share/man/man4/witness.4 +++ b/share/man/man4/witness.4 @@ -32,7 +32,9 @@ .Nd lock validation facility .Sh SYNOPSIS .Cd options WITNESS +.Cd options WITNESS_COUNT .Cd options WITNESS_KDB +.Cd options WITNESS_NO_VNODE .Cd options WITNESS_SKIPSPIN .Sh DESCRIPTION The @@ -56,6 +58,28 @@ does not recurse on a non-recursive lock, or attempt an upgrade on a shared lock held by another thread. If any of these checks fail, then the kernel will panic. .Pp +The +.Dv WITNESS_COUNT +kernel option controls the maximum number of +.Xr witness 4 +entries that are tracked in the kernel. +The maximum number of entries can be queried via the +.Va debug.witness.count +sysctl. +It can also be set from the +.Xr loader 8 +via the +.Va debug.witness.count +environment variable. +.Pp +The +.Dv WITNESS_NO_VNODE +kernel option tells +.Xr witness 4 +to ignore locking issues between +.Xr vnode 9 +objects. +.Pp The flag that controls whether or not the kernel debugger is entered when a lock order violation is detected can be set in a variety of ways. By default, the flag is off, but if the -- 2.42.0