Red Hat Bugzilla – Bug 689559
libnl's error handling uses strerror, which is not threadsafe
Last modified: 2013-11-21 19:15:51 EST
libnl's error handling makes generous use of strerror(), but strerror is not threadsafe, and it's totally acceptable for multiple threads in an application to call libnl. All the occurences of strerror should be replaced with a call to strerror_r that puts the message into a thread-local static buffer.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Fixed upstream: commit 4d7680c19c131175e2ec431de9a026230c968a7e Author: Thomas Graf <tgraf@suug.ch> Date: Thu Feb 28 13:07:04 2013 +0100 Use thread-safe strerror_r() instead of strerror() We have only ever fed well known error codes into strerror() so it should never have been a problem though. Signed-off-by: Thomas Graf <tgraf@suug.ch>
Backported to stable branch as: commit f571938ccabad025eebcd3d9374a869d5769852f Author: Thomas Graf <tgraf@suug.ch> Date: Thu Feb 28 13:07:04 2013 +0100 Use thread-safe strerror_r() instead of strerror() We have only ever fed well known error codes into strerror() so it should never have been a problem though. Signed-off-by: Thomas Graf <tgraf@suug.ch> (cherry picked from commit 4d7680c19c131175e2ec431de9a026230c968a7e) Conflicts: lib/fib_lookup/lookup.c lib/msg.c lib/route/route_obj.c src/lib/utils.c
Fixed in libnl-1.1.2 upstream
Fixed in libnl-1.1.3-1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1730.html