public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, ltp@lists.linux.it,
	viro@zeniv.linux.org.uk, kstewart@linuxfoundation.org,
	gregkh@linuxfoundation.org, rfontana@redhat.com
Subject: Re: [PATCH] kernel: use ktime_get_real_ts64() to calculate acct.ac_btime
Date: Mon, 11 Nov 2019 04:41:33 -0500 (EST)	[thread overview]
Message-ID: <475677126.11444968.1573465293662.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191107125559.GI4131@hirez.programming.kicks-ass.net>


----- Original Message -----
> It's wrecked in general. It also jumps around for any REALTIME
> adjustment.
> 
> > So a CLOCK_REALTIME time stamp at fork would at least be correct
> > vs. suspend resume.
> 
> But still wrecked vs REALTIME jumps, as in, when DST flips the clock
> back an hour, your timestamp is in the future.
> 
> Any which way around the whole thing is buggered.  The only real fix is
> not using REALTIME anything. Which is why I'm loath to add that REALTIME
> timestamp at fork(), it just encourages more use.

Thank you for feedback and listing all other problems.
I'll adjust test expectations.

Regards,
Jan


      parent reply	other threads:[~2019-11-11  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01 23:39 [PATCH] kernel: use ktime_get_real_ts64() to calculate acct.ac_btime Jan Stancek
2019-11-07  8:56 ` Thomas Gleixner
2019-11-07 12:49   ` Peter Zijlstra
2019-11-07 12:32 ` Peter Zijlstra
2019-11-07 12:40   ` Thomas Gleixner
2019-11-07 12:46     ` Peter Zijlstra
2019-11-07 12:55     ` Peter Zijlstra
2019-11-07 14:37       ` Thomas Gleixner
2019-11-11  9:41       ` Jan Stancek [this message]

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=475677126.11444968.1573465293662.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=peterz@infradead.org \
    --cc=rfontana@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    /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