This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/17977] gethostbyname_r hangs forever
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 17 Feb 2015 21:24:09 +0000
- Subject: [Bug libc/17977] gethostbyname_r hangs forever
- Auto-submitted: auto-generated
- References: <bug-17977-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17977
--- Comment #4 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Eric Newton from comment #3)
> Note:
> * it requires the "reorder on" configuration
> * it requires at least 3 threads attempting to run the
> _res_hconf_reorder_addrs function concurrently to lock up a single thread
> * these concurrent accesses must be on the first run of the function
> * future requests of _res_hconf_reorder_addrs will work just fine
> It would be hard, but not impossible to do this deliberately to a service.
Based on your third note, it seems to me that this can only happen once per
process, right? Wouldn't this make it difficult to trigger *deliberately* in a
typical long-running multi-threaded service?
(I'm trying to figure out if we have to treat this as a security issue or a
mere bug.)
--
You are receiving this mail because:
You are on the CC list for the bug.