summaryrefslogtreecommitdiffstats
path: root/drivers/regulator
diff options
context:
space:
mode:
authorEric Dumazet <eric.dumazet@gmail.com>2010-10-07 21:59:29 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2010-10-07 22:31:21 +0200
commit27b3d80a7b6adcf069b5e869e4efcc3a79f88a91 (patch)
treeaa2c9db5131dee90a0aa8155ac3dfa1ddb07619b /drivers/regulator
parentMAINTAINERS: add Samsung S5P series FIMC maintainers (diff)
downloadlinux-27b3d80a7b6adcf069b5e869e4efcc3a79f88a91.tar.xz
linux-27b3d80a7b6adcf069b5e869e4efcc3a79f88a91.zip
sysctl: fix min/max handling in __do_proc_doulongvec_minmax()
When proc_doulongvec_minmax() is used with an array of longs, and no min/max check requested (.extra1 or .extra2 being NULL), we dereference a NULL pointer for the second element of the array. Noticed while doing some changes in network stack for the "16TB problem" Fix is to not change min & max pointers in __do_proc_doulongvec_minmax(), so that all elements of the vector share an unique min/max limit, like proc_dointvec_minmax(). [akpm@linux-foundation.org: coding-style fixes] Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Americo Wang <xiyou.wangcong@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/regulator')
0 files changed, 0 insertions, 0 deletions