All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linaro.org>
To: linux-security-module@vger.kernel.org
Subject: [PATCH v2 0/2] Fix y2038 issues for security/keys subsystem
Date: Thu, 21 Sep 2017 02:32:01 +0000	[thread overview]
Message-ID: <cover.1505960744.git.baolin.wang@linaro.org> (raw)

Since 'time_t', 'timeval' and 'timespec' types are not year 2038 safe on
32 bits system, this patchset tries to fix this issues for security/keys
subsystem.

Changes since v1:
 - Add reviewed tag from Arnd.
 - Drop Patch 3 which had been merged into kernel 4.14 by David.

Baolin Wang (2):
  security: keys: Replace time_t/timespec with time64_t
  security: keys: Replace time_t with time64_t for struct
    key_preparsed_payload

 include/linux/key-type.h     |    2 +-
 include/linux/key.h          |    7 ++++---
 security/keys/gc.c           |   20 ++++++++++----------
 security/keys/internal.h     |    8 ++++----
 security/keys/key.c          |   27 ++++++++++-----------------
 security/keys/keyring.c      |   18 +++++++++---------
 security/keys/permission.c   |    3 +--
 security/keys/proc.c         |   20 ++++++++++----------
 security/keys/process_keys.c |    2 +-
 9 files changed, 50 insertions(+), 57 deletions(-)

-- 
1.7.9.5


WARNING: multiple messages have this Message-ID (diff)
From: Baolin Wang <baolin.wang@linaro.org>
To: dhowells@redhat.com
Cc: james.l.morris@oracle.com, serge@hallyn.com, arnd@arndb.de,
	broonie@kernel.org, keyrings@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org, baolin.wang@linaro.org
Subject: [PATCH v2 0/2] Fix y2038 issues for security/keys subsystem
Date: Thu, 21 Sep 2017 10:32:01 +0800	[thread overview]
Message-ID: <cover.1505960744.git.baolin.wang@linaro.org> (raw)

Since 'time_t', 'timeval' and 'timespec' types are not year 2038 safe on
32 bits system, this patchset tries to fix this issues for security/keys
subsystem.

Changes since v1:
 - Add reviewed tag from Arnd.
 - Drop Patch 3 which had been merged into kernel 4.14 by David.

Baolin Wang (2):
  security: keys: Replace time_t/timespec with time64_t
  security: keys: Replace time_t with time64_t for struct
    key_preparsed_payload

 include/linux/key-type.h     |    2 +-
 include/linux/key.h          |    7 ++++---
 security/keys/gc.c           |   20 ++++++++++----------
 security/keys/internal.h     |    8 ++++----
 security/keys/key.c          |   27 ++++++++++-----------------
 security/keys/keyring.c      |   18 +++++++++---------
 security/keys/permission.c   |    3 +--
 security/keys/proc.c         |   20 ++++++++++----------
 security/keys/process_keys.c |    2 +-
 9 files changed, 50 insertions(+), 57 deletions(-)

-- 
1.7.9.5

WARNING: multiple messages have this Message-ID (diff)
From: baolin.wang@linaro.org (Baolin Wang)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v2 0/2] Fix y2038 issues for security/keys subsystem
Date: Thu, 21 Sep 2017 10:32:01 +0800	[thread overview]
Message-ID: <cover.1505960744.git.baolin.wang@linaro.org> (raw)

Since 'time_t', 'timeval' and 'timespec' types are not year 2038 safe on
32 bits system, this patchset tries to fix this issues for security/keys
subsystem.

Changes since v1:
 - Add reviewed tag from Arnd.
 - Drop Patch 3 which had been merged into kernel 4.14 by David.

Baolin Wang (2):
  security: keys: Replace time_t/timespec with time64_t
  security: keys: Replace time_t with time64_t for struct
    key_preparsed_payload

 include/linux/key-type.h     |    2 +-
 include/linux/key.h          |    7 ++++---
 security/keys/gc.c           |   20 ++++++++++----------
 security/keys/internal.h     |    8 ++++----
 security/keys/key.c          |   27 ++++++++++-----------------
 security/keys/keyring.c      |   18 +++++++++---------
 security/keys/permission.c   |    3 +--
 security/keys/proc.c         |   20 ++++++++++----------
 security/keys/process_keys.c |    2 +-
 9 files changed, 50 insertions(+), 57 deletions(-)

-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2017-09-21  2:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21  2:32 Baolin Wang [this message]
2017-09-21  2:32 ` [PATCH v2 0/2] Fix y2038 issues for security/keys subsystem Baolin Wang
2017-09-21  2:32 ` Baolin Wang
2017-09-21  2:32 ` [PATCH v2 1/2] security: keys: Replace time_t/timespec with time64_t Baolin Wang
2017-09-21  2:32   ` Baolin Wang
2017-09-21  2:32   ` Baolin Wang
2017-09-21  2:32 ` [PATCH v2 2/2] security: keys: Replace time_t with time64_t for struct key_preparsed_payload Baolin Wang
2017-09-21  2:32   ` Baolin Wang
2017-09-21  2:32   ` Baolin Wang
2017-09-28  9:11 ` [PATCH v2 0/2] Fix y2038 issues for security/keys subsystem James Morris
2017-09-28  9:11   ` James Morris
2017-09-28  9:11   ` James Morris
2017-09-28  9:26 ` David Howells
2017-09-28  9:26   ` David Howells
2017-09-28  9:26   ` David Howells
2017-09-28  9:48   ` James Morris
2017-09-28  9:48     ` James Morris
2017-09-28  9:48     ` James Morris
2017-09-28 22:05     ` Baolin Wang
2017-09-28 22:05       ` Baolin Wang
2017-09-28 22:05       ` 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.1505960744.git.baolin.wang@linaro.org \
    --to=baolin.wang@linaro.org \
    --cc=linux-security-module@vger.kernel.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.