Red Hat Bugzilla – Bug 60906
X server will spin on the CPU and eventually crash if up for more than 49 days
Last modified: 2007-04-18 12:40:48 EDT
Description of Problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set your clock to this date:
2. Fire up the X server point it at a configured xdm server:
X -query foo
3. Set your date forward in time many days:
After a few minutes the X server will start hogging the CPU and will probably
crash or exit after a while with an error:
XDM: Too many retransmissions
The X server should keep running as normal.
It appears that after looking at the code that this bit of the code has a very
low tolerance for both clock skew, because someone changed the time, and when
the integer that holds the time rolls over its value. It's very likely that the
retransmission times for contacting the xdm server will be fully screwed up.
I've got a patch that both adds support for detecting clock skew, and correcting
from that condition, and handles the rollover of the value correctly.
Created attachment 47940 [details]
FIxed in rawhide, and also pending XFree86 erratum, will be released soon.
What version of the XFree86 4.1.x rpms is this present in?
Created attachment 48104 [details]
patch from keith packard after sending mine for review
Patch updated in 4.1.0-23