All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhltc@us.ibm.com>
To: John Kacur <jkacur@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] futex: Detect mismatched requeue targets
Date: Tue, 20 Oct 2009 15:51:21 -0700	[thread overview]
Message-ID: <4ADE3EE9.3090308@us.ibm.com> (raw)
In-Reply-To: <1953271756.544571256071596329.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>

John Kacur wrote:
> ----- "Darren Hart" <dvhltc@us.ibm.com> wrote:
> 
>> John Kacur wrote:
>>> Hello Darren
>>>
>>> I took your patch from commit
>> 84bc4af59081ee974dd80210e694ab59ebe51ce8
>>> and I tried to git-cherry-pick it for v2.6.31.4-rt14
>>>
>>> I had a little merge-commit to resolve. That wasn't too hard, but as
>> the 
>>> code is a bit different between the two versions, I would appreciate
>> it if 
>>> you could review the patch, and make sure that it still makes sense
>> for 
>>> v2.6.31.r-rt14
>> Hi John,
>>
>> It looks good to me.  Where did you have the conflicts?
>>
>> --
> 
> The conflict was in the futex_wait_requeue_pi function.
> That's where you really need to double check that the logic still makes sense.

Hi John,

Yes, I suspect the conflict was do to the retry: label. You should have 
already pulled in the spurious wakeup patch, so you should be fine.  The 
patch looks good to me.

Thanks,

-- 
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team

  reply	other threads:[~2009-10-20 22:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 11:30 [PATCH] futex: Detect mismatched requeue targets John Kacur
2009-10-20 11:30 ` John Kacur
2009-10-20 15:32 ` Darren Hart
2009-10-20 20:46   ` John Kacur
2009-10-20 22:51     ` Darren Hart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-14  0:36 [PATCH] futex: detect " Darren Hart
2009-08-14  0:36 ` Darren Hart

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=4ADE3EE9.3090308@us.ibm.com \
    --to=dvhltc@us.ibm.com \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.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.