From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 99665 invoked by alias); 4 Nov 2016 15:14:59 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 99633 invoked by uid 89); 4 Nov 2016 15:14:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:375, protect X-HELO: mx1.redhat.com Subject: Re: Caching of PID/TID after fork To: Adhemerval Zanella , libc-alpha@sourceware.org References: <87y4202blm.fsf@mid.deneb.enyo.de> <87mvidj0qw.fsf@mid.deneb.enyo.de> From: Florian Weimer Message-ID: <03127072-f944-86de-da85-cd889ce5ed76@redhat.com> Date: Fri, 04 Nov 2016 15:14:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2016-11/txt/msg00171.txt.bz2 On 10/10/2016 08:03 PM, Adhemerval Zanella wrote: > + /* Some sanity checks for clone syscall: returned ppid should be currernt Typo: “currernt” On its own, this approach looks okay, but I am worried that it sends a message that it's okay to clone processes without additional measures to protect PRNGs and things like that. Florian