From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
anfei <anfei.zhou@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jamie Lokier <jamie@shareable.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Flush dcache before writing into page to avoid alias
Date: Wed, 27 Jan 2010 22:59:59 +0100 [thread overview]
Message-ID: <20100127215959.GC15325@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <20100125200004.GF22481@n2100.arm.linux.org.uk>
* Russell King - ARM Linux | 2010-01-25 20:00:04 [+0000]:
>On Mon, Jan 25, 2010 at 11:58:14AM -0800, Andrew Morton wrote:
>> On Mon, 25 Jan 2010 21:33:08 +0800 anfei <anfei.zhou@gmail.com> wrote:
>>
>> > 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?
>>
>> Bug. If variable `addr' has type int* then the contents of that file
>> should be 0x11111111 0x77777777. You didn't tell us what the contents
>> were in the incorrect case, but I guess it doesn't matter.
>
>FYI, from a previous email from anfei:
>
>0x44444444 0x77777777
I just wanted to query what the status of this patch is. This patch
seems to fix a real bug which causes a test suite to fail on ARM [0].
The test suite passes on my VIVT ARM with this patch.
[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524003
Sebastian
--
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-27 22:00 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
2010-01-25 19:58 ` Andrew Morton
2010-01-25 20:00 ` Russell King - ARM Linux
2010-01-27 21:59 ` Sebastian Andrzej Siewior [this message]
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=20100127215959.GC15325@Chamillionaire.breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=akpm@linux-foundation.org \
--cc=anfei.zhou@gmail.com \
--cc=jamie@shareable.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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).