sysctl: min/max bounds are optional
authorEric Dumazet <eric.dumazet@gmail.com>
Fri, 15 Oct 2010 21:34:12 +0000 (14:34 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Fri, 15 Oct 2010 21:42:24 +0000 (14:42 -0700)
commita9febbb4bd1302b6f01aa1203b0a804e4e5c9e25
tree7367bee631d0a050e0d392102dd652ec48a57a08
parent5a2b3ef4559f3d0ef58cbfb723f528f1c6b2e601
sysctl: min/max bounds are optional

sysctl check complains with a WARN() when proc_doulongvec_minmax() or
proc_doulongvec_ms_jiffies_minmax() are used by a vector of longs (with
more than one element), with no min or max value specified.

This is unexpected, given we had a bug on this min/max handling :)

Reported-by: Jiri Slaby <jirislaby@gmail.com>
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: David Miller <davem@davemloft.net>
Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
kernel/sysctl_check.c