diff options
author | Ralf Baechle <ralf@linux-mips.org> | 2007-02-19 16:59:24 +0000 |
---|---|---|
committer | Ralf Baechle <ralf@linux-mips.org> | 2007-02-20 01:26:42 +0000 |
commit | e03b526932a9ae1ff20b47459c040f3c6407f625 (patch) | |
tree | 6c1753fc5a0497621b05c7dae9d3d686503bc5d7 /include/asm-mips/dma-mapping.h | |
parent | 269dd2b2526d046d8b43554ff27b486e2ddb3f08 (diff) | |
download | talos-obmc-linux-e03b526932a9ae1ff20b47459c040f3c6407f625.tar.gz talos-obmc-linux-e03b526932a9ae1ff20b47459c040f3c6407f625.zip |
[MIPS] Fixup copy_from_user_inatomic
From the 01408c4939479ec46c15aa7ef6e2406be50eeeca log message:
The problem is that when we write to a file, the copy from userspace to
pagecache is first done with preemption disabled, so if the source
address is not immediately available the copy fails *and* *zeros* *the*
*destination*.
This is a problem because a concurrent read (which admittedly is an odd
thing to do) might see zeros rather that was there before the write, or
what was there after, or some mixture of the two (any of these being a
reasonable thing to see).
If the copy did fail, it will immediately be retried with preemption
re-enabled so any transient problem with accessing the source won't
cause an error.
The first copying does not need to zero any uncopied bytes, and doing
so causes the problem. It uses copy_from_user_atomic rather than
copy_from_user so the simple expedient is to change copy_from_user_atomic
to *not* zero out bytes on failure.
< --- end cite --- >
This patch finally implements at least a not so pretty solution by
duplicating the relevant part of __copy_user.
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Diffstat (limited to 'include/asm-mips/dma-mapping.h')
0 files changed, 0 insertions, 0 deletions