Bug 1139977

Description of problem:

If the system time is moved forward, timers created with g_timeout_add() expire too soon.  In the wild this occurs frequently when NTP is enabled in a clustering environment as pacemaker (HA Add-on) uses g_timeout_add() extensively.

Apparently this is already fixed in RHEL7 thanks to https://github.com/GNOME/glib/commit/91113a8aeea40cc2d7dda65b09537980bb602a06#diff-fc9b4bb280a13f8e51c51b434e7d26fd

Version-Release number of selected component (if applicable):

Name        : glib2                        Relocations: (not relocatable)
Version     : 2.28.8                            Vendor: Red Hat, Inc.
Release     : 1.el6                         Build Date: Wed 11 Jun 2014 21:48:27 EST


How reproducible:

Every time

Steps to Reproduce:
1. Run sample program
2. Immediately run: date -s +60sec

Actual results:

Sample program prints "TIMER2 EXPIRE!" less than 60s after it was started

Expected results:

Sample program prints "TIMER2 EXPIRE!" 60s after it was started

Additional info:

#### Sample program

#include <stdio.h>
#include <glib.h>
#include <sys/times.h>
gboolean timer_func(gpointer data){
        printf("TIMER EXPIRE!\n");
        fflush(stdout);
        exit(1);
//      return FALSE;
}
gboolean timer_func2(gpointer data){
        clock_t         ret;
        struct tms buff;

        ret = times(&buff);

        printf("TIMER2 EXPIRE! %d\n", ret);
        fflush(stdout);
        return TRUE;
}
int main(int argc, char** argv){
        GMainLoop *m;
        clock_t         ret;
        struct tms buff;        gint64 t;

//      t = g_get_monotonic_time();
        m = g_main_new(FALSE);
        g_timeout_add(5000, timer_func2, NULL);
        g_timeout_add(60000, timer_func, NULL);
        ret = times(&buff);
        printf("START! %d\n", ret);]
        g_main_run(m);
}