Bug 770275

Summary: Endless loop in recurrence calculation
Product: Red Hat Enterprise Linux 6 Reporter: Robert Scheck <redhat-bugzilla>
Component: libicalAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2CC: tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://sourceforge.net/tracker/?func=detail&atid=316077&aid=3177380&group_id=16077
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 12:53:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Robert Scheck 2011-12-25 13:55:30 UTC 
Description of problem:
While receiving a meeting request from Novell Groupwise (PRODID:-//Novell 
Inc//Groupwise 7.0.3 ), the timezone definition looked like this:

---
BEGIN:VTIMEZONE
TZID:(GMT+0100) West-Europa (standaardtijd)
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:20001030T000000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=255SU;BYMONTH=10
TZNAME:West-Europa (standaardtijd)
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:20000327T000000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=255SU;BYMONTH=3
TZNAME:West-Europa (zomertijd)
END:DAYLIGHT
END:VTIMEZONE
---

Please note the BYDAY=255SU. Obviously being processed as unsigned, the -1 
turned into 255. This causes an endless loop in ical, which was fixed by 
limiting the value that can be set in BYDAY to a char instead of an int.

Version-Release number of selected component (if applicable):
libical-0.43-5.1.el6

How reproducible:
Everytime together with Zarafa from Fedora EPEL, see above.

Actual results:
Endless loop in recurrence calculation.

Expected results:
No endless loop in recurrence calculation.

Additional info:
http://sourceforge.net/tracker/?func=detail&atid=316077&aid=3177380&group_id=16077
Comment 3 Suzanne Logcher 2012-02-14 23:25:32 UTC 
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.
Comment 4 Jan Kurik 2017-12-06 12:53:41 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/