From: Bamvor Zhang Jian <bamvor.zhangjian@linaro.org>
To: arnd@arndb.de, john.stultz@linaro.org, tglx@linutronix.de
Cc: y2039@lists.linaro.org, linux-kernel@vger.kernel.org,
bamvor.zhangjian@linaro.org
Subject: [RFC PATCH v2 0/4] Convert ppdev to y2038 safe
Date: Mon, 29 Jun 2015 22:23:23 +0800 [thread overview]
Message-ID: <1435587807-10008-1-git-send-email-bamvor.zhangjian@linaro.org> (raw)
Hi, guys
This is my second attempt to convert ppdev to y2038 safe. The first
version is here[1].
There are two parts in my patches.
01/02 migrate timeval relative struct to 64bit time_t types.
03/04 convert ppdev to y2038 safe in both native 32bit and compat
application.
My patches try to follow the idea from arnd y2038 syscalls patches[2],
but my patches not depend on them.
The reason why I choose ppdev is the ppdev use the timexxx directly
in ioctl compare with the other drivers embedded timexxx in their
own type.
Build pass on arm and arm64 on each patches(with and without
CONFIG_COMPAT_TIME). Unfortunately, there is no parport device
(printer) in my test environment. Hope others could help to test
it.
[1] https://lists.linaro.org/pipermail/y2038/2015-June/000522.html
[2] http://git.kernel.org/cgit/linux/kernel/git/arnd/playground.git/log/?h=y2038-syscalls
Bamvor Zhang Jian (4):
y2038: add 64bit time_t support in timeval for 32bit architecture
time64: add timeval64 helper for compat syscalls
ppdev: add compat ioctl
y2038: convert ppdev to 2038 safe
drivers/char/ppdev.c | 41 ++++++++++++++++++++++++++++++++++-------
include/linux/compat.h | 3 +++
include/linux/time64.h | 20 ++++++++++++++++++--
include/uapi/linux/ppdev.h | 14 ++++++++++++--
include/uapi/linux/time.h | 16 ++++++++++++++++
kernel/compat.c | 17 +++++++++++++++++
kernel/time/time.c | 36 ++++++++++++++++++++++++++++++++++++
7 files changed, 136 insertions(+), 11 deletions(-)
--
2.1.4
next reply other threads:[~2015-06-29 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 14:23 Bamvor Zhang Jian [this message]
2015-06-29 14:23 ` [RFC PATCH v2 1/4] y2038: add 64bit time_t support in timeval for 32bit architecture Bamvor Zhang Jian
2015-07-08 20:09 ` John Stultz
2015-07-09 9:02 ` Bamvor Zhang Jian
2015-07-09 10:26 ` Arnd Bergmann
2015-07-15 3:18 ` Bamvor Zhang Jian
2015-07-15 9:33 ` Arnd Bergmann
2015-06-29 14:23 ` [RFC PATCH v2 2/4] time64: add timeval64 helper for compat syscalls Bamvor Zhang Jian
2015-06-29 14:23 ` [RFC PATCH v2 3/4] ppdev: add compat ioctl Bamvor Zhang Jian
2015-07-08 20:17 ` John Stultz
2015-07-08 21:28 ` [Y2038] " Arnd Bergmann
2015-06-29 14:23 ` [RFC PATCH v2 4/4] y2038: convert ppdev to 2038 safe Bamvor Zhang Jian
2015-07-08 21:34 ` Arnd Bergmann
2015-07-08 21:36 ` Arnd Bergmann
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=1435587807-10008-1-git-send-email-bamvor.zhangjian@linaro.org \
--to=bamvor.zhangjian@linaro.org \
--cc=arnd@arndb.de \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=y2039@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).