All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linaro.org>
To: tglx@linutronix.de
Cc: arnd@arndb.de, john.stultz@linaro.org, heenasirwani@gmail.com,
	pang.xunlei@linaro.org, mingo@kernel.org, peterz@infradead.org,
	benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
	schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
	linux390@de.ibm.com, rth@twiddle.net, riel@redhat.com,
	cl@linux.com, tj@kernel.org, fweisbec@gmail.com,
	hofrat@osadl.org, ahh@google.com, linuxppc-dev@lists.ozlabs.org,
	linux-s390@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org, serge.hallyn@canonical.com,
	james.l.morris@oracle.com, serge@hallyn.com, paul@paul-moore.com,
	john.johansen@canonical.com, sds@tycho.nsa.gov,
	casey@schaufler-ca.com, penguin-kernel@I-love.SAKURA.ne.jp,
	neilb@suse.de, edumazet@google.com, jlayton@primarydata.com,
	keescook@chromium.org, linux-security-module@vger.kernel.org,
	baolin.wang@linaro.org, y2038@lists.linaro.org
Subject: [PATCH 0/6] Introduce 64bit accessors and structures required to address y2038 issues in the posix_clock subsystem
Date: Wed, 15 Jul 2015 13:47:49 +0800	[thread overview]
Message-ID: <cover.1436511577.git.baolin.wang@linaro.org> (raw)

This patch series change the 32-bit time types (timespec/itimerspec) to
the 64-bit types (timespec64/itimerspec64), and add new 64bit accessor
functions, which are required in order to avoid y2038 issues in the
posix_clock subsystem.

In order to avoid spamming people too much, I'm only sending the first
few patches of the patch series, and left the other patches for later.

And if you are interested in the whole patch series, see:
https://git.linaro.org/people/baolin.wang/upstream_0627.git

Thoughts and feedback would be appreciated.

Baolin Wang (6):
  time: Introduce struct itimerspec64
  timekeeping: Introduce current_kernel_time64()
  security: Introduce security_settime64()
  time: Introduce do_sys_settimeofday64()
  time: Introduce timespec64_to_jiffies()/jiffies_to_timespec64()
  cputime: Introduce cputime_to_timespec64()/timespec64_to_cputime()

 arch/powerpc/include/asm/cputime.h    |    6 +++---
 arch/s390/include/asm/cputime.h       |    8 ++++----
 include/asm-generic/cputime_jiffies.h |   10 +++++-----
 include/asm-generic/cputime_nsecs.h   |    6 +++---
 include/linux/cputime.h               |   16 +++++++++++++++
 include/linux/jiffies.h               |   22 ++++++++++++++++++---
 include/linux/lsm_hooks.h             |    5 +++--
 include/linux/security.h              |   20 ++++++++++++++++---
 include/linux/time64.h                |   35 +++++++++++++++++++++++++++++++++
 include/linux/timekeeping.h           |   24 +++++++++++++++++++---
 kernel/time/time.c                    |   28 +++++++++++++++-----------
 kernel/time/timekeeping.c             |    6 +++---
 security/commoncap.c                  |    2 +-
 security/security.c                   |    2 +-
 14 files changed, 148 insertions(+), 42 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2015-07-15  5:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15  5:47 Baolin Wang [this message]
2015-07-15  5:51 ` [PATCH 1/6] time: Introduce struct itimerspec64 Baolin Wang
2015-07-15  5:54 ` [PATCH 2/6] timekeeping: Introduce current_kernel_time64() Baolin Wang
2015-07-15  5:57 ` [PATCH 3/6] security: Introduce security_settime64() Baolin Wang
2015-07-15 10:24   ` Thomas Gleixner
2015-07-15 11:34     ` Baolin Wang
2015-07-15  6:01 ` [PATCH 4/6] time: Introduce do_sys_settimeofday64() Baolin Wang
2015-07-15  6:04 ` [PATCH 5/6] time: Introduce timespec64_to_jiffies()/jiffies_to_timespec64() Baolin Wang
2015-07-15  6:07 ` [PATCH 6/6] cputime: Introduce cputime_to_timespec64()/timespec64_to_cputime() Baolin Wang
2015-07-15 10:31   ` Thomas Gleixner
2015-07-15 11:42     ` Baolin Wang
2015-07-15 11:42       ` Baolin Wang
2015-07-15 11:55       ` Thomas Gleixner
2015-07-15 11:55         ` Thomas Gleixner
2015-07-16  2:22         ` Baolin Wang
2015-07-16  2:22           ` Baolin Wang
2015-07-16 10:43           ` Thomas Gleixner
2015-07-17  8:39             ` Baolin Wang

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=cover.1436511577.git.baolin.wang@linaro.org \
    --to=baolin.wang@linaro.org \
    --cc=ahh@google.com \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=casey@schaufler-ca.com \
    --cc=cl@linux.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=heenasirwani@gmail.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hofrat@osadl.org \
    --cc=james.l.morris@oracle.com \
    --cc=jlayton@primarydata.com \
    --cc=john.johansen@canonical.com \
    --cc=john.stultz@linaro.org \
    --cc=keescook@chromium.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux390@de.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mingo@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=neilb@suse.de \
    --cc=pang.xunlei@linaro.org \
    --cc=paul@paul-moore.com \
    --cc=paulus@samba.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=rth@twiddle.net \
    --cc=schwidefsky@de.ibm.com \
    --cc=sds@tycho.nsa.gov \
    --cc=serge.hallyn@canonical.com \
    --cc=serge@hallyn.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=y2038@lists.linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.