| /freebsd/sys/kern/ |
| H A D | kern_poll.c | diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
|
| H A D | uipc_mqueue.c | diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
|
| H A D | subr_taskqueue.c | diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
|
| H A D | kern_thr.c | diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
|
| H A D | kern_umtx.c | diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
|
| H A D | sched_4bsd.c | diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
|
| H A D | kern_intr.c | diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
|
| H A D | kern_synch.c | diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
|
| /freebsd/sys/dev/hwpmc/ |
| H A D | hwpmc_mod.c | diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
diff 0f180a7cce5bed801060557dd5bdbad64318d3c6 Mon Apr 17 20:20:38 CEST 2006 John Baldwin <jhb@FreeBSD.org> Change msleep() and tsleep() to not alter the calling thread's priority
if the specified priority is zero. This avoids a race where the calling
thread could read a snapshot of it's current priority, then a different
thread could change the first thread's priority, then the original thread
would call sched_prio() inside msleep() undoing the change made by the
second thread. I used a priority of zero as no thread that calls msleep()
or tsleep() should be specifying a priority of zero anyway.
The various places that passed 'curthread->td_priority' or some variant
as the priority now pass 0.
|