All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mike Galbraith <bitbucket@online.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.12.5-rt6
Date: Tue, 17 Dec 2013 15:35:45 +0100	[thread overview]
Message-ID: <52B06141.5020803@linutronix.de> (raw)
In-Reply-To: <1387290376.2399.11.camel@marge.simpson.net>

On 12/17/2013 03:26 PM, Mike Galbraith wrote:
> On Tue, 2013-12-17 at 09:16 -0500, Steven Rostedt wrote: 
>>
>>> @@ -1129,11 +1127,8 @@ unsigned long wait_task_inactive(struct task_struct *p, long match_state)
>>>  		 * is actually now running somewhere else!
>>>  		 */
>>>  		while (task_running(rq, p)) {
>>> -			if (match_state) {
>>> -				if (!unlikely(check_task_state(p, match_state)))
>>> -					return 0;
>>> +			if (match_state && !check_task_state(p, match_state))
>>
>> Ah, it was that "!unlikely(" that caused me to miss the '!'. That
>> should have been: likely(!check_task_state()). But anyway, I rather
>> just keep what you wrote and drop the unlikely altogether.
> 
> Maybe better would be to put the thing back inline, with a brief
> reference to the race.

There is similar code in
- task_is_stopped_or_traced()
- task_is_traced()

and I didn't get around to have one function for this stupid check
since the check is always a little different.

> -Mike

Sebastian

      reply	other threads:[~2013-12-17 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16  9:14 [ANNOUNCE] 3.12.5-rt6 Sebastian Andrzej Siewior
2013-12-17  7:16 ` Mike Galbraith
2013-12-17 11:31   ` Steven Rostedt
2013-12-17 12:42     ` Sebastian Andrzej Siewior
2013-12-17 14:16       ` Steven Rostedt
2013-12-17 14:26         ` Mike Galbraith
2013-12-17 14:35           ` Sebastian Andrzej Siewior [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=52B06141.5020803@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=bitbucket@online.de \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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.