Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752464AbdHJCAf (ORCPT ); Wed, 9 Aug 2017 22:00:35 -0400 Received: from mail-oi0-f53.google.com ([209.85.218.53]:36647 "EHLO mail-oi0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752386AbdHJCAc (ORCPT ); Wed, 9 Aug 2017 22:00:32 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Baolin Wang Date: Thu, 10 Aug 2017 10:00:31 +0800 Message-ID: Subject: Re: [PATCH 0/3] Fix y2038 issues for security/keys subsystem To: Arnd Bergmann Cc: David Howells , David Miller , James Morris , "Serge E. Hallyn" , marc.dionne@auristor.com, Dan Carpenter , "Jason A. Donenfeld" , Mark Brown , keyrings@vger.kernel.org, Linux Kernel Mailing List , LSM List , Networking Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 972 Lines: 30 Hi Arnd, On 9 August 2017 at 16:44, Arnd Bergmann wrote: > On Wed, Aug 9, 2017 at 4:51 AM, Baolin Wang wrote: >> 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 and net/rxrpc subsystem which is connected with security/keys >> subsystem. >> >> Baolin Wang (3): >> security: keys: Replace time_t/timespec with time64_t >> security: keys: Replace time_t with time64_t for struct >> key_preparsed_payload >> net: rxrpc: Replace time_t type with time64_t type > > Hi David, > > I did a private review before Baolin posted these patches, this version look > correct to me, though I would like to see some clarification from you for the > rxrpc portion, I'll reply there separately. > > All three patches > > Reviewed-by: Arnd Bergmann Thanks for your reviewed tag. -- Baolin.wang Best Regards