[lkml]   [2006]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subject[patch 0/2] sys_setitimer and sys_alarm hotfixes (take #2)

    The hrtimer merge breaks sys_alarm() with a timeout value > INT_MAX
    due to a unsigned to signed conversion. Timeout values > INT_MAX are
    legitimate usage of alarm(), so this has to be corrected.

    Due to a missing validation check of the userspace itimer values non
    canonical timespecs can be provided to the setitimer code. While the
    pre 2.6.16 code converted negative timevals to a long timeout
    (depending on HZ) the hrtimer code treats them as expired. Also on
    32 bit machines non normalized timevals might cause random behaviour
    of the optimized ktime_t operations. Due to the historical behaviour
    we can not suddenly return -EINVAL in such cases, but we have to
    fixup the values to avoid random behaviour.



    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-03-19 21:05    [W:0.017 / U:13.916 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site