diff options
| author | Gary King <gking@nvidia.com> | 2010-09-09 16:38:05 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2010-09-20 13:17:54 -0700 |
| commit | a0c42c23e8dc2d7f1c3bae407d98c709c9f6b89b (patch) | |
| tree | 59266ef3c293231255caa8843d0247bd59bdf326 /mm/bounce.c | |
| parent | 61e3fe7a310a1b99503535987ff2cc926348480e (diff) | |
| download | linux-stable-a0c42c23e8dc2d7f1c3bae407d98c709c9f6b89b.tar.gz linux-stable-a0c42c23e8dc2d7f1c3bae407d98c709c9f6b89b.tar.bz2 linux-stable-a0c42c23e8dc2d7f1c3bae407d98c709c9f6b89b.zip | |
bounce: call flush_dcache_page() after bounce_copy_vec()
commit ac8456d6f9a3011c824176bd6084d39e5f70a382 upstream.
I have been seeing problems on Tegra 2 (ARMv7 SMP) systems with HIGHMEM
enabled on 2.6.35 (plus some patches targetted at 2.6.36 to perform cache
maintenance lazily), and the root cause appears to be that the mm bouncing
code is calling flush_dcache_page before it copies the bounce buffer into
the bio.
The bounced page needs to be flushed after data is copied into it, to
ensure that architecture implementations can synchronize instruction and
data caches if necessary.
Signed-off-by: Gary King <gking@nvidia.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: Russell King <rmk@arm.linux.org.uk>
Acked-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'mm/bounce.c')
| -rw-r--r-- | mm/bounce.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/mm/bounce.c b/mm/bounce.c index a2b76a588e34..1d5fa0870ca9 100644 --- a/mm/bounce.c +++ b/mm/bounce.c @@ -115,8 +115,8 @@ static void copy_to_high_bio_irq(struct bio *to, struct bio *from) */ vfrom = page_address(fromvec->bv_page) + tovec->bv_offset; - flush_dcache_page(tovec->bv_page); bounce_copy_vec(tovec, vfrom); + flush_dcache_page(tovec->bv_page); } } |