Searched hist:160773 (Results 1 - 5 of 5) sorted by relevance
| /freebsd-11-stable/sys/amd64/ia32/ | ||
| H A D | ia32_syscall.c | diff 160773 Thu Jul 27 20:32:30 MDT 2006 jhb Unify the checking for lock misbehavior in the various syscall() implementations and adjust some of the checks while I'm here: - Add a new check to make sure we don't return from a syscall in a critical section. - Add a new explicit check before userret() to make sure we don't return with any locks held. The advantage here is that we can include the syscall number and name in syscall() whereas that info is not available in userret(). - Drop the mtx_assert()'s of sched_lock and Giant. They are replaced by the more general checks just added. MFC after: 2 weeks |
| /freebsd-11-stable/sys/arm/arm/ | ||
| H A D | syscall.c | diff 160773 Thu Jul 27 20:32:30 MDT 2006 jhb Unify the checking for lock misbehavior in the various syscall() implementations and adjust some of the checks while I'm here: - Add a new check to make sure we don't return from a syscall in a critical section. - Add a new explicit check before userret() to make sure we don't return with any locks held. The advantage here is that we can include the syscall number and name in syscall() whereas that info is not available in userret(). - Drop the mtx_assert()'s of sched_lock and Giant. They are replaced by the more general checks just added. MFC after: 2 weeks |
| H A D | trap-v4.c | diff 160773 Thu Jul 27 20:32:30 MDT 2006 jhb Unify the checking for lock misbehavior in the various syscall() implementations and adjust some of the checks while I'm here: - Add a new check to make sure we don't return from a syscall in a critical section. - Add a new explicit check before userret() to make sure we don't return with any locks held. The advantage here is that we can include the syscall number and name in syscall() whereas that info is not available in userret(). - Drop the mtx_assert()'s of sched_lock and Giant. They are replaced by the more general checks just added. MFC after: 2 weeks |
| /freebsd-11-stable/sys/sparc64/sparc64/ | ||
| H A D | trap.c | diff 160773 Thu Jul 27 20:32:30 MDT 2006 jhb Unify the checking for lock misbehavior in the various syscall() implementations and adjust some of the checks while I'm here: - Add a new check to make sure we don't return from a syscall in a critical section. - Add a new explicit check before userret() to make sure we don't return with any locks held. The advantage here is that we can include the syscall number and name in syscall() whereas that info is not available in userret(). - Drop the mtx_assert()'s of sched_lock and Giant. They are replaced by the more general checks just added. MFC after: 2 weeks |
| /freebsd-11-stable/sys/powerpc/powerpc/ | ||
| H A D | trap.c | diff 160773 Thu Jul 27 20:32:30 MDT 2006 jhb Unify the checking for lock misbehavior in the various syscall() implementations and adjust some of the checks while I'm here: - Add a new check to make sure we don't return from a syscall in a critical section. - Add a new explicit check before userret() to make sure we don't return with any locks held. The advantage here is that we can include the syscall number and name in syscall() whereas that info is not available in userret(). - Drop the mtx_assert()'s of sched_lock and Giant. They are replaced by the more general checks just added. MFC after: 2 weeks |
Completed in 291 milliseconds