From: Steven Rostedt <rostedt@goodmis.org>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, mingo@elte.hu,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: + sched-fix-raciness-in-runqueue_is_locked.patch added to -mm tree
Date: Sat, 19 Sep 2009 15:21:16 -0400 [thread overview]
Message-ID: <1253388076.20020.360.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <200909191855.n8JItiko022148@imap1.linux-foundation.org>
On Sat, 2009-09-19 at 11:55 -0700, akpm@linux-foundation.org wrote:
> The patch titled
> sched(): fix raciness in runqueue_is_locked()
> has been added to the -mm tree. Its filename is
> sched-fix-raciness-in-runqueue_is_locked.patch
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
> out what to do about this
>
> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
>
> ------------------------------------------------------
> Subject: sched(): fix raciness in runqueue_is_locked()
> From: Andrew Morton <akpm@linux-foundation.org>
>
> runqueue_is_locked() is unavoidably racy due to a poor interface design.
> It does
>
> cpu = get_cpu()
> ret = some_perpcu_thing(cpu);
> put_cpu(cpu);
> return ret;
>
> Its return value is unreliable.
>
> Fix.
>
> Cc: Ingo Molnar <mingo@elte.hu>
Acked-by: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
next parent reply other threads:[~2009-09-19 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909191855.n8JItiko022148@imap1.linux-foundation.org>
2009-09-19 19:21 ` Steven Rostedt [this message]
2009-09-20 18:06 ` [tip:sched/urgent] sched: Fix raciness in runqueue_is_locked() tip-bot for Andrew Morton
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=1253388076.20020.360.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.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
all inboxes | Powered by JetHome®