From: anfei <anfei.zhou@gmail.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux@arm.linux.org.uk, Jamie Lokier <jamie@shareable.org>
Subject: Re: [PATCH] Flush dcache before writing into page to avoid alias
Date: Mon, 25 Jan 2010 21:33:08 +0800 [thread overview]
Message-ID: <20100125133308.GA26799@desktop> (raw)
In-Reply-To: <979dd0561001202107v4ddc1eb7xa59a7c16c452f7a2@mail.gmail.com>
Hi Andrew,
On Thu, Jan 21, 2010 at 01:07:57PM +0800, anfei zhou wrote:
> The cache alias problem will happen if the changes of user shared mapping
> is not flushed before copying, then user and kernel mapping may be mapped
> into two different cache line, it is impossible to guarantee the coherence
> after iov_iter_copy_from_user_atomic. So the right steps should be:
> flush_dcache_page(page);
> kmap_atomic(page);
> write to page;
> kunmap_atomic(page);
> flush_dcache_page(page);
> More precisely, we might create two new APIs flush_dcache_user_page and
> flush_dcache_kern_page to replace the two flush_dcache_page accordingly.
>
> Here is a snippet tested on omap2430 with VIPT cache, and I think it is
> not ARM-specific:
> int val = 0x11111111;
> fd = open("abc", O_RDWR);
> addr = mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0);
> *(addr+0) = 0x44444444;
> tmp = *(addr+0);
> *(addr+1) = 0x77777777;
> write(fd, &val, sizeof(int));
> close(fd);
> The results are not always 0x11111111 0x77777777 at the beginning as expected.
>
Is this a real bug or not necessary to support?
Thanks,
Anfei.
> Signed-off-by: Anfei <anfei.zhou@gmail.com>
> ---
> fs/fuse/file.c | 3 +++
> mm/filemap.c | 3 +++
> 2 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/fs/fuse/file.c b/fs/fuse/file.c
> index c18913a..a9f5e13 100644
> --- a/fs/fuse/file.c
> +++ b/fs/fuse/file.c
> @@ -828,6 +828,9 @@ static ssize_t fuse_fill_write_pages(struct fuse_req *req,
> if (!page)
> break;
>
> + if (mapping_writably_mapped(mapping))
> + flush_dcache_page(page);
> +
> pagefault_disable();
> tmp = iov_iter_copy_from_user_atomic(page, ii, offset, bytes);
> pagefault_enable();
> diff --git a/mm/filemap.c b/mm/filemap.c
> index 96ac6b0..07056fb 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -2196,6 +2196,9 @@ again:
> if (unlikely(status))
> break;
>
> + if (mapping_writably_mapped(mapping))
> + flush_dcache_page(page);
> +
> pagefault_disable();
> copied = iov_iter_copy_from_user_atomic(page, i, offset, bytes);
> pagefault_enable();
> --
> 1.6.3.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-01-25 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 5:07 [PATCH] Flush dcache before writing into page to avoid alias anfei zhou
2010-01-25 13:33 ` anfei [this message]
2010-01-25 19:58 ` Andrew Morton
2010-01-25 20:00 ` Russell King - ARM Linux
2010-01-27 21:59 ` Sebastian Andrzej Siewior
2010-01-27 22:12 ` Andrew Morton
2010-01-26 1:01 ` anfei zhou
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=20100125133308.GA26799@desktop \
--to=anfei.zhou@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jamie@shareable.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).