From: Gratian Crisan <gratian.crisan@ni.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Gratian Crisan <gratian.crisan@ni.com>,
Julia Cartwright <julia@ni.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Darren Hart <dvhart@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] futex: Avoid violating the 10th rule of futex
Date: Fri, 08 Dec 2017 10:04:19 -0600 [thread overview]
Message-ID: <87k1xxqk8s.fsf@kerf.amer.corp.natinst.com> (raw)
In-Reply-To: <20171208124939.7livp7no2ov65rrc@hirez.programming.kicks-ass.net>
Peter Zijlstra writes:
> On Thu, Dec 07, 2017 at 05:02:40PM -0600, Gratian Crisan wrote:
>
>> Yep ... looks good to me. I've been running two targets with the
>> original reproducer for 8 hours now plus a target running the C test.
>> All of them are still going.
>>
>> I'm going to let them run overnight to make sure but I'm going to call
>> it fixed.
>
> Assuming nothing bad happens; find below the patch with a Changelog
> attached.
Looks good after overnight testing. Thank you so much.
-Gratian
next prev parent reply other threads:[~2017-12-08 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 17:56 PI futexes + lock stealing woes Julia Cartwright
2017-12-01 20:11 ` Darren Hart
2017-12-01 21:49 ` Julia Cartwright
2017-12-02 0:32 ` Darren Hart
2017-12-06 23:46 ` Peter Zijlstra
2017-12-07 2:09 ` Gratian Crisan
2017-12-07 10:45 ` Peter Zijlstra
2017-12-07 14:26 ` Peter Zijlstra
2017-12-07 14:57 ` Gratian Crisan
2017-12-07 19:50 ` Julia Cartwright
2017-12-07 23:02 ` Gratian Crisan
2017-12-08 12:49 ` [PATCH] futex: Avoid violating the 10th rule of futex Peter Zijlstra
2017-12-08 16:04 ` Gratian Crisan [this message]
2018-01-08 21:09 ` Julia Cartwright
2018-01-14 18:06 ` [tip:locking/urgent] " tip-bot for Peter Zijlstra
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=87k1xxqk8s.fsf@kerf.amer.corp.natinst.com \
--to=gratian.crisan@ni.com \
--cc=dvhart@infradead.org \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).