All of lore.kernel.org
 help / color / mirror / Atom feed
From: juri.lelli@arm.com (Juri Lelli)
To: linux-arm-kernel@lists.infradead.org
Subject: suspicious RCU usage on 4.4-rc2 ARM platform
Date: Wed, 25 Nov 2015 11:53:36 +0000	[thread overview]
Message-ID: <20151125115336.GF20439@e106622-lin> (raw)
In-Reply-To: <20151124165206.GQ26643@linux.vnet.ibm.com>

On 24/11/15 08:52, Paul E. McKenney wrote:
> On Tue, Nov 24, 2015 at 04:27:50PM +0000, Juri Lelli wrote:
> > Hi Paul,
> > 
> > I'm hitting these splats while running simple hotplug tests on an ARM
> > TC2 platform. The following seems to cure it, but I don't think it never
> > made it to mainline:
> > 
> >  https://lkml.org/lkml/2015/5/12/892 
> > 
> > Any reason why?
> 
> If I remember correctly, it could result in failures on some ARM
> processors.  The problem was that this patch assumes that the CPU
> caches remain active throughout, when in fact they can be disabled at an
> inconvenient time.  As I understand it, this can result in other updates
> to that cache line being lost when the CPU is powered off.
> 
> RMK would know more.
> 

Paul, Russell,

thanks for confirming that this is a know problem; I just wanted to be
sure I'm not seeing something new. I guess I'll keep using this fix on
my box while I wait for a proper one.

Best,

- Juri

WARNING: multiple messages have this Message-ID (diff)
From: Juri Lelli <juri.lelli@arm.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	ALKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: suspicious RCU usage on 4.4-rc2 ARM platform
Date: Wed, 25 Nov 2015 11:53:36 +0000	[thread overview]
Message-ID: <20151125115336.GF20439@e106622-lin> (raw)
In-Reply-To: <20151124165206.GQ26643@linux.vnet.ibm.com>

On 24/11/15 08:52, Paul E. McKenney wrote:
> On Tue, Nov 24, 2015 at 04:27:50PM +0000, Juri Lelli wrote:
> > Hi Paul,
> > 
> > I'm hitting these splats while running simple hotplug tests on an ARM
> > TC2 platform. The following seems to cure it, but I don't think it never
> > made it to mainline:
> > 
> >  https://lkml.org/lkml/2015/5/12/892 
> > 
> > Any reason why?
> 
> If I remember correctly, it could result in failures on some ARM
> processors.  The problem was that this patch assumes that the CPU
> caches remain active throughout, when in fact they can be disabled at an
> inconvenient time.  As I understand it, this can result in other updates
> to that cache line being lost when the CPU is powered off.
> 
> RMK would know more.
> 

Paul, Russell,

thanks for confirming that this is a know problem; I just wanted to be
sure I'm not seeing something new. I guess I'll keep using this fix on
my box while I wait for a proper one.

Best,

- Juri

  reply	other threads:[~2015-11-25 11:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 16:27 suspicious RCU usage on 4.4-rc2 ARM platform Juri Lelli
2015-11-24 16:27 ` Juri Lelli
2015-11-24 16:40 ` Russell King - ARM Linux
2015-11-24 16:40   ` Russell King - ARM Linux
2015-11-24 16:52 ` Paul E. McKenney
2015-11-24 16:52   ` Paul E. McKenney
2015-11-25 11:53   ` Juri Lelli [this message]
2015-11-25 11:53     ` Juri Lelli

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=20151125115336.GF20439@e106622-lin \
    --to=juri.lelli@arm.com \
    --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.