From: Deepa Dinamani <deepa.kernel@gmail.com>
To: viro@zeniv.linux.org.uk, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Cc: arnd@arndb.de, y2038@lists.linaro.org,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
linux-aio@kvack.org
Subject: [PATCH v4 0/5] y2038: Make ppoll, io_pgetevents and pselect y2038 safe
Date: Wed, 19 Sep 2018 21:41:03 -0700 [thread overview]
Message-ID: <20180920044108.6606-1-deepa.kernel@gmail.com> (raw)
The series transitions the ppoll, io_getevents, and pselect syscalls
to be y2038 safe.
This is part of the work proceeding for syscalls for y2038.
It is based on the series [1] from Arnd Bergmann.
The overview of the series is as below:
1. Refactor sigmask handling logic for the above syscalls.
2. Provide y2038 safe versions of the syscalls for all ABIs.
[1] https://lkml.org/lkml/2018/8/27/651
Changes since v3:
* fixed pselect copy+paste error
Changes since v2:
* remove 64BIT_TIME conditional for ppoll, pselect,
io_getpevents as per review comments
Changes since v1:
* fixed bug pointed out by arnd
Deepa Dinamani (5):
signal: Add set_user_sigmask()
signal: Add restore_user_sigmask()
ppoll: use __kernel_timespec
pselect6: use __kernel_timespec
io_pgetevents: use __kernel_timespec
fs/aio.c | 134 ++++++++++-----
fs/eventpoll.c | 52 +-----
fs/select.c | 360 ++++++++++++++++++++++-----------------
include/linux/compat.h | 20 +++
include/linux/signal.h | 4 +
include/linux/syscalls.h | 20 ++-
kernel/signal.c | 78 +++++++++
7 files changed, 426 insertions(+), 242 deletions(-)
--
2.17.1
next reply other threads:[~2018-09-20 4:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 4:41 Deepa Dinamani [this message]
2018-09-20 4:41 ` [PATCH v4 1/5] signal: Add set_user_sigmask() Deepa Dinamani
2018-09-20 4:41 ` Deepa Dinamani
2018-09-20 4:41 ` [PATCH v4 2/5] signal: Add restore_user_sigmask() Deepa Dinamani
2018-09-20 4:41 ` [PATCH v4 3/5] ppoll: use __kernel_timespec Deepa Dinamani
2018-09-20 4:41 ` Deepa Dinamani
2018-09-20 4:41 ` [PATCH v4 4/5] pselect6: " Deepa Dinamani
2018-09-20 4:41 ` Deepa Dinamani
2018-09-20 4:41 ` [PATCH v4 5/5] io_pgetevents: " Deepa Dinamani
2018-09-20 4:41 ` Deepa Dinamani
2018-12-06 16:26 ` [PATCH v4 0/5] y2038: Make ppoll, io_pgetevents and pselect y2038 safe Arnd Bergmann
2018-12-06 16:26 ` 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=20180920044108.6606-1-deepa.kernel@gmail.com \
--to=deepa.kernel@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-aio@kvack.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--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.