CVS commit: [netbsd-9] src

["Martin Husemann" <martin%netbsd.org@localhost>]

Module Name:    src
Committed By:   martin
Date:           Sat Jun 27 19:23:44 UTC 2026

Modified Files:
        src/external/cddl/osnet/dist/lib/libuutil/common [netbsd-9]:
            libuutil_impl.h uu_avl.c uu_list.c uu_misc.c
        src/lib/libc/gen [netbsd-9]: arc4random.c
        src/lib/libc/stdlib [netbsd-9]: malloc.c

Log Message:
Pull up following revision(s) (requested by riastradh in ticket #2018):

        external/cddl/osnet/dist/lib/libuutil/common/uu_list.c: revision 1.2
        lib/libc/gen/arc4random.c: revision 1.51
        external/cddl/osnet/dist/lib/libuutil/common/uu_misc.c: revision 1.5
        lib/libbsdmalloc/malloc.c: revision 1.13
        external/cddl/osnet/dist/lib/libuutil/common/uu_avl.c: revision 1.2
        external/cddl/osnet/dist/lib/libuutil/common/libuutil_impl.h: revision 1.2
        lib/libc/stdlib/malloc.c: revision 1.61
        (all via patch)

arc4random(3): Use mutex_init, not mutex_unlock, in child post-fork.

Using mutex_unlock may try to wake a thread that doesn't exist in the
child, which could lead to trouble such as crash or deadlock.  But
since the child is single-threaded, it is safe to just reinitialize
the mutex memory anyway.

PR lib/59237: postfork mutex audit: mutex_init, not mutex_unlock
libbsdmalloc: Use mutex_init, not mutex_unlock, in child post-fork.

Using mutex_unlock may try to wake a thread that doesn't exist in the
child, which could lead to trouble such as crash or deadlock.  But
since the child is single-threaded, it is safe to just reinitialize
the mutex memory anyway.

PR lib/59237: postfork mutex audit: mutex_init, not mutex_unlock
osnet libuutil: Use mutex_init, not mutex_unlock, in child post-fork.

Using mutex_unlock may try to wake a thread that doesn't exist in the
child, which could lead to trouble such as crash or deadlock.  But
since the child is single-threaded, it is safe to just reinitialize
the mutex memory anyway.

PR lib/59237: postfork mutex audit: mutex_init, not mutex_unlock
old malloc(3): Use mutex_init, not mutex_unlock, in child post-fork.

Using mutex_unlock may try to wake a thread that doesn't exist in the
child, which could lead to trouble such as crash or deadlock.  But
since the child is single-threaded, it is safe to just reinitialize
the mutex memory anyway.

PR lib/59237: postfork mutex audit: mutex_init, not mutex_unlock


To generate a diff of this commit:
cvs rdiff -u -r1.1.1.1 -r1.1.1.1.48.1 \
    src/external/cddl/osnet/dist/lib/libuutil/common/libuutil_impl.h \
    src/external/cddl/osnet/dist/lib/libuutil/common/uu_list.c
cvs rdiff -u -r1.1.1.2 -r1.1.1.2.4.1 \
    src/external/cddl/osnet/dist/lib/libuutil/common/uu_avl.c
cvs rdiff -u -r1.4 -r1.4.4.1 \
    src/external/cddl/osnet/dist/lib/libuutil/common/uu_misc.c
cvs rdiff -u -r1.31 -r1.31.18.1 src/lib/libc/gen/arc4random.c
cvs rdiff -u -r1.59 -r1.59.16.1 src/lib/libc/stdlib/malloc.c

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.