[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180102021403.GK1627@brightrain.aerifal.cx>
Date: Mon, 1 Jan 2018 21:14:03 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] Add getrandom syscall wrapper function
On Mon, Jan 01, 2018 at 05:03:54PM -0500, Rich Felker wrote:
> > > and we've
> > > discussed in the past but never reached any conclusion on whether
> > > there should be a fallback when the syscall doesn't exist (running on
> > > old kernel).
> >
> > glibc does not have a fallback for this syscall there was a long
> > discussion about this, see here: https://lwn.net/Articles/711013/
> > As they never found a good solution for their fallback. I think musl
> > should also not provide a fallback.
Interesting that the biggest issue seems to have been about using file
descriptors as the fallback. That's something I never considered using
in musl since we have AT_RANDOM and sysctl on ancient kernels that
lack it. There are a small number of kernels between when sysctl
started spamming syslog with deprecation warnings and when AT_RANDOM
was added but I don't really care about those; it still works anyway.
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.
