> Did you get to the bottom of this yet? It looks like you're right, > and I suggest a seqlock might be a good option. It basically doesn't matter because nobody changes the time zone after boot. -Andi - 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: How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?
- From: Christoph Lameter <[email protected]>
- Re: How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?
- References:
- How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?
- From: "Dong Feng" <[email protected]>
- Re: How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?
- From: "Dong Feng" <[email protected]>
- Re: How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?
- From: Nick Piggin <[email protected]>
- How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?
- Prev by Date: Re: [PATCH 4 of 4] x86-64: Calgary IOMMU: Fix off by one when calculating register space
- Next by Date: Re: Postal 56% waits for flock_lock_file_wait
- Previous by thread: Re: How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?
- Next by thread: Re: How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?
- Index(es):
 |