public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/12926] getaddrinfo()/make_request() may spin forever
Date: Wed, 21 Oct 2015 15:28:00 -0000	[thread overview]
Message-ID: <bug-12926-131-V7GdiUcB3g@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12926-131@http.sourceware.org/bugzilla/>

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

--- Comment #14 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Florian Weimer from comment #13)
> (In reply to Carlos O'Donell from comment #11)
> 
> > How can we assume all supported kernels from 2.6.32 and up are not
> > vulnerable? AFAIK glibc has to be defensive in this case.
> 
> We could probably make an exception here.  In general, I really dislike the
> idea of working around kernel security bugs, but this might be an exception.
> (Although there are likely corner cases the libc check won't cover.)

We can conditionlize the code on upstream kernel version with the fix, similar
to the way we conditionalize with interface availability and eventually remove
the code when the minimum kernel version is new enough.

I don't like it either, but it is a fact of developing on a library with a wide
range of supported kernel versions.

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


  parent reply	other threads:[~2015-10-21 15:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23 16:51 [Bug libc/12926] New: " ppluzhnikov at google dot com
2011-07-16  5:36 ` [Bug libc/12926] " nick.jones@network-box.com
2011-07-16  5:43 ` ppluzhnikov at google dot com
2011-07-17  3:32 ` bugdal at aerifal dot cx
2014-06-27 13:04 ` fweimer at redhat dot com
2014-10-14 16:05 ` cvs-commit at gcc dot gnu.org
2014-10-14 16:06 ` siddhesh at redhat dot com
2015-05-27  9:54 ` fengtiantian at huawei dot com
2015-05-27 11:29 ` jim.king at simplivity dot com
2015-08-22 20:32 ` [Bug network/12926] " jsm28 at gcc dot gnu.org
2015-10-16 20:36 ` fweimer at redhat dot com
2015-10-21 14:17 ` jim.king at simplivity dot com
2015-10-21 14:21 ` fweimer at redhat dot com
2015-10-21 15:28 ` carlos at redhat dot com [this message]
2015-10-21 16:01 ` joseph at codesourcery dot com
2015-10-23 20:08 ` 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-12926-131-V7GdiUcB3g@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).