Robert Watson 7906271f25 In sysctl, req->td is believed always to be non-NULL, so there's no need
to test req->td for NULL values and then do somewhat more bizarre things
relating to securelevel special-casing and suser checks.  Remove the
testing and conditional security checks based on req->td!=NULL, and insert
a KASSERT that td != NULL.  Callers to sysctl must always specify the
thread (be it kernel or otherwise) requesting the operation, or a
number of current sysctls will fail due to assumptions that the thread
exists.

Obtained from:	TrustedBSD Project
Sponsored by:	DARPA, NAI Labs
Discussed with:	bde
2002-03-22 14:58:27 +00:00
..
2002-03-21 18:48:00 +00:00
2002-03-20 18:22:19 +00:00
2002-03-20 08:00:54 +00:00
2002-03-20 08:56:31 +00:00
2002-03-20 05:00:21 +00:00
2002-03-20 05:14:42 +00:00
2002-03-20 05:14:42 +00:00
2002-03-19 20:12:08 +00:00
2002-03-19 22:40:48 +00:00
2002-03-20 07:51:46 +00:00
2002-03-20 07:51:46 +00:00
2002-03-21 18:49:23 +00:00
2002-03-20 02:39:27 +00:00
2002-03-20 08:00:54 +00:00
2002-03-20 02:39:27 +00:00
2002-03-20 02:39:27 +00:00
2002-03-20 02:39:27 +00:00
2002-03-20 02:39:27 +00:00
2002-03-20 10:12:07 +00:00
2002-03-20 12:28:03 +00:00
2002-03-20 02:08:01 +00:00
2002-03-19 22:20:14 +00:00
2002-03-21 06:21:32 +00:00