Remove slightly oddly placed suser() call from the KTR/ALQ setup sysctl:
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:
parent
f3ed5ebbcf
commit
484cc85edb
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=162181
@ -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);
|
||||
|
Loading…
Reference in New Issue
Block a user