Bug 1046410
Summary: | X APPLICATION CRASHES AFTER SOME TIME ON RHEL6 X86 WITH LIBXCB 1.8.1 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Luan Jianhai <jianhai.luan> | ||||
Component: | libxcb | Assignee: | Olivier Fourdan <ofourdan> | ||||
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.5 | CC: | ashishks, dave.kinsell, jherrman, joe.jin, ofourdan, thatsafunnyname, tlavigne, tpelka | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | libxcb-1.9.1-3.el6 | Doc Type: | Bug Fix | ||||
Doc Text: |
On 32-bit architectures, an X11 protocol client was under certain circumstances disconnected after processing a large number of X11 requests. With this update, the libxcb library exposes the request sequence number as a 64-bit integer so that libX11 can make use of 64-bit sequence number even on 32-bit systems. As a result, the described failure of the X11 client no longer occurs.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-07-22 07:02:22 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Luan Jianhai
2013-12-25 06:56:25 UTC
Created attachment 841403 [details]
Patch of fixing libX11 uint_64
As xorg-devel discussion, the attachment should have fix the issue. Would you like merge the patch into latest RHEL? Would you like to give me some respond about the issue. If the patch don't fix the isssue, do you have good advice about the issue. Defect still present in RHEL6u6 and RHEL7u0 (libxcb 1.9-5). Also occurs on apps compiled as 32 bits on 64 bit systems. Can see the failure in less than 5 minutes of run time, under 'best case' conditions. (In reply to dave.kinsell from comment #11) > Defect still present in RHEL6u6 and RHEL7u0 (libxcb 1.9-5). Also occurs on > apps compiled as 32 bits on 64 bit systems. Can see the failure in less > than 5 minutes of run time, under 'best case' conditions. A patch to address this issue is currently under review upstream. Note that X IO errors can have multiple causes, including bugs in the program itself. Reaching the failure in less than 5 minutes sounds surprising, it means you reach the 32bit sequence number limit in less than 5 minutes. To give you an idea, it takes me roughly 5 hours to reach that limit in a VM using the reproducer program, which draws a line continuously. Thank you Olivier, so nice to hear this may get a patch from upstream. The 5 minutes to failure is done with rapid XNoOp() calls, as discussed in https://bugs.freedesktop.org/show_bug.cgi?id=71338 I used my own counter to make sure it was making 2^32 calls before failing. With a realistic program that we support, it can fail in about 28 hours. I wanted to clarify this happens with any 32 bit executable, not just on 32 bit systems, because the number of people affected is much larger. (In reply to dave.kinsell from comment #14) > The 5 minutes to failure is done with rapid XNoOp() calls, as discussed in > https://bugs.freedesktop.org/show_bug.cgi?id=71338 > > I used my own counter to make sure it was making 2^32 calls before failing. > With a realistic program that we support, it can fail in about 28 hours. OK, thanks for clarifying. > I wanted to clarify this happens with any 32 bit executable, not just on 32 > bit systems, because the number of people affected is much larger. Yes, correct, 32apps link to 32bit libs and therefore are equally affected, even on a 64bit system - This is why I also cloned these bugs for el7 as well. 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. https://rhn.redhat.com/errata/RHBA-2015-1358.html |