On Thu, Sep 11, 2014 at 04:53:38PM -0700, Davidlohr Bueso wrote: > On Thu, 2014-09-11 at 23:52 +0200, Thomas Gleixner wrote: > > From: Thomas Gleixner <[email protected]> > > Date: Thu, 11 Sep 2014 23:44:35 +0200 > > Subject: futex: Unlock hb->lock in futex_wait_requeue_pi() error path > > That's the second time we are bitten by bugs in when requeing, now pi. > We need to reconsider some of our testing tools to stress these paths > better, imo.
We do, yes. Per the kselftest discussion at kernel summit, I agreed to move the futextest testsuite into the kernel, function into kselftest and performance into perf, then futextest can go away. From there we can look at how to improve these tests. Sadly, the best testing we seem to have is trinity - which does a fantastic job at finding nasties. If someone wanted to start having a look at migrating the futextest tests over... I certainly wouldn't object to the help! ;-) git://git.kernel.org/pub/scm/linux/kernel/git/dvhart/futextest.git -- Darren Hart Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
