From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
Waiman Long <Waiman.Long@hp.com>, Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andrey Ryabinin <a.ryabinin@samsung.com>,
Dave Jones <davej@codemonkey.org.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: sched: memory corruption on completing completions
Date: Thu, 5 Feb 2015 10:30:24 +0100 [thread overview]
Message-ID: <20150205093024.GF5029@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+55aFwJcG0eAzFJEKD0KVKF2vug-pQpZcoboue9D9SdarsjoQ@mail.gmail.com>
On Wed, Feb 04, 2015 at 04:16:54PM -0800, Linus Torvalds wrote:
>
> Why did I think we had this bug but already fixed it ? Maybe it's one
> of those things that Waiman fixed in his long delayed qspinlock
> series? Waiman?
ISTR that that would do the exact same thing, but I need to go look a
the latest paravirt code -- that's the part that we all were still
bothered with.
> Or maybe I just remember the fixes where we changed
> from a mutex to a spinlock, which fixed a very similar case for
> non-paravirtualized cases.
I think we had a non paravirt mutex case last year or so.
next prev parent reply other threads:[~2015-02-05 9:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 23:24 Sasha Levin
2015-02-04 23:46 ` Andrew Morton
2015-02-05 0:16 ` Linus Torvalds
2015-02-05 7:10 ` Ingo Molnar
2015-02-05 9:30 ` Peter Zijlstra [this message]
2015-02-05 20:44 ` Sasha Levin
2015-02-05 20:59 ` Davidlohr Bueso
2015-02-05 21:02 ` Sasha Levin
2015-02-05 21:34 ` Linus Torvalds
2015-02-05 22:37 ` Davidlohr Bueso
2015-02-05 22:57 ` Linus Torvalds
2015-02-06 6:48 ` Raghavendra K T
2015-02-06 15:00 ` Raghavendra K T
2015-02-06 12:29 ` Raghavendra K T
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=20150205093024.GF5029@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Waiman.Long@hp.com \
--cc=a.ryabinin@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.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
Powered by JetHome