From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/12545 Path: news.gmane.org!.POSTED!not-for-mail From: Julien Ramseier Newsgroups: gmane.linux.lib.musl.general Subject: Re: [PATCH] sigtimedwait: allow failing with EINTR Date: Sat, 24 Feb 2018 11:45:16 +0100 Message-ID: <9DFC885B-7454-4F81-A2BF-AED124FF80AD@gmail.com> References: <20180223214531.GJ1436@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1519469011 22076 195.159.176.226 (24 Feb 2018 10:43:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 24 Feb 2018 10:43:31 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-12561-gllmg-musl=m.gmane.org@lists.openwall.com Sat Feb 24 11:43:27 2018 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1epXIc-0005HI-2r for gllmg-musl@m.gmane.org; Sat, 24 Feb 2018 11:43:26 +0100 Original-Received: (qmail 3404 invoked by uid 550); 24 Feb 2018 10:45:29 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 3377 invoked from network); 24 Feb 2018 10:45:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=IN0H0Btb1agxjloeXPMT4w+hQdEQgsdJ7A30tl8cczY=; b=bacVpKRyic4XV7qcIa/X9B7BQuuJa/NqHGFT9Uf2LEKD6fqsRwWpAvuEnapY0YUZ1w 95CYmEgwbYMYq0XaVbGdzH+WybzlrXIygSfM7g85K5QWVKFZpQn/T0qL/dYpQP2RBCpw cfw+nwDtkTdApLwDSFLAy2YrrHLPf42pktMZ2UVa/JTXnrecVk5SMQVHjsBjunKPQD8m ievLFtfGntpk3zAhfE/Dt7fV5BBoufgbbDVtl/TS+fs4Zh73Rki5++JagKJ3x+Zz6Lk8 1cZIcvamSh4Fjn3EM39TvhaC2zkacuoarBaqKc7buoGbDQGqMLsd4c+j0B3H24k64HYn wh9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=IN0H0Btb1agxjloeXPMT4w+hQdEQgsdJ7A30tl8cczY=; b=eU8xBhzSRppqxi6Z60rmdhDb76P8e5UnbVEGp01IuVWcxhVXFtQ6X+WMp101au4Wwe LCCxeq3o64XaUhFZ48TuzGgPESk7+GnnDJuuGxyPVuYclbpch26pN6wk5ushVZjdRaoI BH6BP7gu+wb7n5+M8oViRTkZ7Zer048Hr2BDYemZwsGP/F+v8qc9YMlFE12d4Z5s8pj/ 4ExYUb6fU1L5ZVqmq+CFbwKiVml7VHIN5ZL/bCSoDu3rL39iYnmyUWNTT24776gKaaUh 2aQFC2WSHUGpBXDcnst7XsBylvWWZ+dEVY+y70AI+Z+t10YbSff4JHupv5hXBFYnSLL4 uSPQ== X-Gm-Message-State: APf1xPBei9jE9ENd4pcaMw8zrN2QFjO2+eXKOHE0A5lc6+TmRS+itcSj hYyVOXYwlWc9gOTf1dCCSjyMiy0d X-Google-Smtp-Source: AH8x224b/udYEXWxAX4nz4Ge5dFwXxKUpXlNpWnfDL9CoZvY+Exm2s1CQYyao+meFBrPHPnWzrHEqg== X-Received: by 10.80.148.239 with SMTP id t44mr6432850eda.147.1519469117490; Sat, 24 Feb 2018 02:45:17 -0800 (PST) In-Reply-To: <20180223214531.GJ1436@brightrain.aerifal.cx> X-Mailer: Apple Mail (2.3445.5.20) Xref: news.gmane.org gmane.linux.lib.musl.general:12545 Archived-At: > Le 23 f=C3=A9vr. 2018 =C3=A0 22:45, Rich Felker a = =C3=A9crit : >=20 > On Fri, Feb 23, 2018 at 01:09:35PM +0100, Julien Ramseier wrote: >> According to POSIX, sigtimedwait(2) is allowed to fail >> with EINTR, while sigwait(3) is not, so move the retry loop there. >> --- >=20 > This is a "may fail", not a "shall fail". Generally we prefer not to > support EINTR in cases where it's optional, since getting rid of them > with retry loops makes it safe to run on old kernels or > pseudo-linux-compat systems where SA_RESTART semantics were/are not > actually conforming. Is there a reason you want it to fail with EINTR? >=20 > Rich Some apps seem to rely on this, notably Python where a test case expects sigtimedwait to be interrupted when a SIGALRM is fired. I cannot find another case in musl where EINTR is inhibited (while being allowed by POSIX), are there any? - Julien=