d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove slightly oddly placed suser() call from the KTR/ALQ setup sysctl:

Browse Source 
it was present only in the enable path, not the disable path, which one
presumes would be equally of interest.  Either way, it was not needed,
as the sysctl framework already calls suser() if the operation is a
write operation, which configuration requests are.

Sponsored by:	nCircle Network Security, Inc.
This commit is contained in:
Robert Watson 2006-09-09 16:09:01 +00:00
parent f3ed5ebbcf
commit 484cc85edb
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=162181
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
sys/kern/kern_ktr.c
View File

@ -163,9 +163,6 @@ sysctl_debug_ktr_alq_enable(SYSCTL_HANDLER_ARGS)
if (enable) {
if (ktr_alq_enabled)
return (0);
error = suser(curthread);
if (error)
return (error);
error = alq_open(&ktr_alq, (const char *)ktr_alq_file,
req->td->td_ucred, ALQ_DEFAULT_CMODE,
sizeof(struct ktr_entry), ktr_alq_depth);