This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/17977] gethostbyname_r hangs forever


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

--- Comment #3 from Eric Newton <eric.newton at gmail dot com> ---
The error did cause service availability failures.

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

In this case, a component of a large distributed database was asked by hundred
of other services to perform work at the moment it came online. These requests
locked other resources before performing a name lookup.

It would be hard, but not impossible to do this deliberately to a service.

It was not deliberately caused when it was found.  Just (un)lucky.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]