From: Dmitriy Monakhov <dmonakhov@openvz.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Linux Memory Management <linux-mm@kvack.org>
Subject: [PATCH] mm:D-cache aliasing issue in cow_user_page
Date: Tue, 17 Oct 2006 13:15:37 +0400 [thread overview]
Message-ID: <8764ejqp52.fsf@sw.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]
from mm/memory.c:
1434 static inline void cow_user_page(struct page *dst, struct page *src, unsigned long va)
1435 {
1436 /*
1437 * If the source page was a PFN mapping, we don't have
1438 * a "struct page" for it. We do a best-effort copy by
1439 * just copying from the original user address. If that
1440 * fails, we just zero-fill it. Live with it.
1441 */
1442 if (unlikely(!src)) {
1443 void *kaddr = kmap_atomic(dst, KM_USER0);
1444 void __user *uaddr = (void __user *)(va & PAGE_MASK);
1445
1446 /*
1447 * This really shouldn't fail, because the page is there
1448 * in the page tables. But it might just be unreadable,
1449 * in which case we just give up and fill the result with
1450 * zeroes.
1451 */
1452 if (__copy_from_user_inatomic(kaddr, uaddr, PAGE_SIZE))
1453 memset(kaddr, 0, PAGE_SIZE);
1454 kunmap_atomic(kaddr, KM_USER0);
#### D-cache have to be flushed here.
#### It seems it is just forgotten.
1455 return;
1456
1457 }
1458 copy_user_highpage(dst, src, va);
#### Ok here. flush_dcache_page() called from this func if arch need it
1459 }
Following is the patch fix this issue:
Signed-off-by: Dmitriy Monakhov <dmonakhov@openvz.org>
---
[-- Attachment #2: d-cache-aliasing-issue-in-cow-user-page.patch --]
[-- Type: text/plain, Size: 341 bytes --]
diff --git a/mm/memory.c b/mm/memory.c
index b5a4aad..156861f 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -1452,6 +1452,7 @@ static inline void cow_user_page(struct
if (__copy_from_user_inatomic(kaddr, uaddr, PAGE_SIZE))
memset(kaddr, 0, PAGE_SIZE);
kunmap_atomic(kaddr, KM_USER0);
+ flush_dcache_page(dst);
return;
}
[-- Attachment #3: Type: text/plain, Size: 4 bytes --]
---
next reply other threads:[~2006-10-17 9:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 9:15 Dmitriy Monakhov [this message]
2006-10-19 6:33 ` [PATCH] mm:D-cache aliasing issue in cow_user_page Andrew Morton
2006-10-19 6:33 ` Andrew Morton
2006-10-19 7:00 ` David Miller
2006-10-19 7:00 ` David Miller, Andrew Morton
2006-10-19 7:17 ` Andrew Morton
2006-10-19 7:17 ` Andrew Morton
2006-10-19 7:22 ` David Miller
2006-10-19 7:22 ` David Miller, Andrew Morton
2006-10-19 7:41 ` Andrew Morton
2006-10-19 7:41 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-12-05 7:38 [PATCH] mm: D-cache " Matt Reimer
2006-12-05 21:24 ` David Miller
2006-12-06 0:57 ` Matt Reimer
2006-12-06 0:59 ` David Miller
2006-12-06 7:04 ` Matt Reimer
2006-12-06 21:19 ` Matt Reimer
2006-12-07 0:46 ` David Miller
2006-12-07 6:20 ` Matt Reimer
2006-12-07 7:22 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8764ejqp52.fsf@sw.ru \
--to=dmonakhov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.