diff options
| author | bde <bde@FreeBSD.org> | 2001-05-20 18:05:44 +0000 |
|---|---|---|
| committer | bde <bde@FreeBSD.org> | 2001-05-20 18:05:44 +0000 |
| commit | e37c5b4039950f6c6b0546d9d23e73a3bdf5ffae (patch) | |
| tree | ef2e0731f44f4d0f6cc157c312674262199a0633 /usr.bin/id | |
| parent | fe3ed5cadca20fbbc88e70b0e90ba5261ab16058 (diff) | |
| download | FreeBSD-src-e37c5b4039950f6c6b0546d9d23e73a3bdf5ffae.zip FreeBSD-src-e37c5b4039950f6c6b0546d9d23e73a3bdf5ffae.tar.gz | |
Use a critical region to protect almost everything in npxinit().
npxinit() didn't have the usual race because it doesn't save to curpcb,
but it may have had a worse form of it since it uses the npx when it
doesn't "own" it. I'm not sure if locking prevented this. npxinit()
is normally caled with the proc lock but not sched_lock.
Use a critical region to protect pushing of curproc's npx state to
curpcb in npxexit(). Not doing so was harmless since it at worst
saved a wrong state to a dieing pcb.
Diffstat (limited to 'usr.bin/id')
0 files changed, 0 insertions, 0 deletions
