public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "holger@applied-asynchrony.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/29605] Regression in NSCD backend of getaddrinfo
Date: Mon, 26 Sep 2022 19:18:27 +0000	[thread overview]
Message-ID: <bug-29605-131-xAwhPUhhfN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29605-131@http.sourceware.org/bugzilla/>

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

--- Comment #8 from Holger Hoffstätte <holger@applied-asynchrony.com> ---
So my crashes/garbage data in packets indeed turned out to be caused by
post-2.36 release patches from the backport branch, presumably the resolver
rewrite. Building a completely vanilla 2.36 made everything work again, and
nscd runs just fine with enabled host cache.
Cheers :)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-09-26 19:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 11:19 [Bug nscd/29605] New: " joerg at bec dot de
2022-09-23 12:19 ` [Bug nscd/29605] " fweimer at redhat dot com
2022-09-23 17:55 ` siddhesh at sourceware dot org
2022-09-23 20:22 ` joerg at bec dot de
2022-09-25 11:05 ` holger@applied-asynchrony.com
2022-09-26 13:35 ` siddhesh at sourceware dot org
2022-09-26 17:57 ` siddhesh at sourceware dot org
2022-09-26 18:03 ` sam at gentoo dot org
2022-09-26 18:13 ` holger@applied-asynchrony.com
2022-09-26 18:15 ` sam at gentoo dot org
2022-09-26 19:18 ` holger@applied-asynchrony.com [this message]
2022-09-26 19:21 ` siddhesh at sourceware dot org
2022-09-28 16:47 ` cvs-commit at gcc dot gnu.org
2022-09-28 16:48 ` siddhesh at sourceware dot org
2022-09-28 16:49 ` cvs-commit at gcc dot gnu.org
2024-01-08 11:11 ` camila.camargodematos at canonical dot com

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=bug-29605-131-xAwhPUhhfN@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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: link
Be 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).