Thomas Gleixner wrote:
It only happens with CONFIG_HIGHRES_TIMERS=y otherwise clock_was_set() is a NOP. So only the 2.6.21 kernel and i386 and ARM are affected.
Are you certain?Vanilla 2.6.10 shows a clock_was_set() function. Does it just not call the dangerous code or something?
Also, our modified 2.6.10 has the high res timers patch applied, but the config option is turned off and we were still affected.
Chris - 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/
- Follow-Ups:
- Re: 2.6.21.5 june 30th to july 1st date hang?
- From: Thomas Gleixner <[email protected]>
- Re: 2.6.21.5 june 30th to july 1st date hang?
- References:
- 2.6.21.5 june 30th to july 1st date hang?
- From: "Fortier,Vincent [Montreal]" <[email protected]>
- Re: 2.6.21.5 june 30th to july 1st date hang?
- From: "Chris Friesen" <[email protected]>
- Re: 2.6.21.5 june 30th to july 1st date hang?
- From: Chuck Ebbert <[email protected]>
- Re: 2.6.21.5 june 30th to july 1st date hang?
- From: Uli Luckas <[email protected]>
- Re: 2.6.21.5 june 30th to july 1st date hang?
- From: Chris Wright <[email protected]>
- Re: 2.6.21.5 june 30th to july 1st date hang?
- From: Clemens Koller <[email protected]>
- Re: 2.6.21.5 june 30th to july 1st date hang?
- From: "Chris Friesen" <[email protected]>
- Re: 2.6.21.5 june 30th to july 1st date hang?
- From: Thomas Gleixner <[email protected]>
- 2.6.21.5 june 30th to july 1st date hang?
- Prev by Date: Re: [PATCH][RESEND] PIE randomization
- Next by Date: Re: [1/2] 2.6.22-rc7: known regressions
- Previous by thread: Re: 2.6.21.5 june 30th to july 1st date hang?
- Next by thread: Re: 2.6.21.5 june 30th to july 1st date hang?
- Index(es):
 |