summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_exit.c
diff options
context:
space:
mode:
authorjulian <julian@FreeBSD.org>2004-07-18 23:36:13 +0000
committerjulian <julian@FreeBSD.org>2004-07-18 23:36:13 +0000
commita488bebcd21f1e39697ac09fdac970a06d6fb621 (patch)
tree548243b8828b679ca121764ef843b623c31cf5b9 /sys/kern/kern_exit.c
parentd538dc62fd30a8ac9beb2f57ffc4321e42569aab (diff)
downloadFreeBSD-src-a488bebcd21f1e39697ac09fdac970a06d6fb621.zip
FreeBSD-src-a488bebcd21f1e39697ac09fdac970a06d6fb621.tar.gz
When calling scheduler entrypoints for creating new threads and processes,
specify "us" as the thread not the process/ksegrp/kse. You can always find the others from the thread but the converse is not true. Theorotically this would lead to runtime being allocated to the wrong entity in some cases though it is not clear how often this actually happenned. (would only affect threaded processes and would probably be pretty benign, but it WAS a bug..) Reviewed by: peter
Diffstat (limited to 'sys/kern/kern_exit.c')
-rw-r--r--sys/kern/kern_exit.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/kern/kern_exit.c b/sys/kern/kern_exit.c
index 8efb312..a268771 100644
--- a/sys/kern/kern_exit.c
+++ b/sys/kern/kern_exit.c
@@ -526,7 +526,7 @@ retry:
PCPU_SET(switchticks, ticks);
cnt.v_swtch++;
- sched_exit(p->p_pptr, p);
+ sched_exit(p->p_pptr, td);
/*
* Make sure the scheduler takes this thread out of its tables etc.
OpenPOWER on IntegriCloud