Bug 613860
| Summary: | A problem of libxml2 which is not thread safe. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | HIDEO YAMAUCHI <renayama19661014> | ||||||
| Component: | libxml2 | Assignee: | Daniel Veillard <veillard> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 5.5 | CC: | cww, mfuruta, mnowak, mpoole, plyons, syeghiay | ||||||
| Target Milestone: | rc | Keywords: | ZStream | ||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | libxml2-2.6.26-2.1.12 | Doc Type: | Bug Fix | ||||||
| Doc Text: |
Due to an uninitialized field in one of the private libxml2 XPath data structures, the XPath evaluation may have return incorrect results. This error has been fixed, the field is now initialized properly, and XPath evaluation returns expected results.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-07-21 11:13:59 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 590060, 640191 | ||||||||
| Attachments: |
|
||||||||
|
Description
HIDEO YAMAUCHI
2010-07-13 01:14:21 UTC
First note: the program provided does not follow the recommendations from http://xmlsoft.org/threads.html as it does not call xmlInitParser() in the "main" thread before using any of the libxml2 API Daniel Tested on RHEL-5.5, program compiled as expected shows results where [3] elements are retourned. Simply adding xmlInitParser() as stated in libxml2 documentation seems to fix the problem for me, in a nutshell sounds like a bogus app, trivially fixed, please try to fix the real program and report. Daniel Okay I have been looking at it more deeply, th problem still persists if I add xmlInitParser() in main(), it just didn't show up on my few test runs ... Now I can reproduce this and I'm trying to find this out, but it's not simple ! Daniel Created attachment 451508 [details]
Patch fixing the random XPath problem
The problem wasn't a threading bug it was related to a lack of initialization
in an internal data structure, patch attached
Daniel
Hi Daniel,
> Created attachment 451508 [details]
> Patch fixing the random XPath problem
> The problem wasn't a threading bug it was related to a lack of initialization
> in an internal data structure, patch attached
I confirmed that the problem was solved with your patch.
This revision seems to be performed in libxml2-2.7.2.
Best Regards,
Hideo Yamauchi.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Due to an uninitialized field in one of the private libxml2 XPath data structures, the XPath evaluation may have return incorrect results. This error has been fixed, the field is now initialized properly, and XPath evaluation returns expected results.
Fixed in build libxml2-2.6.26-2.1.12 targetted at RHEL-5.7, Daniel An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1053.html |