linux-kernel - Re: [tip PATCH v6 0/8] requeue pi implementation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0903302208390.3843@gandalf.stny.rr.com>
Date:	Mon, 30 Mar 2009 22:09:50 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Darren Hart <dvhltc@...ibm.com>
cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Sripathi Kodi <sripathik@...ibm.com>,
	Peter Zijlstra <peterz@...radead.org>,
	John Stultz <johnstul@...ibm.com>,
	Dinakar Guniguntala <dino@...ibm.com>,
	Ulrich Drepper <drepper@...hat.com>,
	Eric Dumazet <dada1@...mosbay.com>,
	Ingo Molnar <mingo@...e.hu>, Jakub Jelinek <jakub@...hat.com>
Subject: Re: [tip PATCH v6 0/8] requeue pi implementation




On Mon, 30 Mar 2009, Darren Hart wrote:
> 
> Darren Hart (8):
>       RFC: futex: add requeue_pi calls
>       RFC: futex: Add requeue_futex() call
>       RFC: futex: Add FUTEX_HAS_TIMEOUT flag to restart.futex.flags

I just finished reviewing the first three patches, and I don't see 
anything wrong with them. I'll review more tomorrow, but just for now, you 
can add on to the first three:

Reviewed-by: Steven Rostedt <srostedt@...hat.com>

-- Steve


>       RFC: rt_mutex: add proxy lock routines
>       RFC: futex: finish_futex_lock_pi()
>       RFC: futex: futex_lock_pi_atomic()
>       RFC: futex: futex_top_waiter()
>       RFC: futex: futex_wait_queue_me()
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/