Searched hist:244582 (Results 1 - 5 of 5) sorted by relevance
| /freebsd-10.1-release/sys/kern/ | ||
| H A D | kern_rmlock.c | diff 244582 Sat Dec 22 07:39:56 MST 2012 attilio Fixup r240424: On entering KDB backends, the hijacked thread to run interrupt context can still be idlethread. At that point, without the panic condition, it can still happen that idlethread then will try to acquire some locks to carry on some operations. Skip the idlethread check on block/sleep lock operations when KDB is active. Reported by: jh Tested by: jh MFC after: 1 week |
| H A D | kern_rwlock.c | diff 244582 Sat Dec 22 07:39:56 MST 2012 attilio Fixup r240424: On entering KDB backends, the hijacked thread to run interrupt context can still be idlethread. At that point, without the panic condition, it can still happen that idlethread then will try to acquire some locks to carry on some operations. Skip the idlethread check on block/sleep lock operations when KDB is active. Reported by: jh Tested by: jh MFC after: 1 week |
| H A D | kern_sx.c | diff 244582 Sat Dec 22 07:39:56 MST 2012 attilio Fixup r240424: On entering KDB backends, the hijacked thread to run interrupt context can still be idlethread. At that point, without the panic condition, it can still happen that idlethread then will try to acquire some locks to carry on some operations. Skip the idlethread check on block/sleep lock operations when KDB is active. Reported by: jh Tested by: jh MFC after: 1 week |
| H A D | kern_lock.c | diff 244582 Sat Dec 22 07:39:56 MST 2012 attilio Fixup r240424: On entering KDB backends, the hijacked thread to run interrupt context can still be idlethread. At that point, without the panic condition, it can still happen that idlethread then will try to acquire some locks to carry on some operations. Skip the idlethread check on block/sleep lock operations when KDB is active. Reported by: jh Tested by: jh MFC after: 1 week |
| H A D | kern_mutex.c | diff 244582 Sat Dec 22 07:39:56 MST 2012 attilio Fixup r240424: On entering KDB backends, the hijacked thread to run interrupt context can still be idlethread. At that point, without the panic condition, it can still happen that idlethread then will try to acquire some locks to carry on some operations. Skip the idlethread check on block/sleep lock operations when KDB is active. Reported by: jh Tested by: jh MFC after: 1 week |
Completed in 194 milliseconds