From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: cache aliasing in dup_mmap
Date: Tue, 1 Dec 2009 18:08:42 +0000 [thread overview]
Message-ID: <20091201180842.GC3453@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20091130092022.GA1638@n2100.arm.linux.org.uk>
On Mon, Nov 30, 2009 at 09:20:22AM +0000, Russell King - ARM Linux wrote:
> On Mon, Nov 23, 2009 at 08:31:10PM +0000, Russell King - ARM Linux wrote:
> > On Thu, Nov 19, 2009 at 01:08:01PM -0500, Steven Walter wrote:
> > > On Thu, Nov 19, 2009 at 3:57 AM, Russell King - ARM Linux
> > > <linux@arm.linux.org.uk> wrote:
> > > > I'm afraid that I have nothing further to suggest, and so I'm shelving
> > > > the patches. ?That means this problem will remain unresolved in future
> > > > kernels.
> > >
> > > I had the tester restart the reboot-loop, and so far it's done ~1200
> > > runs with no problem. I'm thinking now that either I hosed something
> > > up with the build initially, or else the tester didn't flash it
> > > correctly. 1200 runs isn't enough to be conclusive, but it's a lot
> > > better than 88. I'll let you know when we have something more
> > > definitive.
> >
> > I'd just like to keep this issue hot so it doesn't get forgotten about.
> > Are we at a conclusive point on this?
>
> Today is decision day. Do we go with these two patches or not?
Right, I've had enough of being patient and trying to get responses. I
will not be merging these fixes for 2.6.33. What's another three months
or so when it's already taken nine months to get this far already?
next prev parent reply other threads:[~2009-12-01 18:08 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
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 [this message]
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=20091201180842.GC3453@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).