sysctl and signed net.bpf.maxbufsize variable

[elof2 at sentor.se]

Isn't this a bug?

# sysctl net.bpf.maxbufsize=3000000000
net.bpf.maxbufsize: 524288 -> -1294967296

No error message and exit status is 0.


Shouldn't net.bpf.maxbufsize be unsigned?



I would like sysctl to have a crude sanity control and return an error if 
you set a positive value but the result becomes negative.


...and also have some specific sanity control to test if you try to set a 
value waaaay out of bounds (like setting net.bpf.maxbufsize to a value greater 
than the maximum RAM).

/Elof