All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: cache aliasing in dup_mmap
Date: Thu, 19 Nov 2009 08:57:35 +0000	[thread overview]
Message-ID: <20091119085735.GA14178@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20091116222016.GF3568@n2100.arm.linux.org.uk>

On Mon, Nov 16, 2009 at 10:20:16PM +0000, Russell King - ARM Linux wrote:
> On Mon, Nov 16, 2009 at 12:23:36PM -0500, Steven Walter wrote:
> > Yes, SIGSEGV after 88 boots, with a crash that we previously
> > identified as caused by this cache corruption issue.  Attached are the
> > patches I used, as manually backported to 2.6.18.5.  Stock 2.6.18.5
> > would reliably crash in under 1000 reboots, whereas  with my ad-hoc
> > fix (also attached) we were able to run 8000 reboots before we ended
> > the test.
> 
> I can see no reason for the difference between the two.  The backport
> looks fine.
> 
> The only difference I can see is:
> 
> - version which works
> 
> > diff --git a/src/mm/memory.c b/src/mm/memory.c
> > index 0b7a668..d0bc8c1 100644
> 
> - version which doesn't
> 
> > diff --git a/src/mm/memory.c b/src/mm/memory.c
> > index f508c60..69d8d32 100644
> 
> That first index number gives the sha1 hash of the git object storing
> this file.  Since they're different, these two patches weren't applied
> to the same file.
> 
> Could there be other changes in your tree which could be affecting the
> behaviour in this area?

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.

  reply	other threads:[~2009-11-19  8:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e06498070903061426o5875ad13hc6328aa0d3f08ed7@mail.gmail.com>
2009-03-06 22:55 ` cache aliasing in dup_mmap Russell King - ARM Linux
     [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             ` 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 [this message]
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=20091119085735.GA14178@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 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.