From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Julia Lawall <julia@diku.dk>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arch@vger.kernel.org, Greg KH <greg@kroah.com>,
Andy Whitcroft <apw@canonical.com>
Subject: Re: Lots of bugs with current->state = TASK_*INTERRUPTIBLE
Date: Thu, 21 Jan 2010 11:59:42 +0100 [thread overview]
Message-ID: <20100121105940.GC5017@nowhere> (raw)
In-Reply-To: <1264071413.4283.1155.camel@laptop>
On Thu, Jan 21, 2010 at 11:56:53AM +0100, Peter Zijlstra wrote:
> On Thu, 2010-01-21 at 11:53 +0100, Frederic Weisbecker wrote:
>
> > Looks fine as spin_unlock includes a memory barrier, IIRC.
>
> It doesn't actually, see Documentation/memory-barriers.txt
>
Doh!
next prev parent reply other threads:[~2010-01-21 10:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 20:29 Lots of bugs with current->state = TASK_*INTERRUPTIBLE Steven Rostedt
2010-01-19 20:58 ` Julia Lawall
2010-01-19 20:58 ` Julia Lawall
2010-01-19 21:08 ` Steven Rostedt
2010-01-21 10:47 ` Julia Lawall
2010-01-21 10:47 ` Julia Lawall
2010-01-21 10:53 ` Frederic Weisbecker
2010-01-21 10:56 ` Peter Zijlstra
2010-01-21 10:59 ` Frederic Weisbecker [this message]
2010-01-21 17:31 ` Steven Rostedt
2010-01-21 17:31 ` Steven Rostedt
2010-01-21 18:12 ` Julia Lawall
2010-01-21 19:18 ` David Daney
2010-01-21 19:34 ` Steven Rostedt
2010-01-21 19:57 ` David Daney
2010-01-21 20:18 ` Steven Rostedt
2010-01-21 20:18 ` Steven Rostedt
2010-01-21 20:21 ` David Daney
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=20100121105940.GC5017@nowhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=greg@kroah.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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