summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)Author
2023-07-09libm: Add missing fma(3) and friends for sh3.rin
2023-07-08Make mstats() decl match prototype so this compiles with -DMSTATS.simonb
2023-07-07select(2), poll(2): Clarify return values.riastradh
2023-07-06bsdmalloc(3): fix malloc() signatureuwe
2023-07-05libbsdmalloc: Use a multiply-overflow that clang supports too.riastradh
XXX pullup-10
2023-07-05mk.conf(5): document rump variableslukem
Update mk.conf(5) with the rump variables from - lib/librumpuser/README.compileopts - sys/rump/README.compileopts Add cross-references back to mk.conf(5) in those files. Ensure that the Default: is listed last in a description, for consistency with the convention in this file.
2023-07-05libbsdmalloc: Make aligned_alloc(A, S) actually align when A > S.riastradh
XXX pullup-10
2023-07-05libbsdmalloc: Lift C11 divisibility restriction on aligned_alloc.riastradh
Restriction was lifted in C17. XXX pullup-10
2023-07-05bsdmalloc.3: fix typos in function parametersrillig
2023-07-05libbsdmalloc: Fix build with DEBUG.riastradh
Nix __P while here. XXX pullup-10
2023-07-04libc: Fix missing membar_consumer in dl_iterate_phdr.riastradh
Pairs with the existing membar_producer. XXX pullup-8 XXX pullup-9 XXX pullup-10
2023-07-04libbsdmalloc: Nix K&R definitions. Bump WARNS to 3.riastradh
2023-07-04libbsdmalloc: New man page.riastradh
XXX pullup-10
2023-07-04libbsdmalloc: Bump shlib minor.riastradh
New symbols, new minor. XXX pullup-10
2023-07-04libbsdmalloc: Nix trailing whitespace.riastradh
No functional change intended. XXX pullup-10
2023-07-04libbsdmalloc: Provide all allocator front ends and fork hooks.riastradh
Front ends: - aligned_alloc - calloc - posix_memalign Fork hooks: - _malloc_prefork - _malloc_postfork - _malloc_postfork_child Otherwise these will pull in the jemalloc definitions from libc, which (a) defeats the purpose, and (b) won't work correctly with fork and threads. Thanks to kre@ and the thread on tech-userlevel for pointing me in the right direction to making this actually work to override jemalloc: https://mail-index.netbsd.org/tech-userlevel/2023/06/30/msg013957.html Note: libbsdmalloc doesn't set errno=ENOMEM on malloc failure, but these front ends do (even aligned_alloc, which is from C11, which doesn't define ENOMEM at all, but this pacifies our aligned_alloc tests in t_posix_memalign.c). Might want to fix that. XXX pullup-10
2023-07-02getrandom(2): Reduce editorializing tone in man page.riastradh
XXX pullup-10
2023-07-02libc/shlib_version: note that *rand48* should be punted to libcompatdholland
2023-06-30getentropy(3): use .Sx to xref CAVEATSuwe
2023-06-30getrandom(2), getentropy(3): Rework man pages.riastradh
Make supportable promises. Omit needless verbiage. Give caveats with cross-references to entropy(7). Emphasize that security is necessarily relative to system configuration. XXX pullup-10
2023-06-29vis(3): Avoid nonportable MIN in portable code.riastradh
2023-06-24Fix typo in comment.msaitoh
2023-06-21libedit: fix pkg-config to really provide readline directory as intendedwiz
2023-06-20install pkg-config file for libeditwiz
version number matches portable libedit --cflags output matches portable libedit, since users probably want the readline interface
2023-06-20pam_krb5: Refuse to operate without a key to verify tickets.riastradh
New allow_kdc_spoof overrides this to restore previous behaviour which was vulnerable to KDC spoofing, because without a host or service key, pam_krb5 can't distinguish the legitimate KDC from a spoofed one. This way, having pam_krb5 enabled isn't dangerous even if you create an empty /etc/krb5.conf to use client SSO without any host services. Perhaps this should use krb5_verify_init_creds(3) instead, and thereby respect the rather obscurely named krb5.conf option verify_ap_req_nofail like the Linux pam_krb5 does, but: - verify_ap_req_nofail is default-off (i.e., vulnerable by default), - changing verify_ap_req_nofail to default-on would probably affect more things and therefore be riskier, - allow_kdc_spoof is a much clearer way to spell the idea, - this patch is a smaller semantic change and thus less risky, and - a security change with compatibility issues shouldn't have a workaround that might introduce potentially worse security issues or more compatibility issues. Perhaps this should use krb5_verify_user(3) with secure=1 instead, for simplicity, but it's not clear how to do that without first prompting for the password -- which we shouldn't do at all if we later decide we won't be able to use it anyway -- and without repeating a bunch of the logic here anyway to pick the service name. References about verify_ap_req_nofail: - mit-krb5 discussion about verify_ap_req_nofail: https://mailman.mit.edu/pipermail/krbdev/2011-January/009778.html - Oracle has the default-secure setting in their krb5 system: https://docs.oracle.com/cd/E26505_01/html/E27224/setup-148.html https://docs.oracle.com/cd/E26505_01/html/816-5174/krb5.conf-4.html#REFMAN4krb5.conf-4 https://docs.oracle.com/cd/E19253-01/816-4557/gihyu/ - Heimdal issue on verify_ap_req_nofail default: https://github.com/heimdal/heimdal/issues/1129
2023-06-20pam_ksu: No need for homedir access.riastradh
2023-06-19Fix typo. unknwon -> unknownmsaitoh
2023-06-19Fix typo in the document. From FreeBSD.msaitoh
2023-06-17Include the OpenSSL Makefile fragment so that build_install works on eachchristos
OpenSSL subdirectory.
2023-06-16fix typos in comments.andvar
2023-06-11Correct history (Brad Smith)christos
2023-06-08socket(2): change type flags list back to -taguwe
On second thought, convert the list of type flags back to -tag, but don't make it -compact. This way it's easier to see that it's related to the list above.
2023-06-06socket(2): fix macro invocation in a columnuwe
2023-06-06socket(2): use "provides" consistently in "type" descriptionsuwe
2023-06-06socket(2): use .Bl -column where appropriateuwe
2023-06-06socket(2): Move prose list of socket type summaries into a table.riastradh
2023-06-06socket(2): Tidy up markup a bit.riastradh
Use a tag list, not a literal block with hand-formatted text, for protocols and socket type flags.
2023-06-03adapt to ${CC_WNO_IMPLICIT_FALLTHROUGH}lukem
Use ${CC_WNO_IMPLICIT_FALLTHROUGH} instead of the older style more complex expressions.
2023-06-03fix various typos in comments and messages.andvar
2023-06-03bsd.own.mk: rename GCC_NO_* to CC_WNO_*lukem
Rename compiler-warning-disable variables from GCC_NO_warning to CC_WNO_warning where warning is the full warning name as used by the compiler. GCC_NO_IMPLICIT_FALLTHRU is CC_WNO_IMPLICIT_FALLTHROUGH Using the convention CC_compilerflag, where compilerflag is based on the full compiler flag name.
2023-06-03bsd.own.mk: rename to CC_WNO_ADDRESS_OF_PACKED_MEMBERlukem
Provide a single variable CC_WNO_ADDRESS_OF_PACKED_MEMBER with options for both clang and gcc, to replace CLANG_NO_ADDR_OF_PACKED_MEMBER CC_NO_ADDR_OF_PACKED_MEMBER GCC_NO_ADDR_OF_PACKED_MEMBER Using the convention CC_compilerflag, where compilerflag is based on the full compiler flag name.
2023-05-31stat_flags(3): try to improve the descriptionsuwe
List all alternative forms recognized by string_to_flags(3). Both "dump" and "nonodump" are the negative of "nodump". string_to_flags does not recognize "snap". Provide xrefs for flag descriptions where applicable.
2023-05-30Fix some const qual (Piotr Pawel Stefaniak)christos
2023-05-29libc: fix typo in comments: NO_SRSC -> NO_SRCSlukem
2023-05-25libpthread: New pthread__smt_wait to put CPU in low power for spin.riastradh
This is now distinct from pthread__smt_pause, which is for spin lock backoff with no paired wakeup. On Arm, there is a single-bit event register per CPU, and there are two instructions to manage it: - wfe, wait for event -- if event register is clear, enter low power mode and wait until event register is set; then exit low power mode and clear event register - sev, signal event -- sets event register on all CPUs (other circumstances like interrupts also set the event register and cause wfe to wake) These can be used to reduce the power consumption of spinning for a lock, but only if they are actually paired -- if there's no sev, wfe might hang indefinitely. Currently only pthread_spin(3) actually pairs them; the other lock primitives (internal lock, mutex, rwlock) do not -- they have spin lock backoff loops, but no corresponding wakeup to cancel a wfe. It may be worthwhile to teach the other lock primitives to pair wfe/sev, but that requires some performance measurement to verify it's actually worthwhile. So for now, we just make sure not to use wfe when there's no sev, and keep everything else the same -- this should fix severe performance degredation in libpthread on Arm without hurting anything else. No change in the generated code on amd64 and i386. No change in the generated code for pthread_spin.c on arm and aarch64 -- changes only the generated code for pthread_lock.c, pthread_mutex.c, and pthread_rwlock.c, as intended. PR port-arm/57437 XXX pullup-10
2023-05-25libpthread: Use __nothing, not /* nothing */, for empty macros.riastradh
No functional change intended -- just safer to do it this way in case the macros are used in if branches or comma expressions. PR port-arm/57437 (pthread__smt_pause/wake issue) XXX pullup-10
2023-05-19Add the compat calls for renamed symbols so that configure scriptsskrll
can find them. sigprocmask being the most problematic. RISC-V doesn't need the compat syscalls, but seeing them fail in ktrace is helpful.
2023-05-19No need for double semi-colonskrll
Indent END the same as ENTRY. NFCI.
2023-05-19KNFskrll
2023-05-13fix typos in comments.andvar