summaryrefslogtreecommitdiffstats
path: root/arch/mn10300/configs
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2015-04-06 10:26:17 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2015-04-08 14:28:45 -0700
commitcae2a173fe94ab3a437416af6f092fae2e65837e (patch)
tree964300dcf8958f0bf47767ea98e3d0e1f646db99 /arch/mn10300/configs
parent7b43b47373d40d557cd7e1a84a0bd8ebc4d745ab (diff)
downloadlinux-cae2a173fe94ab3a437416af6f092fae2e65837e.tar.bz2
x86: clean up/fix 'copy_in_user()' tail zeroing
The rule for 'copy_from_user()' is that it zeroes the remaining kernel buffer even when the copy fails halfway, just to make sure that we don't leave uninitialized kernel memory around. Because even if we check for errors, some kernel buffers stay around after thge copy (think page cache). However, the x86-64 logic for user copies uses a copy_user_generic() function for all the cases, that set the "zerorest" flag for any fault on the source buffer. Which meant that it didn't just try to clear the kernel buffer after a failure in copy_from_user(), it also tried to clear the destination user buffer for the "copy_in_user()" case. Not only is that pointless, it also means that the clearing code has to worry about the tail clearing taking page faults for the user buffer case. Which is just stupid, since that case shouldn't happen in the first place. Get rid of the whole "zerorest" thing entirely, and instead just check if the destination is in kernel space or not. And then just use memset() to clear the tail of the kernel buffer if necessary. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/mn10300/configs')
0 files changed, 0 insertions, 0 deletions