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 network/17630] endless loop in getaddr_r Date: Thu, 18 Dec 2014 01:07:00 -0000 [thread overview] Message-ID: <bug-17630-131-NYHGRw28Hx@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17630-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17630 --- Comment #13 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU C Library master sources". The branch, release/2.20/master has been updated via f80af76648ed97a76745fad6caa3315a79cb1c7c (commit) from a3a1f4163c4d0f9a36056c8640661a88674ae8a2 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=f80af76648ed97a76745fad6caa3315a79cb1c7c commit f80af76648ed97a76745fad6caa3315a79cb1c7c Author: Florian Weimer <fweimer@redhat.com> Date: Mon Dec 15 17:41:13 2014 +0100 Avoid infinite loop in nss_dns getnetbyname [BZ #17630] (cherry picked from commit 11e3417af6e354f1942c68a271ae51e892b2814d) (cherry picked from commit e54db0ea6a49affac43fa305fd134f3020c41382) Conflicts: NEWS ----------------------------------------------------------------------- Summary of changes: ChangeLog | 6 ++++++ NEWS | 8 ++++++-- resolv/nss_dns/dns-network.c | 4 ++-- 3 files changed, 14 insertions(+), 4 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-12-18 1:07 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-20 13:44 [Bug network/17630] New: " yashavanth.hsn at gmail dot com 2014-11-20 14:47 ` [Bug network/17630] " schwab@linux-m68k.org 2014-11-24 16:29 ` yashavanth.hsn at gmail dot com 2014-11-24 16:31 ` yashavanth.hsn at gmail dot com 2014-11-24 16:58 ` schwab@linux-m68k.org 2014-11-25 9:48 ` yashavanth.hsn at gmail dot com 2014-12-09 13:34 ` schwab@linux-m68k.org 2014-12-12 14:06 ` fweimer at redhat dot com 2014-12-15 9:26 ` yashavanth.hsn at gmail dot com 2014-12-15 9:34 ` schwab@linux-m68k.org 2014-12-15 9:50 ` fweimer at redhat dot com 2014-12-15 9:50 ` yashavanth.hsn at gmail dot com 2014-12-16 9:10 ` cvs-commit at gcc dot gnu.org 2014-12-16 9:11 ` fweimer at redhat dot com 2014-12-18 1:07 ` cvs-commit at gcc dot gnu.org [this message] 2014-12-18 6:17 ` [Bug network/17630] endless loop in getaddr_r (CVE-2014-9402) fweimer at redhat dot com 2015-01-14 12:19 ` cvs-commit at gcc dot gnu.org 2015-01-14 13:13 ` cvs-commit at gcc dot gnu.org 2015-01-16 16:59 ` cvs-commit at gcc dot gnu.org 2015-01-16 17:02 ` cvs-commit at gcc dot gnu.org 2015-01-16 17:03 ` cvs-commit at gcc dot gnu.org 2015-01-21 13:56 ` cvs-commit at gcc dot gnu.org 2015-01-29 18:50 ` cvs-commit at gcc dot gnu.org 2015-02-12 13:05 ` cvs-commit at gcc dot gnu.org 2015-02-23 14:06 ` cvs-commit at gcc dot gnu.org 2015-02-23 14:23 ` cvs-commit at gcc dot gnu.org 2015-02-23 15:02 ` cvs-commit at gcc dot gnu.org
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-17630-131-NYHGRw28Hx@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).