[Bug 1944468] Re: Electron applications all crash upon launch

[Florian Weimer]

Doesn't Electron need regular security updates for its browser engine?
If true, these projects really need to figure out how to rebuild
regularly against current Electron versions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468

Title:
  Electron applications all crash upon launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1944468/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1951340] Re: libdl.so missing in impish and jammy

[Florian Weimer]

libdl.a is empty, it exists only to make -ldl work. This is a curiosity
in some Cmake-based build systems. We had to do some rebuilds to make
those legacy file references go away, for example:

https://bugzilla.redhat.com/show_bug.cgi?id=1977878

** Bug watch added: Red Hat Bugzilla #1977878
   https://bugzilla.redhat.com/show_bug.cgi?id=1977878

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951340

Title:
  libdl.so missing in impish and jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1951340/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945072] Re: getaddrinfo crashes on negative answers after Truncated retry

[Florian Weimer]

I tried to replicate it with this patch to the test suite:

diff --git a/resolv/tst-bug18665-tcp.c b/resolv/tst-bug18665-tcp.c
index 9b1ff0fbd8..e8e0d12bb7 100644
--- a/resolv/tst-bug18665-tcp.c
+++ b/resolv/tst-bug18665-tcp.c
@@ -47,6 +47,41 @@ response (const struct resolv_response_context *ctx,
   struct resolv_response_flags flags = {.tc = true};
   resolv_response_init (b, flags);
   resolv_response_add_question (b, qname, qclass, qtype);
+
+  if (qtype == T_A)
+{
+  resolv_response_section (b, ns_s_an);
+  resolv_response_open_record (b, qname, qclass, T_CNAME, 600);
+  const char *alias = "somewhat.longish.cname.example";
+  resolv_response_add_name (b, alias);
+  resolv_response_close_record (b);
+
+  for (int i = 0; i < 35; ++i)
+{
+  resolv_response_open_record (b, alias, qclass, T_A, 600);
+  const char ipv4[4] = {10, 255, 255, i};
+  resolv_response_add_data (b, ipv4, sizeof (ipv4));
+  resolv_response_close_record (b);
+}
+}
+  else
+{
+  resolv_response_section (b, ns_s_ns);
+  resolv_response_open_record (b, qname, qclass, T_SOA, 600);
+  resolv_response_add_name (b, "ns1.example");
+  resolv_response_add_name (b, "hostmaster.example");
+  const uint32_t values[5] =
+{
+  htonl (2021092901),
+  htonl (600),
+  htonl (600),
+  htonl (36),
+  htonl (600),
+};
+  resolv_response_add_data (b, values, sizeof (values));
+  resolv_response_close_record (b);
+}
+
   return;
 }
 
But I do not get a crash with current master. I think we really need those 
packet captures, sorry.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945072

Title:
  getaddrinfo crashes on negative answers after Truncated retry

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1945072/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945072] Re: getaddrinfo crashes on negative answers after Truncated retry

[Florian Weimer]

Thanks for the update. A packet capture could still be useful, and also
a backtrace (with symbols) from the crash.

We have an upstream test case which is supposed to cover various packet
sizes, and I am going to try to adopt it to cover this. The code itself
is pretty much impenetrable. We have been slowly cleaning it up, but
there is still a lot left to do.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945072

Title:
  getaddrinfo crashes on negative answers after Truncated retry

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1945072/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945072] Re: getaddrinfo crashes on negative answers after Truncated retry

[Florian Weimer]

Would you be able to share packet capture (tcpdump -s 0 -w CAPTURE-FILE,
and then the output of CAPTURE-FILE)?  Thanks.

As far as I can tell, “getent ahosts large-a.t.enyo.de” results in DNS
activity that matches the preconditions in your description, but I don't
observe a crash (even with Ubuntu 18.04 LTS and its 2.27-based glibc).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945072

Title:
  getaddrinfo crashes on negative answers after Truncated retry

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1945072/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943124] Re: Upgrade fails due to "text file busy"

[Florian Weimer]

To me, the clue is the ETXTBSY for ld-linux-x86-64.so.2.dpkg-new (with
the suffix). I can't quite see how this could become used without a
reference from /etc/ld.so.cache. And I think according to the ldconfig
heuristic, ld-linux-x86-64.so.2.dpkg-new is considered a newer version
than ld-linux-x86-64.so.2. (Maybe we should not apply this heuristic if
a file with the exact soname exists.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943124

Title:
  Upgrade fails due to "text file busy"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943124] Re: Upgrade fails due to "text file busy"

[Florian Weimer]

The ldconfig aspect is just a guess on my part. Assuming that
/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2.dpkg-new was not created by
renaming of /lib/x86_64-linux-gnu/ld-linux-x86-64.so, it is unclear to
me how a process would end up using it—it has to be listed in
/etc/ld.so.cache for that to happen.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943124

Title:
  Upgrade fails due to "text file busy"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943049] Re: Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'

[Florian Weimer]

Just to be clear, this is a container host bug which needs to be fixed.
glibc works fine on real Linux kernels with and without clone3 support.

There is *supposed* to be a generic fix for this in docker and runc, but
that broke temporarily upstream when support for other system calls
(with higher system call numbers than clone3) was added. As far as I
know, podman does not have the generic fix, so it currently needs to be
updated for each new system call individually. (None of this depends on
the system calls actually implemented in the host kernel, just to be
clear.)

From a philosophical perspective, I also object to the notion that the
container hosts developers get to define the Linux system call
interface. That should be up to Linux maintainers in collaboration with
userspace developers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943049

Title:
  Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm
  -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb
  /var/cache/apt/*.bin || true'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1943049/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943124] Re: Upgrade fails due to "text file busy"

[Florian Weimer]

Is it possible that this is a result of running ldconfig early, before
the `.dpkg-new` files have been renamed into place? If yes, can you stop
doing that?  If not, we could perhaps teach ldconfig to ignore .dpkg-new
files. See _dl_is_dso in elf/dl-is_dso.h.

This may have been a result of the upstream removal of symbolic links.
Before, those .dpkg-new files probably weren't created by dpkg.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943124

Title:
  Upgrade fails due to "text file busy"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1933879] [NEW] libc6-lse does not replace ld.so with LSE enabled version

[Florian Weimer]

* Kyle Huey:

> This is a problem for porting rr (https://rr-project.org/) to AArch64.
> The old-style exclusive load/store atomics are inherently non-
> deterministic and cannot be handled by rr. And not replacing ld.so with
> an LSE version means every program contains code that can execute the
> old-style atomics (in practice only programs with threads actually
> trigger that codepath in ld.so, but that's still most interesting
> programs).

Would outline atomics solve this rr issue?

Thanks,
Florian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933879

Title:
  libc6-lse does not replace ld.so with LSE enabled version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1933879/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916485] Re: test -x fails inside shell scripts in containers

[Florian Weimer]

To paper over the faccessat2 issue, a libseccomp update is enough *if*
the container runtime already knows about the faccessat2 system call and
mentions it in its profiles. But with the current design, every new
system call will need similar updates to several components (not just
libseccomp) just to produce the ENOSYS error, which is not a sustainable
development model. Hence the runc pull request mentioned in comment 8.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916485

Title:
  test -x fails inside shell scripts in containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916485/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916749] Re: plf-colony simple.cc test fails with "stderr: dis_syslink(ppc)(theInstr)" on ppc64el with glibc 2.33

[Florian Weimer]

This is a valgrind bug: https://bugs.kde.org/show_bug.cgi?id=431157

** Bug watch added: KDE Bug Tracking System #431157
   https://bugs.kde.org/show_bug.cgi?id=431157

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916749

Title:
  plf-colony simple.cc test fails with "stderr:
  dis_syslink(ppc)(theInstr)" on ppc64el with glibc 2.33

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916749/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916485] Re: test -x fails inside shell scripts in containers

[Florian Weimer]

Patches have been proposed for that, but were rejected:

[PATCH] syscalls: Document OCI seccomp filter interactions & workaround
https://lore.kernel.org/linux-api/87lfer2c0b@oldenburg2.str.redhat.com/

[RFC PATCH] Linux: Add seccomp probing to faccessat2
https://sourceware.org/pipermail/libc-alpha/2020-November/119955.html

We *really* need to clean this up properly, so that we are prepared if
we need to add a new system call as part of a security fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916485

Title:
  test -x fails inside shell scripts in containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916485/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916485] Re: test -x fails inside shell scripts in containers

[Florian Weimer]

Yes, it's a seccomp issue that needs to be fixed on the container host.

There's a generic kludge here:
https://github.com/opencontainers/runc/pull/2750

Recent docker/podman version be okay as well, but the fix (logically,
not explicitly) depends on other package updates too (e.g., libseccomp).

Most container hosts on offer allow disabling seccomp filters in some
way, but that's not entirely standardized.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916485

Title:
  test -x fails inside shell scripts in containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916485/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1907298]

[Florian Weimer]

Reported to linuxppc-dev: https://lists.ozlabs.org/pipermail/linuxppc-
dev/2021-January/223194.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907298

Title:
  glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1907298/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906250]

[Florian Weimer]

Fixed for glibc 2.33 via:

commit 84ba719b260551918965d0a433914de683087645
Author: Florian Weimer 
Date:   Fri Dec 4 09:13:43 2020 +0100

elf: Add endianness markup to ld.so.cache (bug 27008)

Use a reserved byte in the new format cache header to indicate whether
the file is in little endian or big endian format.  Eventually, this
information could be used to provide a unified cache for qemu-user
and similiar scenarios.

Reviewed-by: Adhemerval Zanella  

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906250

Title:
  Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using
  qemu-s390x on x86_64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1906250/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906250] Re: Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64.

[Florian Weimer]

** Bug watch added: Sourceware.org Bugzilla #27008
   https://sourceware.org/bugzilla/show_bug.cgi?id=27008

** Also affects: glibc via
   https://sourceware.org/bugzilla/show_bug.cgi?id=27008
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906250

Title:
  Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using
  qemu-s390x on x86_64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1906250/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898902]

[Florian Weimer]

The manual pages are maintained by the Linux man-pages project.  I
submitted a patch: https://lore.kernel.org/linux-
man/87zh4vdc7d@oldenburg2.str.redhat.com/T/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898902

Title:
  (doc?) locale-gen disagrees with locale(5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1898902/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898902] Re: (doc?) locale-gen disagrees with locale(5)

[Florian Weimer]

Please note that the manual pages come from the Linux man-pages project,
not glibc. I posted a patch: https://lore.kernel.org/linux-
man/87zh4vdc7d@oldenburg2.str.redhat.com/T/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898902

Title:
  (doc?) locale-gen disagrees with locale(5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1898902/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 386558]

[Florian Weimer]

FD_SET fortification was implemented in glibc 2.15.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/386558

Title:
  RLIMIT_NOFILE > FD_SETSIZE seems to cause select() to corrupt the
  stack

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/386558/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

[Florian Weimer]

Is this a native s390x build, or something qemu-user? Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886814

Title:
  posix_spawn usage in gnu make causes failures on s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869364] Re: glibc pwd/test-getpw test failures in autopkgtest

[Florian Weimer]

I believe this is related to the kind of NSS modules which are active on
the system. I believe it's related how the way errno is (not) set. I'm
not sure if this is a bug in the NSS framework, in the NSS module, or
simply a case of incorrect test expectations.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869364

Title:
  glibc pwd/test-getpw test failures in autopkgtest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1869364/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867675] Re: Install failure for libc6 2.31-0ubuntu6 on armhf

[Florian Weimer]

> - somehow make libseccomp handle "unknown" syscalls, and perhaps
> allow them (instead of blocking)? (not exactly sure how it's
> handling these, so I'd have to read up on that); probably that's the
> same (similar) as changing our "whitelist" to a "blacklist" (which
> could weaken security)

Blocking not otherwise specified system calls with ENOSYS instead of
EPERM generally has this effect.  Some container runtimes incorrectly
use EPERM, though.  I don't know if this is the issue with Docker here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867675

Title:
  Install failure for libc6 2.31-0ubuntu6 on armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867675/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 565002] Re: ldopen failing with relative path when linux capability is set

[Florian Weimer]

Yes, this is deliberate behavior for execve with an AT_SECURE
transition. Environmental parameters such as the path to the executable
are not trustworthy in that case.

For safe use of Java with capabilities you will have to use a
restricted, custom launcher. I don't think such a thing exists today.
That launcher should be able to avoid the use of $ORIGIN, too.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/565002

Title:
  ldopen failing with relative path when linux capability is set

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/565002/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861353] Re: libc6-dev:amd64 is not co-installable with libc6-dev:s390x

[Florian Weimer]

This file describes the interface of the libmvec library. There is no
port for s390x yet, which is why there is nothing there on s390x. Its
contents will depend on what has been implemented, too.

The file is architecture-specific and really should be in multiarch
subdirectory.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861353

Title:
  libc6-dev:amd64 is not co-installable with libc6-dev:s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1861353/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842730]

[Florian Weimer]

Fixed for glibc 2.31.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842730

Title:
  glibc: dlopen crash after a previously failed call to dlopen

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1842730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851263] Re: Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable

[Florian Weimer]

I think what Romain is asking is to rebase along release/2.27/master,
and not a different upstream version. If you don't do that, you have to
evaluate each upstream commit individually for backporting.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851263

Title:
  Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1851263/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842730]

[Florian Weimer]

Patch posted: https://gnutoolchain-gerrit.osci.io/r/c/glibc/+/471

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842730

Title:
  glibc: dlopen crash after a previously failed call to dlopen

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1842730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842730]

[Florian Weimer]

I think I have a patch for this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842730

Title:
  glibc: dlopen crash after a previously failed call to dlopen

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1842730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1844022] Re: pthread_setattr_default_np race condition with pthread_create.

[Florian Weimer]

No, the race condition is in your stack size test (which is written
incorrectly), not in the stack creation.

However, this code is inherently race-prone anyway:

pthread_attr_t attr;

pthread_setattr_default_np()
std::thread t(...);

You just need something else in the process using std::thread which does
not go through the wrapper you wrote to trigger this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844022

Title:
  pthread_setattr_default_np race condition with pthread_create.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1844022/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1844022] Re: pthread_setattr_default_np race condition with pthread_create.

[Florian Weimer]

I assume the code in another_thread attempts to obtain the size of the
current thread.  But the code just reads back the default stack size,
which may have changed due to the set_default_thread_stack_size call.

One way to obtain the size of the current thread stack is this call:

  if(int err = ::pthread_getattr_np(pthread_self(), ))
throw std::system_error(err, std::system_category(), 
"pthread_getattr_np");

This should give consistent results all the time.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844022

Title:
  pthread_setattr_default_np race condition with pthread_create.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1844022/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842730] Re: glibc: dlopen crash after a previously failed call to dlopen

[Florian Weimer]

Can you reproduce this with any NODELETE object (linked with -z nodelete
in place of librt)? Then this is probably this upstream bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=20839

** Bug watch added: Sourceware.org Bugzilla #20839
   https://sourceware.org/bugzilla/show_bug.cgi?id=20839

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842730

Title:
  glibc: dlopen crash after a previously failed call to dlopen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1842730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50363]

[Florian Weimer]

Only crashes on startup have been reported, so flagging as security-.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50363

Title:
  libc6-amd64 on edgy (2.4-1ubuntu4) fails on samba

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/50363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 305901]

[Florian Weimer]

(In reply to Szabolcs Nagy from comment #16)
> (In reply to Kees Cook from comment #14)
> > So I'd like to bring this back up and reiterate the issue: there is no
> > benefit to the early truncation, and it actively breaks lots of existing
> > software (which is why Debian and Ubuntu have had this fix for 10 years 
> > now).
> > 
> > What is the _benefit_ of early truncation that justifies breaking so many
> > existing cases?

I wonder if the early truncation was introduced to avoid cases where
aliasing can be used to avoid fortify length checks.  But then again,
truncation might not effectively prevent that after all.  And we do not
seem to use strlen followed by strcpy in vfprintf.

I haven't looked at this in detail, though.

> ideally sprintf, snprintf and sprintf_chk would be able to share code and
> have identical behaviour (currently there is a lot of duplicated logic in
> glibc with a potential for inconsistent behaviour).

Not sure what you mean by this.  The core vfprintf engine is shared, of
course.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/305901

Title:
  Intrepid gcc -O2 breaks string appending with sprintf(), due to
  fortify source patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/305901/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1803327] Re: iconv no longer transforms UTF8 to CP1252 as it used to under Ubuntu 16.04 LTS.

[Florian Weimer]

Your iutput shows the bytes 0xE0 0xEA 0xFC, which corresponds to the
characters you listed.  So the intended bytes are printed.

Maybe you changed terminal emulators, and this leads to the observed
difference in behavior?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803327

Title:
  iconv no longer transforms UTF8 to CP1252 as it used to under Ubuntu
  16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1803327/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1803327] Re: iconv no longer transforms UTF8 to CP1252 as it used to under Ubuntu 16.04 LTS.

[Florian Weimer]

This is exactly what I get: no transliteration happens because none is
needed.  I do not see a bug here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803327

Title:
  iconv no longer transforms UTF8 to CP1252 as it used to under Ubuntu
  16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1803327/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1803327] Re: iconv no longer transforms UTF8 to CP1252 as it used to under Ubuntu 16.04 LTS.

[Florian Weimer]

Please remove the first xxd from the pipe.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803327

Title:
  iconv no longer transforms UTF8 to CP1252 as it used to under Ubuntu
  16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1803327/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1803327] Re: iconv no longer transforms UTF8 to CP1252 as it used to under Ubuntu 16.04 LTS.

[Florian Weimer]

Would you please pipe the problematic output through xxd (or another
hexdumper), so that we can see the individual bytes?  Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803327

Title:
  iconv no longer transforms UTF8 to CP1252 as it used to under Ubuntu
  16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1803327/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797335] Re: strstr() on ubuntu18.04 8 times slower than on ubuntu16

[Florian Weimer]

Yes, but to be absolutely certain, the `strstr` binary you created is a
64-bit binary?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797335

Title:
  strstr() on ubuntu18.04 8 times slower than on ubuntu16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1797335/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797335] Re: strstr() on ubuntu18.04 8 times slower than on ubuntu16

[Florian Weimer]

Regarding:

$ gcc -o strstr strstr.c

Do you compile for i386 or amd64?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797335

Title:
  strstr() on ubuntu18.04 8 times slower than on ubuntu16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1797335/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1663280] Re: Serious performance degradation of math functions

[Florian Weimer]

Note that you may also have to take measures to increase available stack
size and avoid lazy binding for libgcc_s, for increased backwards
compatibility on AVX-512 systems.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663280

Title:
  Serious performance degradation of math functions

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1663280/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1663280] Re: Serious performance degradation of math functions

[Florian Weimer]

Sorry for being unclear.  What I was trying to say is this: The patches
you posted do not look like the XSAVE/XRSTOR patches for the dynamic
linker trampoline, but they appear to be based on an earlier attempt to
fix this.  I'm worried that these patches clobber registers which are
used by existing binaries to pass arguments (even though these registers
are reserved by the ABI).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663280

Title:
  Serious performance degradation of math functions

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1663280/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776967] Re: glibc pkeys test fail on powerpc

[Florian Weimer]

Upstream bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23202

There are three issues here: The kernel implementation in 4.17 was
buggy: pkey_set and pkey_get weren't implement in glibc, and the misc
/tst-pkeys has some incorrect test expectations.

** Bug watch added: Sourceware.org Bugzilla #23202
   https://sourceware.org/bugzilla/show_bug.cgi?id=23202

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776967

Title:
  glibc pkeys test fail on powerpc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1776967/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1663280] Re: Serious performance degradation of math functions

[Florian Weimer]

Daniel, are the patches in comment 17 compatible with the (non-standard)
Intel __regcall calling convention>

https://sourceware.org/bugzilla/show_bug.cgi?id=21265

** Bug watch added: Sourceware.org Bugzilla #21265
   https://sourceware.org/bugzilla/show_bug.cgi?id=21265

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663280

Title:
  Serious performance degradation of math functions

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1663280/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1613067] Re: NSS is unreliable in statically linked binaries

[Florian Weimer]

** Summary changed:

- SIGSEGV on internal_getent nss_files/files-XXX.c:251
+ NSS is unreliable in statically linked binaries

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613067

Title:
  NSS is unreliable in statically linked binaries

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1613067/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767097] Re: ftok() returns different result for same (path, id) pair if the inode of the file is changed

[Florian Weimer]

I believe the expectations actually is that the function result depends
on file system contents.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767097

Title:
  ftok() returns different result for same (path, id) pair if the inode
  of the file is changed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1767097/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767097] Re: ftok() returns different result for same (path, id) pair if the inode of the file is changed

[Florian Weimer]

You misunderstood what the manpage intends to say.  Over time, two
pathnames can refer to different files.  Essentially, the return value
depends on the file, not on the pathname.  If you delete a file and
recreate the file, it is no longer the same file.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767097

Title:
  ftok() returns different result for same (path, id) pair if the inode
  of the file is changed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1767097/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1757517] Re: An unused thread-local memory allocation can cause library calls to segfault.

[Florian Weimer]

Upstream bug: https://sourceware.org/bugzilla/show_bug.cgi?id=11787

** Bug watch added: Sourceware.org Bugzilla #11787
   https://sourceware.org/bugzilla/show_bug.cgi?id=11787

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757517

Title:
  An unused thread-local memory allocation can cause library calls to
  segfault.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1757517/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1746995] Re: regression in 2.23-0ubuntu10: rsync in glusterfs's georeplication fails

[Florian Weimer]

Do you have strace output for the getcwd system call before the failure?
That would be helpful.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746995

Title:
  regression in 2.23-0ubuntu10: rsync in glusterfs's georeplication
  fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1746995/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record

[Florian Weimer]

I believe systemd-resolved is still active on the system.  It's just not
queried over whatever interface nss_resolved uses, but over DNS, via the
stub resolver at 127.0.0.53.  If the systemd-resolved has bad data, it
will probably return bad data on the DNS interface as well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717015

Title:
  libc resolver stops searching domain search list after getting back
  NSEC record

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717015/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1737312] Re: Qemu crashes with signal 6 on arm64 chroot creation on amd64 (installing bash)

[Florian Weimer]

This is a QEMU bug.  It does not implement vfork with proper semantics
and runs both the parent and child in parallel.  It is expected that the
parent blocks until the fate of the child process is decided (successful
execve or exit).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737312

Title:
  Qemu crashes with signal 6 on arm64 chroot creation on amd64
  (installing bash)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1737312/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1732261] Re: glibc 2.26-0ubuntu2 ADT test failure with linux 4.14.0-7.9

[Florian Weimer]

This is a known issue related to HZ kernel settings.  I think Andreas
Schwab posted a patch for it; someone needs to review it and backport it
to the 2.26 branch.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732261

Title:
  glibc 2.26-0ubuntu2 ADT test failure with linux 4.14.0-7.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1732261/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726711] Re: valgrind reports invalid memory access on epoll_pwait call when invoked via epoll_wait

[Florian Weimer]

This is a valgrind bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1462258
https://bugs.kde.org/show_bug.cgi?id=381289

** Bug watch added: Red Hat Bugzilla #1462258
   https://bugzilla.redhat.com/show_bug.cgi?id=1462258

** Bug watch added: KDE Bug Tracking System #381289
   https://bugs.kde.org/show_bug.cgi?id=381289

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726711

Title:
  valgrind reports invalid memory access on epoll_pwait call when
  invoked via epoll_wait

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1726711/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

[Florian Weimer]

I filed a glibc bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=22273

However, I do not know if that bug is the root cause of the issue
reported here.

** Bug watch added: Sourceware.org Bugzilla #22273
   https://sourceware.org/bugzilla/show_bug.cgi?id=22273

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719004

Title:
  cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1719004/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720339] Re: artful libc6-dev_2.26-0ubuntu1 is missing bits/sigset.h

[Florian Weimer]

This is not a bug.  The header file was removed as part of this upstream
commit:

commit a992f506ff7162da2afa5a6151cc6f15949ceef4
Author: Zack Weinberg 
Date:   Thu Dec 1 19:24:13 2016 -0500

Remove __need macros from signal.h.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720339

Title:
  artful libc6-dev_2.26-0ubuntu1 is missing bits/sigset.h

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1720339/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1719959] Re: eglibc 2.19 leaks memory on getaddrinfo

[Florian Weimer]

Looks like this issue

  https://sourceware.org/bugzilla/show_bug.cgi?id=21336#c16

Quoting:

The announcement of CVE-2015-7547 said:

“
- Always malloc the second response buffer if needed.

  - Requires fix for sourceware bug 16574 to avoid memory leak.
commit d668061994a7486a3ba9c7d5e7882d85a2883707
commit ab09bf616ad527b249aca5f2a4956fd526f0712f
”



Coincidentally, this regression originally delayed the disclosure of
CVE-2015-7547.  The upstream glibc 2.19 branch already had the fix for
bug 16574 when CVE-2015-7547 was fixed, but our downstream 2.12 and 2.17
branches still needed it.

If you have you own resolv backports, you should really try to get a
valgrind-clean pass with the external resolv test suite:



** Bug watch added: Sourceware.org Bugzilla #21336
   https://sourceware.org/bugzilla/show_bug.cgi?id=21336

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-7547

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719959

Title:
  eglibc 2.19 leaks memory on getaddrinfo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1719959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record

[Florian Weimer]

“resolve” before “dns” in /etc/nsswitch.conf means you are using
systemd-resolved, not the glibc stub resolver, so this does not look
like a glibc bug anymore.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717015

Title:
  libc resolver stops searching domain search list after getting back
  NSEC record

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1717015/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record

[Florian Weimer]

Thanks.  I have difficulties reproducing this.

Have you set options in /etc/resolv.conf?  What's the contents of your
/etc/nsswitch.conf file, particularly the “hosts” line?

It's odd that the DO bit is set on the query.  Ordinarily, the glibc
stub resolver would not send such queries without application patches.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717015

Title:
  libc resolver stops searching domain search list after getting back
  NSEC record

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1717015/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record

[Florian Weimer]

Do you have packet captures which demonstrate the problem?  We will need
the data exchanged between the host which performs the DNS lookup and
the recursive resolvers configured in resolv.conf.

We are pretty sure that the stub resolver is tolerant to unknown DNS
record types, so the behavior you report is rather odd.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717015

Title:
  libc resolver stops searching domain search list after getting back
  NSEC record

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1717015/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs