diff options
| author | rwatson <rwatson@FreeBSD.org> | 2004-03-05 17:35:28 +0000 |
|---|---|---|
| committer | rwatson <rwatson@FreeBSD.org> | 2004-03-05 17:35:28 +0000 |
| commit | e2aad13d33454593c5ca54eb83d844666f386031 (patch) | |
| tree | de1b1af8ec6f0ec326ae8afd97cce658bb15db2c | |
| parent | 5bd82537fb46493a499f220a8b1c068f08adcf52 (diff) | |
| download | FreeBSD-src-e2aad13d33454593c5ca54eb83d844666f386031.zip FreeBSD-src-e2aad13d33454593c5ca54eb83d844666f386031.tar.gz | |
Put "failed to set signal flags properly for ast()" check under
DIAGNOSTIC instead of INVARIANTS. INVARIANTS is intended for tests
that don't substantially change code flow or behavior (passive), but
this test required locking both the proc lock and scheduler lock
in order to execute. It also appears to be a very advisory diagnostic
as opposed to an invariant violation.
Following discussion with: bde
| -rw-r--r-- | sys/kern/subr_trap.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/kern/subr_trap.c b/sys/kern/subr_trap.c index a556d0e..3e40672 100644 --- a/sys/kern/subr_trap.c +++ b/sys/kern/subr_trap.c @@ -83,7 +83,7 @@ userret(td, frame, oticks) CTR3(KTR_SYSC, "userret: thread %p (pid %d, %s)", td, p->p_pid, p->p_comm); -#ifdef INVARIANTS +#ifdef DIAGNOSTIC /* Check that we called signotify() enough. */ PROC_LOCK(p); mtx_lock_spin(&sched_lock); |
