public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Andreas K. Huttel <dilfridge@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] NEWS: Insert autogenerated list of fixed bugs Date: Tue, 25 Jul 2023 22:00:54 +0000 (GMT) [thread overview] Message-ID: <20230725220054.CC9663856092@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b40f5f84c41bc484d4792531a693d7583cecae0a commit b40f5f84c41bc484d4792531a693d7583cecae0a Author: Andreas K. Hüttel <dilfridge@gentoo.org> Date: Tue Jul 25 23:59:25 2023 +0200 NEWS: Insert autogenerated list of fixed bugs Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> Diff: --- NEWS | 43 +++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 41 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 105b22c682..455ba9553b 100644 --- a/NEWS +++ b/NEWS @@ -90,8 +90,47 @@ Security related changes: The following bugs are resolved with this release: - [The release manager will add the list generated by - scripts/list-fixed-bugs.py just before the release.] + [178] string: Please add strlcpy and strlcat (attached) + [14697] nptl: Behavior of exit is nonconformant with respect to + threads and stdio + [15142] stdio: Missing locking in _IO_cleanup + [18096] glob: null deref in wordexp/parse_dollars/parse_arith + [18906] stdio: fopen: ccs value may affect open mode + [24466] stdio: Feature request: provide special printf formats for + intXX_t + [25457] nss: hosts lookup fails for ipv4mapped ipv6 addresses + [28519] libc: system and popen should pass "--" between /bin/sh and + argument + [29016] stdio: popen() sets errno to ENOMEM when shell does not exist + [29591] string: wcsnlen length can overflow in page cross case. + [30053] time: strftime %s returns -1 after 2038 on 32 bits systems + [30068] stdio: incorrect printf output for integers with thousands + separator and width field (CVE-2023-25139) + [30111] time: support_descriptors_list fails after 2038 on 32 bits + systems + [30125] dynamic-link: [regression, bisected] glibc-2.37 creates new + symlink for libraries without soname + [30130] math: [s390] The _FPU_SETCW macro yields compile error with + Clang + [30156] time: Potential ntp_gettime abi break + [30235] libc: Missing fallback in getlogin if loginuid is unset + [30258] dynamic-link: sprof cannot read and display shared object + profiling data correctly + [30263] libc: Add test coverage for abs(), labs(), and llabs(). + [30305] math: Incorrect asm constraint in feraiseexcept on x86-64 + [30402] libc: FAIL: elf/tst-glibcelf + [30425] dynamic-link: Symbol lookup during dlclose may fail + unnecessarily + [30435] dynamic-link: Root dir wrongly marked as nonexist in open_path + [30477] libc: [RISCV]: time64 does not work on riscv32 + [30515] dynamic-link: _dl_find_object incorrectly returns 1 during + early startup + [30527] network: resolv_conf lock not unlocked on allocation failure + [30550] math: powerpc64le: GCC-specific code for isinf() is being used + on clang + [30555] string: strerror can incorrectly return NULL + [30579] malloc: trim_threshold in realloc lead to high memory usage + [30662] nscd: Group and password cache use errno in place of errval \f Version 2.37
reply other threads:[~2023-07-25 22:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230725220054.CC9663856092@sourceware.org \ --to=dilfridge@sourceware.org \ --cc=glibc-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).