On 11/05/18 16:12, Alastair D'Silva wrote:
From: Alastair D'Silva <alastair@xxxxxxxxxxx> The current implementation of TID allocation, using a global IDR, may result in an errant process starving the system of available TIDs. Instead, use task_pid_nr(), as mentioned by the original author. The scenario described which prevented it's use is not applicable, as set_thread_tidr can only be called after the task struct has been populated. In the unlikely event that 2 threads share the TID and are waiting, all potential outcomes have been determined safe. Signed-off-by: Alastair D'Silva <alastair@xxxxxxxxxxx>
Thanks for the clarifying comment. The diff is painful to read but I think it makes sense :)
Reviewed-by: Andrew Donnellan <andrew.donnellan@xxxxxxxxxxx> -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnellan@xxxxxxxxxxx IBM Australia Limited -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
