summaryrefslogtreecommitdiffstats
path: root/fs/ufs
diff options
context:
space:
mode:
authorAlexey Dobriyan <adobriyan@gmail.com>2011-05-25 02:13:31 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2011-05-25 17:39:52 +0200
commitc196e32a111b0ee356d67acceb938ae0b5e63ef0 (patch)
tree8759b68d81eb693e391dee8f85a8d418ea5656a6 /fs/ufs
parentlru_cache: use correct type in sizeof for allocation (diff)
downloadlinux-c196e32a111b0ee356d67acceb938ae0b5e63ef0.tar.xz
linux-c196e32a111b0ee356d67acceb938ae0b5e63ef0.zip
lib: add kstrto*_from_user()
There is quite a lot of code which does copy_from_user() + strict_strto*() or simple_strto*() combo in slightly different ways. Before doing conversions all over tree, let's get final API correct. Enter kstrtoull_from_user() and friends. Typical code which uses them looks very simple: TYPE val; int rv; rv = kstrtoTYPE_from_user(buf, count, 0, &val); if (rv < 0) return rv; [use val] return count; There is a tiny semantic difference from the plain kstrto*() API -- the latter allows any amount of leading zeroes, while the former copies data into buffer on stack and thus allows leading zeroes as long as it fits into buffer. This shouldn't be a problem for typical usecase "echo 42 > /proc/x". The point is to make reading one integer from userspace _very_ simple and very bug free. Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/ufs')
0 files changed, 0 insertions, 0 deletions