On 2013年03月30日 21:15, Frederic Weisbecker wrote: > In order to arm the next timer to schedule, we take a sample of the > current process or thread cputime. > > If the task is dying though, we don't arm anything but we > cache the remaining timer expiration delta for further reads. > > Something similar is performed in posix_cpu_timer_get() but > here we forget to take the process wide cputime sample > before caching it. > > As a result we are storing random stack content, leading > every further reads of that timer to return junk values. > > Fix this by taking the appropriate sample in the case of > process wide timers. > > Reported-by: Andrew Morton <[email protected]> > Reported-by: Chen Gang <[email protected]> > Signed-off-by: Frederic Weisbecker <[email protected]> > Cc: Stanislaw Gruszka <[email protected]> > Cc: Thomas Gleixner <[email protected]> > Cc: Peter Zijlstra <[email protected]> > Cc: Ingo Molnar <[email protected]> > Cc: Oleg Nesterov <[email protected]> > Cc: Chen Gang <[email protected]> > ---
thank you for mark me as reported by, although I reported too late (Andrew Morton is the first reporter). next, I should continue to try to find another issues about kernel. :-) -- Chen Gang Asianux Corporation -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
