From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 96732 invoked by alias); 25 Nov 2019 12:42:56 -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 96724 invoked by uid 89); 25 Nov 2019 12:42:56 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-9.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=H*MI:sk:21e43b6, H*f:sk:21e43b6, H*i:sk:21e43b6 X-HELO: mail-qk1-f193.google.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=subject:from:to:cc:references:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bPYEGYZzHOyKtmh5d47PWO6jSq6YZrPCf7inCDwj58w=; b=yTCGKfJyNqaKAm42OyGTn1wO90SEZu1JMv+Myg5ZXKcw/QP1xo37BBmRJ6ufl9inmq OygcsFJK17GciwmwT6M7Gcky1NUdk//YBIHxUIeDXMPKYQcqbwR0RjkHqTqzxxA2xWZz ApRBpsrTHRAz+VvLjRFkklvFoDq/TS6uQfXWZGgX7gmbiHOwThAkS2FcBAqnxdsrAohT RrKUE6cHUDYDjjRJx6LnMBKZsx+9tyxXdzbX/qmE17Wj8rzGXQW0/LGIRWA5l7uciRi3 9JSxBZN4exUZdxtuzX2fdqZd84VESXfA4xjU24UocqhyckLpswZa3qbgwNpdr+FjkVFJ Oi2w== Return-Path: Subject: Re: [PATCH 5/7] linux: Use waitid on wait4 if __NR_wait4 is not defined From: Adhemerval Zanella To: Alistair Francis Cc: GNU C Library References: <20191114144704.19002-1-adhemerval.zanella@linaro.org> <20191114144704.19002-5-adhemerval.zanella@linaro.org> <21e43b69-28a4-2d38-1faa-a4432f3cf255@linaro.org> Openpgp: preference=signencrypt Message-ID: Date: Mon, 25 Nov 2019 12:42:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <21e43b69-28a4-2d38-1faa-a4432f3cf255@linaro.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-11/txt/msg00812.txt.bz2 On 25/11/2019 09:39, Adhemerval Zanella wrote: > So it seems that __ASSUME_WAITID_PID0_P_PGID should be a safe call to > avoid such theoretical scenarios. I will rework how the flag is used > to mimic other assume usage where newer kernel version undef the flag, > so it should be simpler to remove it once the minimum kernel is lifted. > In fact I think change the __ASSUME_WAITID_PID0_P_PGID won't be much a improvement