From: Andi Kleen <ak@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Dong Feng <middle.fengdong@gmail.com>,
Christoph Lameter <clameter@sgi.com>,
Arjan van de Ven <arjan@infradead.org>,
Paul Mackerras <paulus@samba.org>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?
Date: Tue, 3 Oct 2006 12:03:57 +0200 [thread overview]
Message-ID: <200610031203.57328.ak@suse.de> (raw)
In-Reply-To: <20061003080352.GA4078@ucw.cz>
On Tuesday 03 October 2006 10:03, Pavel Machek wrote:
> 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.
(a) only root change it.
(b) the time of day subsystem never cares about the time zone. It is
just a variable stored for user space.
-Andi
next prev parent reply other threads:[~2006-10-03 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 14:33 How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path? Dong Feng
2006-09-29 16:05 ` Christoph Lameter
2006-09-29 16:16 ` Dong Feng
2006-09-30 14:37 ` Nick Piggin
2006-09-30 15:03 ` Andi Kleen
2006-09-30 17:13 ` Christoph Lameter
2006-10-02 10:08 ` Samuel Tardieu
2006-10-03 8:03 ` Pavel Machek
2006-10-03 10:03 ` Andi Kleen [this message]
2006-09-30 16:09 ` Dong Feng
2006-09-30 17:26 ` Christoph Lameter
2006-10-01 3:48 ` Nick Piggin
2006-10-01 12:22 ` Dong Feng
2006-10-02 10:12 ` Samuel Tardieu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610031203.57328.ak@suse.de \
--to=ak@suse.de \
--cc=arjan@infradead.org \
--cc=clameter@sgi.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=middle.fengdong@gmail.com \
--cc=nickpiggin@yahoo.com.au \
--cc=paulus@samba.org \
--cc=pavel@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox