From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SUBJ_OBFU_PUNCT_FEW,SUBJ_OBFU_PUNCT_MANY autolearn=ham autolearn_force=no version=3.4.2 Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by inbox.vuxu.org (OpenSMTPD) with SMTP id fe0a6bd3 for ; Fri, 31 Jan 2020 04:27:25 +0000 (UTC) Received: (qmail 9626 invoked by uid 550); 31 Jan 2020 04:27:23 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 9605 invoked from network); 31 Jan 2020 04:27:23 -0000 Date: Thu, 30 Jan 2020 23:27:09 -0500 From: Rich Felker To: musl@lists.openwall.com Message-ID: <20200131042709.GD1663@brightrain.aerifal.cx> References: <20200130163853.GA1663@brightrain.aerifal.cx> <87k1583m8b.fsf@oldenburg2.str.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87k1583m8b.fsf@oldenburg2.str.redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: Rich Felker Subject: Re: [musl] [RFC] removing SYS_clock_gettime & SYS_gettimeofday On Thu, Jan 30, 2020 at 06:09:08PM +0100, Florian Weimer wrote: > * Rich Felker: > > > I think I'd like to go ahead with this patch, discussed in a previous > > thread. Does it look okay? Should I add any other syscalls that are > > absolutely not valid to use anymore (as opposed to the ones with > > optional timeouts, which I won't remove, because musl doesn't break > > valid code to catch bugs) to the list? > > I think this change needs to be reflected in the UAPI headers in some > way, too. Can you clarify? Do you mean asm/unistd.h? musl does not use it to provide sys/syscall.h. I suppose it's possible that some applications are including asm/unistd.h rather than sys/syscall.h (is there a code search that could check this for us?) but my experience has been that they use the latter, and I don't think there's much we can do about the former, at least not from our side. Rich