https://bugzilla.kernel.org/show_bug.cgi?id=203105 Michael Kerrisk (mtk.manpages@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |CODE_FIX --- Comment #3 from Michael Kerrisk (mtk.manpages@xxxxxxxxx) --- Hello Jakub, Okay, now I understand what you meant to say. (Perhaps I should have worked it out to begin with!) The text of the page says: CLONE_CHILD_SETTID (since Linux 2.5.49) Store the child thread ID at the location ctid in the child's memory. The store operation completes before clone() returns control to user space. When I read that text, then because the first sentence meantipns the child's memory, I naturally read the second sentence as implying *before clone() returns in the child*. But I also that other's might not take that implication, so I changed the text to read: CLONE_CHILD_SETTID (since Linux 2.5.49) Store the child thread ID at the location ctid in the child's memory. The store operation completes before clone() returns control to user space in the child process. Thanks, Michael -- You are receiving this mail because: You are on the CC list for the bug.