A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=libressl-v3.2.3 2020-09-06T06:41:03+00:00 2020-09-06T06:41:03+00:00 otto 2020-09-06T06:41:03+00:00 urn:sha1:764cad0b41a6709d8db171bee28134987f460c1a shaving off into the cache but unamp them. Pages in the cache get re-used and then a future grow of the first allocation will be hampered. Also make realloc a no-op for small shrinkage. ok deraadt@ 2020-07-06T13:33:06+00:00 pirofti 2020-07-06T13:33:06+00:00 urn:sha1:0320e8b397405d62725b086d54c65caf0669f919 This diff exposes parts of clock_gettime(2) and gettimeofday(2) to userland via libc eliberating processes from the need for a context switch everytime they want to count the passage of time. If a timecounter clock can be exposed to userland than it needs to set its tc_user member to a non-zero value. Tested with one or multiple counters per architecture. The timing data is shared through a pointer found in the new ELF auxiliary vector AUX_openbsd_timekeep containing timehands information that is frequently updated by the kernel. Timing differences between the last kernel update and the current time are adjusted in userland by the tc_get_timecount() function inside the MD usertc.c file. This permits a much more responsive environment, quite visible in browsers, office programs and gaming (apparently one is are able to fly in Minecraft now). Tested by robert@, sthen@, naddy@, kmos@, phessler@, and many others! OK from at least kettenis@, cheloha@, naddy@, sthen@ 2020-05-27T22:25:09+00:00 schwarze 2020-05-27T22:25:09+00:00 urn:sha1:865d79a51cfbda059a32d59a45f9a8981dc6b7ff The bug, present since 4.4BSD, was that a trailing dash in an option group, when the dash is not permitted as an option letter, resulted in the whole option group being returned as an argument, even though the previous option in the group was already parsed as an option: OPTS=abc ./getopt-test -a- -c arg ===>> OPT(a)ARG(-a-)ARG(-c)ARG(arg). Instead, treat the dash as an invalid option and continue parsing options: ===>> OPT(a)ERR(?-)OPT(c)ARG(arg). The undesirable behaviour was that allowing the dash as an option letter only allowed isolated dashes ("-") and trailing dashes in groups ("-a-"), but neither middle dashes in groups ("-a-b"), even though that already partially worked in 4.4BSD, nor leading dashes in groups ("--a"), even though that works on all other BSDs and on glibc. Also, while POSIX does not require that the dash can be used as an option letter at all, arguably, it encourages that letters either be fully supported or not supported at all. It is dubious whether supporting an option letter in some positions but not in others can be considered conforming. This patch makes OpenBSD behaviour identical to FreeBSD and NetBSD, improves compatibility with glibc (except that glibc does not support isolated "-"), improves compatibility with DragonFly (except that DragonFly is buggy when the dash option letter can take an optional argument but that argument is not present), improves compatibility with Illumos and Solaris 11 (except those do not support "-" and mishandle "--a"), and restores 4.4BSD behaviour for "-a-b". In no respect i'm aware of is compatibility with any other systems reduced. For the full rationale, see my mail to tech@ on 30 Mar 2020 14:26:41 +0200. Part of the problem was originally reported by an anonymous coward on tech@ on 12 Mar 2020 03:40:24 +0200, additional analysis was contributed by martijn@, and then the OP sent the final version of the patch i'm now committing on 17 Mar 2020 19:17:56 +0200. No licensing problem here because after the commit, the file does not contain a single word written by the OP. Also, the OP told me in private mail that he intends to publish the patch under the ISC license already contained in the file and that he wishes to be known by the pseudonym "0xef967c36". OK martijn@, and no objection when shown on tech@, but commit delayed to stay clear of the release. 2020-04-26T16:36:14+00:00 schwarze 2020-04-26T16:36:14+00:00 urn:sha1:e46228d31b64bf4aabfbe1e7bafe0120ba40176c queue -> list; mention "intrusive"; element -> member at one place; delete a bogus remark that maybe referred to a long-gone implementation in VAX assembly code. Much more could be improved, but i don't want to waste too much time here. 2020-04-26T13:59:56+00:00 jmc 2020-04-26T13:59:56+00:00 urn:sha1:0740c14f7f520b95c1d09ed6d9195493ec4f2119 ok schwarze kill a Tn while here... 2020-04-25T21:06:17+00:00 jca 2020-04-25T21:06:17+00:00 urn:sha1:5ac285f9542fbaa83f719d92c31dc7540b6aa10b Suggested by Evan Silberman, confirmed by jmc@ 2020-04-25T16:23:59+00:00 jca 2020-04-25T16:23:59+00:00 urn:sha1:a6b45674e18ab9626e7297f2b5433e1bc495a0e1 Suggested by eric@, input from deraadt@, ok deraadt@ eric@ 2020-04-25T14:30:05+00:00 jca 2020-04-25T14:30:05+00:00 urn:sha1:93346054dd85553cc13072024267ff8ceb9dfd19 The previous wording implied this option does nothing, which is wrong. This option does affect the way gethostbyname(3) works on OpenBSD (return IPv6 addresses if available). On some systems, it also introduces IPv4-mapped IPv6 addresses, a "feature" that we don't support. ok deraadt@ eric@ 2020-04-16T12:40:41+00:00 claudio 2020-04-16T12:40:41+00:00 urn:sha1:1fa8673e72977d152acd0df1c460be4a3ae7c289 2020-04-16T12:39:28+00:00 claudio 2020-04-16T12:39:28+00:00 urn:sha1:61e2100116cd13204d9523ed402e88424a1a65f2 based on code from musl and now similar to our strstr(). OK tb@ millert@