[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200131042709.GD1663@brightrain.aerifal.cx>
Date: Thu, 30 Jan 2020 23:27:09 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: [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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
