Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]
On Thu, Sep 09, 2021 at 12:52:03AM +0200, Aurelien Jarno wrote: > control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27476 > > On 2021-09-09 00:21, Helmut Grohne wrote: > > Source: nss > > Version: 2:3.70-1 > > Severity: serious > > Tags: ftbfs > > X-Debbugs-Cc: debian-glibc@lists.debian.org > > > > A native build of nss now fails as follows: > > > > | x86_64-linux-gnu-gcc -o OBJS/nsinstall.o -c -std=c99 -g -g -fPIC -pipe > > -ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall > > -Wshadow -Werror -DXP_UNIX -DXP_UNIX -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE > > -D_BSD_SOURCE -D_POSIX_SOURCE -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT > > -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE > > -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DNSS_NO_INIT_SUPPORT > > -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT > > -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/<>/dist/include > > -I/<>/dist/public/coreconf > > -I/<>/dist/private/coreconf nsinstall.c > > | nsinstall.c: In function ‘main’: > > | nsinstall.c:70:16: error: argument 1 is null but the corresponding size > > argument 2 value is 4096 [-Werror=nonnull] > > |70 | #define GETCWD getcwd > > | |^ > > | nsinstall.c:239:8: note: in expansion of macro ‘GETCWD’ > > | 239 | cwd = GETCWD(0, PATH_MAX); > > | |^~ > > | In file included from nsinstall.c:20: > > | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ > > declared with attribute ‘write_only (1, 2)’ > > | 520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur > > | | ^~ > > | nsinstall.c:70:16: error: argument 1 is null but the corresponding size > > argument 2 value is 4096 [-Werror=nonnull] > > |70 | #define GETCWD getcwd > > | |^ > > | nsinstall.c:246:13: note: in expansion of macro ‘GETCWD’ > > | 246 | todir = GETCWD(0, PATH_MAX); > > | | ^~ > > | In file included from nsinstall.c:20: > > | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ > > declared with attribute ‘write_only (1, 2)’ > > | 520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur > > | | ^~ > > | cc1: all warnings being treated as errors > > | make[2]: *** [../../coreconf/rules.mk:292: OBJS/nsinstall.o] Error 1 > > | make[2]: Leaving directory '/<>/nss/coreconf/nsinstall' > > | make[1]: *** [debian/rules:100: override_dh_auto_build] Error 2 > > | make[1]: Leaving directory '/<>' > > | make: *** [debian/rules:195: build] Error 2 > > | dpkg-buildpackage: error: debian/rules build subprocess returned exit > > status 2 > > > > It looks very much like this is due to the glibc 2.32 upload. My reading > > of man getcwd is that the call of nss is legit (as a glibc extension). > > Maybe this is a glibc bug? > > This is indeed partially a glibc bug, already reported upstream there: > https://sourceware.org/bugzilla/show_bug.cgi?id=27476 > > Note however that the feature of calling getcwd(NULL, >0) is a GNU > extension, and that the above code doesn't define _GNU_SOURCE, so this > is also a bug in the package. That said, it's also an extension in Solaris. Mike
Processed: Re: Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]
Processing commands for cont...@bugs.debian.org: > reassign 993973 libc6-dev Bug #993973 [src:nss] nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull] Bug reassigned from package 'src:nss' to 'libc6-dev'. No longer marked as found in versions nss/2:3.70-1. Ignoring request to alter fixed versions of bug #993973 to the same values previously set > found 993973 2.32-1 Bug #993973 [libc6-dev] nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull] Marked as found in versions glibc/2.32-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 993973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[Git][glibc-team/glibc][sid] debian/patches/git-updates.diff: update from upstream stable branch.
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: e9f47f34 by Aurelien Jarno at 2021-09-09T00:54:56+02:00 debian/patches/git-updates.diff: update from upstream stable branch. - - - - - 2 changed files: - debian/changelog - debian/patches/git-updates.diff View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/e9f47f346c85747b4d6680c4ba17fff179fae3db -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/e9f47f346c85747b4d6680c4ba17fff179fae3db You're receiving this email because of your account on salsa.debian.org.
Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]
Source: nss Version: 2:3.70-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: debian-glibc@lists.debian.org A native build of nss now fails as follows: | x86_64-linux-gnu-gcc -o OBJS/nsinstall.o -c -std=c99 -g -g -fPIC -pipe -ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall -Wshadow -Werror -DXP_UNIX -DXP_UNIX -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/<>/dist/include -I/<>/dist/public/coreconf -I/<>/dist/private/coreconf nsinstall.c | nsinstall.c: In function ‘main’: | nsinstall.c:70:16: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull] |70 | #define GETCWD getcwd | |^ | nsinstall.c:239:8: note: in expansion of macro ‘GETCWD’ | 239 | cwd = GETCWD(0, PATH_MAX); | |^~ | In file included from nsinstall.c:20: | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ declared with attribute ‘write_only (1, 2)’ | 520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur | | ^~ | nsinstall.c:70:16: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull] |70 | #define GETCWD getcwd | |^ | nsinstall.c:246:13: note: in expansion of macro ‘GETCWD’ | 246 | todir = GETCWD(0, PATH_MAX); | | ^~ | In file included from nsinstall.c:20: | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ declared with attribute ‘write_only (1, 2)’ | 520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur | | ^~ | cc1: all warnings being treated as errors | make[2]: *** [../../coreconf/rules.mk:292: OBJS/nsinstall.o] Error 1 | make[2]: Leaving directory '/<>/nss/coreconf/nsinstall' | make[1]: *** [debian/rules:100: override_dh_auto_build] Error 2 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:195: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 It looks very much like this is due to the glibc 2.32 upload. My reading of man getcwd is that the call of nss is legit (as a glibc extension). Maybe this is a glibc bug? Helmut
Processed: Bug#993954 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #993954 [src:glibc] glibc: Usually FTBFS on hppa - please xfail nptl/tst-cond24 Added tag(s) pending. -- 993954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[Git][glibc-team/glibc][sid] debian/testsuite-xfail-debian.mk: whitelist test-xfail-tst-cond24 on hppa. Closes: #993954.
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 92b38d08 by Aurelien Jarno at 2021-09-08T22:00:16+02:00 debian/testsuite-xfail-debian.mk: whitelist test-xfail-tst-cond24 on hppa. Closes: #993954. - - - - - 2 changed files: - debian/changelog - debian/testsuite-xfail-debian.mk View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/92b38d08ec0bb9e34d4f03ce29f7bdac720326a8 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/92b38d08ec0bb9e34d4f03ce29f7bdac720326a8 You're receiving this email because of your account on salsa.debian.org.
Bug#989147: glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes
On 2021-09-08 13:25, Jonas Andradas wrote: > Hi, > > On Sat, 21 Aug 2021 20:14:52 +0200 Aurelien Jarno > wrote: > > Version: 2.32-0experimental0 > > > > On 2021-05-26 21:57, Salvatore Bonaccorso wrote: > > > Source: glibc > > > Version: 2.31-12 > > > Severity: important > > > Tags: security upstream > > > Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=27896 > > > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > > > [...snip...] > > > > This bug has been fixed in the glibc 2.32-0experimental0 upload to > > experimental, but wasn't close due to a typo in the changelog. Closing > > the bug manually. > > > > Is there an estimated timeline for when the experimental, fixed package would > transition to sid (and possibly testing/bookworm)? Is there an estimate for The fix is already in sid for a few days. Transition to testing/bookworm depends on many factors that are out of control of the glibc maintainers. > when the fix will be backported to bullseye? Unfortunately the fixes are not trivial to get backported, as they depend on new symbols exported through GLIBC_PRIVATE. This is something in progress, but I have no ETA so far. Best regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#989147: glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes
Hi, On Sat, 21 Aug 2021 20:14:52 +0200 Aurelien Jarno wrote: > Version: 2.32-0experimental0 > > On 2021-05-26 21:57, Salvatore Bonaccorso wrote: > > Source: glibc > > Version: 2.31-12 > > Severity: important > > Tags: security upstream > > Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=27896 > > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > [...snip...] > > This bug has been fixed in the glibc 2.32-0experimental0 upload to > experimental, but wasn't close due to a typo in the changelog. Closing > the bug manually. > Is there an estimated timeline for when the experimental, fixed package would transition to sid (and possibly testing/bookworm)? Is there an estimate for when the fix will be backported to bullseye? Thank you very much in advance, Best Regards, Jonas.
Bug#993954: glibc: Usually FTBFS on hppa - please xfail nptl/tst-cond24
Source: glibc Version: 2.32 Severity: normal Dear Maintainer, The nptl/tst-cond24 test usually fails on multi-way machines. For now, it needs to be xfailed like nptl/tst-cond25 in testsuite-xfail-debian.mk. Thanks, Dave Anglin -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 5.13.14+ (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
