From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: cache aliasing in dup_mmap
Date: Mon, 5 Oct 2009 15:46:23 +0100 [thread overview]
Message-ID: <20091005144623.GA20633@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090929191108.GA13568@n2100.arm.linux.org.uk>
On Tue, Sep 29, 2009 at 08:11:08PM +0100, Russell King - ARM Linux wrote:
> On Tue, Sep 29, 2009 at 12:30:27PM -0400, Steven Walter wrote:
> > On Sun, Mar 8, 2009 at 10:36 AM, Russell King - ARM Linux
> > <linux@arm.linux.org.uk> wrote:
> > > On Sun, Mar 08, 2009 at 12:10:29PM +0000, Russell King - ARM Linux wrote:
> > >> I don't think moving flush_cache_mm solves anything - the problem remains,
> > >> but with a different timing.
> > >
> > > On the other hand, this should solve the problem. ?I'm not 100% happy
> > > with this because we end up using the cache flush ops on the same memory
> > > several times.
> >
> > Russell
> >
> > It appears that this patch is neither in Linus' tree nor the ARM
> > master branch. ?Was a different fix committed to address the original
> > memory corruption issue?
>
> >From what I can see, there was no positive response to the actual patch
> (and no testing of the actual patch), so it doesn't get merged.
>
> Changes don't get merged until they themselves have been tested.
I've not heard anything further. I've thrown the patches into the git
tree under a separate branch now (top two):
http://ftp.arm.linux.org.uk/git/gitweb.cgi?p=linux-2.6-arm.git;a=shortlog;h=refs/heads/cup
I do feel that more work needs to be done to the 2nd patch though.
next prev parent reply other threads:[~2009-10-05 14:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e06498070903061426o5875ad13hc6328aa0d3f08ed7@mail.gmail.com>
[not found] ` <20090306225525.GB3212@n2100.arm.linux.org.uk>
[not found] ` <e06498070903062020s22222594h7be318fb9f3fdaee@mail.gmail.com>
[not found] ` <ca992f110903080105ye955070t260e6a4334186986@mail.gmail.com>
[not found] ` <20090308121029.GA21277@n2100.arm.linux.org.uk>
[not found] ` <20090308143607.GA27349@n2100.arm.linux.org.uk>
[not found] ` <e06498070909290925q55777041q6f3ecfaf9847babb@mail.gmail.com>
2009-09-29 16:30 ` cache aliasing in dup_mmap Steven Walter
2009-09-29 19:11 ` Russell King - ARM Linux
2009-10-05 14:46 ` Russell King - ARM Linux [this message]
2009-11-05 14:48 ` Russell King - ARM Linux
2009-11-13 14:49 ` Steven Walter
2009-11-16 16:30 ` Russell King - ARM Linux
2009-11-16 17:23 ` Steven Walter
2009-11-16 17:28 ` Russell King - ARM Linux
2009-11-16 21:50 ` Steven Walter
2009-11-16 22:20 ` Russell King - ARM Linux
2009-11-19 8:57 ` Russell King - ARM Linux
2009-11-19 18:08 ` Steven Walter
2009-11-23 20:31 ` Russell King - ARM Linux
2009-11-30 9:20 ` Russell King - ARM Linux
2009-11-30 19:09 ` Jamie Lokier
2009-11-30 19:23 ` Russell King - ARM Linux
2009-12-01 18:08 ` Russell King - ARM Linux
2009-12-08 22:17 ` Steven Walter
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=20091005144623.GA20633@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 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).