public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nscd/29607] nscd repeatably crashes calling __strlen_avx2 when hosts cache is enabled Date: Fri, 07 Oct 2022 14:34:41 +0000 [thread overview] Message-ID: <bug-29607-131-yGODUd4ysW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29607-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29607 --- Comment #20 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The release/2.34/master branch has been updated by Arjun Shankar <arjun@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=e3976287b22422787f3cc6fc9adda58304b55bd9 commit e3976287b22422787f3cc6fc9adda58304b55bd9 Author: Siddhesh Poyarekar <siddhesh@sourceware.org> Date: Tue Oct 4 18:40:25 2022 -0400 nscd: Drop local address tuple variable [BZ #29607] When a request needs to be resent (e.g. due to insufficient buffer space), the references to subsequent tuples in the local variable are stale and should not be used. This used to work by accident before, but since 1d495912a it no longer does. Instead of trying to reset it, just let gethostbyname4_r write into TUMPBUF6 for us, thus maintaining a consistent state at all times. This is now consistent with what is done in gaih_inet for getaddrinfo. Resolves: BZ #29607 Reported-by: Holger Hoffstätte <holger@applied-asynchrony.com> Tested-by: Holger Hoffstätte <holger@applied-asynchrony.com> Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit 6e33e5c4b73cea7b8aa3de0947123db16200fb65) -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-10-07 14:34 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-23 15:39 [Bug nscd/29607] New: " holger@applied-asynchrony.com 2022-09-23 17:19 ` [Bug nscd/29607] " holger@applied-asynchrony.com 2022-09-24 1:17 ` sam at gentoo dot org 2022-09-24 1:18 ` sam at gentoo dot org 2022-09-25 10:50 ` holger@applied-asynchrony.com 2022-09-25 11:09 ` schwab@linux-m68k.org 2022-09-25 11:13 ` holger@applied-asynchrony.com 2022-09-25 11:46 ` holger@applied-asynchrony.com 2022-09-25 12:16 ` holger@applied-asynchrony.com 2022-09-26 18:03 ` sam at gentoo dot org 2022-09-26 19:13 ` holger@applied-asynchrony.com 2022-09-26 19:20 ` holger@applied-asynchrony.com 2022-09-26 19:34 ` holger@applied-asynchrony.com 2022-09-26 19:34 ` sam at gentoo dot org 2022-09-26 19:49 ` holger@applied-asynchrony.com 2022-09-26 20:11 ` holger@applied-asynchrony.com 2022-09-26 20:22 ` siddhesh at sourceware dot org 2022-09-27 5:33 ` holger@applied-asynchrony.com 2022-09-29 23:25 ` sam at gentoo dot org 2022-09-30 18:03 ` siddhesh at sourceware dot org 2022-10-04 22:40 ` cvs-commit at gcc dot gnu.org 2022-10-04 22:44 ` cvs-commit at gcc dot gnu.org 2022-10-04 22:45 ` siddhesh at sourceware dot org 2022-10-07 14:34 ` cvs-commit at gcc dot gnu.org 2022-10-07 14:34 ` cvs-commit at gcc dot gnu.org [this message]
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-29607-131-yGODUd4ysW@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: 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).