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/15946] getaddrinfo() writes DNS queries to random file descriptors under high load
Date: Tue, 03 Jun 2014 16:05:00 -0000	[thread overview]
Message-ID: <bug-15946-131-icwFFymWqw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15946-131@http.sourceware.org/bugzilla/>

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

--- Comment #6 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, master has been updated
       via  f9d2d03254a58d92635a311a42253eeed5a40a47 (commit)
      from  71840409ea45ab9e49d0ac70dfc1c355accf355f (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=f9d2d03254a58d92635a311a42253eeed5a40a47

commit f9d2d03254a58d92635a311a42253eeed5a40a47
Author: Andreas Schwab <schwab@suse.de>
Date:   Mon May 26 18:01:31 2014 +0200

    Fix invalid file descriptor reuse while sending DNS query (BZ #15946)

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog         |    6 ++++++
 NEWS              |   20 ++++++++++----------
 resolv/res_send.c |    1 +
 3 files changed, 17 insertions(+), 10 deletions(-)

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


  parent reply	other threads:[~2014-06-03 16:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12  9:50 [Bug network/15946] New: " arnaud.lb at gmail dot com
2013-09-15 15:58 ` [Bug network/15946] " ian at airs dot com
2013-09-15 16:05 ` ian at airs dot com
2013-09-16  7:56 ` fweimer at redhat dot com
2014-03-06 20:27 ` bugdal at aerifal dot cx
2014-03-06 21:01 ` schwab@linux-m68k.org
2014-03-06 21:07 ` bugdal at aerifal dot cx
2014-03-06 21:16 ` schwab@linux-m68k.org
2014-03-13  0:08 ` edsrzf at gmail dot com
2014-06-03 16:05 ` schwab@linux-m68k.org
2014-06-03 16:05 ` cvs-commit at gcc dot gnu.org [this message]
2014-06-13 12:49 ` fweimer at redhat dot com
2014-08-28 10:26 ` cvs-commit at gcc dot gnu.org
2015-01-08 14:21 ` nilsson.dd+bz at gmail dot com
2015-01-28 12:33 ` jannhorn at googlemail dot com
2015-01-28 19:51 ` k_f at gentoo dot org
2015-01-29  2:43 ` jirka at fud dot cz
2015-01-30  3:18 ` bugdal at aerifal dot cx
2015-01-30 13:22 ` jirka at fud dot cz
2015-02-24 10:51 ` [Bug network/15946] getaddrinfo() writes DNS queries to random file descriptors under high load (CVE-2013-7423) fweimer at redhat dot com
2015-03-03 11:26 ` schwab@linux-m68k.org
2015-04-07 18:02 ` cvs-commit at gcc dot gnu.org
2015-04-07 18:06 ` cvs-commit at gcc dot gnu.org
2015-05-27 11:32 ` jim.king at simplivity dot com
2015-10-22 13:50 ` fweimer at redhat 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-15946-131-icwFFymWqw@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).