Bug#817210: systemd-resolve: segfaults upon domain name resolution

[Rostislav Pehlivanov]

Package: libnss-resolve
Version: 229-2
Severity: important

Dear maintainer:

If systemd-resolve is used as the default system dns resolver
(by replacing "dns" inside /etc/nsswitch.conf with "resolve"),
the process handling the resolving "/lib/systemd/systemd-resolved"
started by the service systemd-resolved will segfault upon domain name
resolution (e.g. ping <domain name> will crash the process). The service
gets restarted immediately after it segfaults and is able to resolve the
first domain name (but with a short delay), so it's mostly transparent
to the end user. However the dmesg log quickly gets filled with entries like:

"[ 7620.719971] systemd-resolve[3655]: segfault at 5c ip 00005625f5934147 sp 00007ffc5acd7380 error 4 in systemd-resolved[5625f590c000+9d000"

I believe it started after libc6 was updated in Debian unstable, though
I am not sure it was the cause.

I did try to run gdb to at least find out where it crashes, but the process
doesn't function as it should without it being started as a service.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc6-youmu (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libnss-resolve depends on:
ii  libc6        2.22-1
ii  libselinux1  2.4-3+b1
ii  systemd      229-2

libnss-resolve recommends no packages.

libnss-resolve suggests no packages.

-- no debconf information