mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Jon Masters <jcm@redhat.com>
Cc: mhban <mhban@samsung.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	DavidHowells <dhowells@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Michel Lespinasse <walken@google.com>,
	Russell King <linux@arm.linux.org.uk>,
	Chris Metcalf <cmetcalf@tilera.com>
Subject: Re: [PATCH] ARM: futex: fix clobbering oldval
Date: Tue, 6 Dec 2011 21:14:46 +0000	[thread overview]
Message-ID: <20111206211446.GB15640@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1323200328.11696.32.camel@constitution.bos.jonmasters.org>

On Tue, Dec 06, 2011 at 07:38:48PM +0000, Jon Masters wrote:
> On Tue, 2011-12-06 at 19:11 +0000, Will Deacon wrote:
> > On Tue, Dec 06, 2011 at 06:58:34PM +0000, Jon Masters wrote:
> > > 
> > > Was there ever any additional followup on this topic?
> > 
> > Yup, check commit df77abca ("ARM: 7099/1: futex: preserve oldval in SMP
> > __futex_atomic_op"). It should be in stable for all affected kernels too.
> 
> Yea, Mark flagged that patch and it was included into the kernels on our
> boards here. So far, it seems to be making some improvement, though we
> still have stuck boards and weird signal issues sometimes. We are trying
> to collect more data when this occurs (I gave the engineer concerned
> some instructions around collecting data that will be of use). So I just
> wondered if you saw any more futex issues, or if this is believe fixed.

I think this is fixed, but that doesn't mean there aren't bugs lurking
elsewhere that I'm simply not seeing. If you do get any diagnostics or
concrete debug information, please CC me on any posts to the list.

Cheers,

Will

      reply	other threads:[~2011-12-06 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22  2:53 mhban
2011-09-22 17:26 ` Will Deacon
2011-09-23  0:18   ` mhban
2011-09-23  8:43     ` Will Deacon
2011-12-06 18:58   ` Jon Masters
2011-12-06 19:11     ` Will Deacon
2011-12-06 19:38       ` Jon Masters
2011-12-06 21:14         ` Will Deacon [this message]

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=20111206211446.GB15640@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=cmetcalf@tilera.com \
    --cc=dhowells@redhat.com \
    --cc=jcm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mhban@samsung.com \
    --cc=tglx@linutronix.de \
    --cc=walken@google.com \
    /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

all inboxes | Powered by JetHome®