Re: How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?

On Sat 30-09-06 17:03:45, Andi Kleen wrote:
> 
> > 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.

Attacker might; in a tight loop, to confuse time-of-day subsystem, or
maybe oops the kernel.
							Pavel

-- 
Thanks for all the (sleeping) penguins.
-
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: Andi Kleen <[email protected]>

Prev by Date: Re: [NFS] [PATCH 008 of 11] knfsd: Prepare knfsd for support of rsize/wsize of up to 1MB, over TCP.
Next by Date: Fwd: Any way to find the network usage by a process?
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):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]