public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper.fsp at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11884] Unbounded alloca() in node parameter of getaddrinfo()
Date: Sat, 21 May 2011 03:48:00 -0000 [thread overview]
Message-ID: <bug-11884-131-XAaQx1120n@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11884-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11884
Ulrich Drepper <drepper.fsp at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |FIXED
--- Comment #9 from Ulrich Drepper <drepper.fsp at gmail dot com> 2011-05-21 03:48:05 UTC ---
Not that anything here was any help, I still looked through the code. There
shouldn't be unprotected alloca uses anymore. The changes don't really have
anything to do with with bug but I'm still attaching it to them to prevent
annoying questions.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-05-21 3:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11884-131@http.sourceware.org/bugzilla/>
2011-04-27 11:16 ` thoger at redhat dot com
2011-05-21 3:48 ` drepper.fsp at gmail dot com [this message]
2014-06-30 17:24 ` fweimer at redhat dot com
2010-08-05 5:12 [Bug libc/11884] New: Unbound " cdn at chromium dot org
2010-08-05 5:12 ` [Bug libc/11884] Unbounded " cdn at chromium dot org
2010-08-05 5:14 ` cdn at chromium dot org
2010-08-18 17:12 ` cdn at chromium dot org
2010-09-12 15:27 ` kees at outflux dot net
2010-09-12 15:41 ` kees at outflux dot net
2010-09-12 15:51 ` kees at outflux dot net
2010-09-12 20:41 ` cdn at chromium dot org
2010-09-12 22:56 ` kees at outflux dot net
2010-09-14 0:15 ` cdn at chromium dot org
2010-09-14 0:36 ` pasky at suse dot cz
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-11884-131-XAaQx1120n@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).