| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This lets witness(4) save a stack trace on each lock acquisition.
The saved traces can be viewed in ddb(4) when showing the currently
held locks, which may help when debugging incorrect locking.
Sample output:
ddb{0}> show all locks
Process 63836 (rm) thread 0xffff8000221e52c8 (435004)
exclusive rrwlock inode r = 0 (0xfffffd8119a092c0) locked @ /usr/src/sys/ufs/ufs/ufs_vnops.c:1547
#0 witness_lock+0x419
#1 _rw_enter+0x2bb
#2 _rrw_enter+0x42
#3 VOP_LOCK+0x3f
#4 vn_lock+0x36
#5 vfs_lookup+0xa1
#6 namei+0x2b3
#7 dounlinkat+0x85
#8 syscall+0x338
#9 Xsyscall+0x128
exclusive kernel_lock &kernel_lock r = 1 (0xffffffff81e6a5f0) locked @ /usr/src/sys/arch/amd64/amd64/intr.c:525
#0 witness_lock+0x419
#1 syscall+0x2b6
#2 Xsyscall+0x128
The saving adds overhead, so it is not enabled by default. It can be
taken into use by setting sysctl kern.witness.locktrace=1 at runtime
or by defining WITNESS_LOCKTRACE in the kernel configuration.
Feedback and OK anton@
|
| |
|
|
|
|
| |
From Klemens Nanni.
|
|
|
|
|
|
| |
and drop the now redundant allocation type M_FTABLE.
OK mikeb@, bluhm@, mpi@
|
| |
|
|
|
|
|
|
| |
M_BWMETER.
ok mikeb@
|
|
|
|
| |
it down, that is ok, you can pass 0. (but it is slower)
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
what M_CANFAIL means for each.
motivation and initial diff from doug hogan
|
|
|
|
| |
after discussions with beck deraadt kettenis.
|
| |
|
|
|
|
| |
thx Jean-Philippe Ouellet
|
|
|
|
|
|
|
| |
While here, change malloc(9)'s size argument from "unsigned long" to
"size_t".
ok tedu
|
| |
|
| |
|
|
|
|
| |
feels a bit clumsy, hopefully jmc can help.
|
| |
|
|
|
|
|
| |
Diff from Jan Klemkow <j dot klemkow at wemelug dot de> on tech@.
No objection from jmc@ against this type of change.
|
| |
|
|
|
|
|
|
| |
mysterious and unused mbtypes[] array in mbuf.h.
ok tedu@, deraadt@
|
|
|
|
|
|
|
|
|
| |
to know that.
ok jmc@, though i'm tempted to remove the whole bit about being the same
as having no other flags specified as well.
Prompted by a discussion with deraadt and tedu.
|
|
|
|
|
|
|
|
| |
instead, .It is required. Thus, move .Pp and text before the .Bl,
and remove the .Pp altogether where it is not needed.
Syntax errors found by mandoc(1), also required to fix the mandoc build;
feedback and ok jmc@, and sobrado@ also supports the direction.
|
|
|
|
|
|
|
| |
- some text improvements
- remember systat(1)
ok otto
|
|
|
|
|
|
| |
spotted by and initial patch from espie@, with inputs from jmc@
ok espie@ jmc@
|
|
|
|
|
|
|
|
|
| |
Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.
OK deraadt@
|
| |
|
|
|
|
|
|
| |
adosfs has the issue and in an entirely different way. noone uses this
code so this is hte best way to handle the problem
diff from pedro who went to sleep but we need to move ahead; ok thib
|
| |
|
|
|
|
| |
ok brad
|
| |
|
|
|
|
| |
help from and ok jmc@ ok deraadt@ no objections art@
|
|
|
|
| |
prodded by beck@, feedback jmc@, ok deraadt@
|
|
|
|
| |
been worked on, so EA is pointless to maintain. go ahead jmc@
|
|
|
|
| |
ok jmc@
|
| |
|
|
|
|
|
|
| |
From NetBSD.
Tested by many people, ok art@.
|
| |
|
|
|
|
| |
Vfs -> VFS, Adosfs -> ADOSFS, etc.
|
| |
|
|
|
|
|
|
| |
- macro fixes
- kill whitespace at EOL
- use .Ox for OpenBSD, .Fx for FreeBSD
|
|
|
|
| |
md5(9): ok tedu@
|
| |
|
|
|
|
| |
ok art@
|
| |
|
| |
|
| |
|
| |
|
| |
|