From patchwork Fri Nov 8 21:32:51 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Arnd Bergmann X-Patchwork-Id: 178997 Delivered-To: patch@linaro.org Received: by 2002:a92:38d5:0:0:0:0:0 with SMTP id g82csp3314996ilf; Fri, 8 Nov 2019 13:37:14 -0800 (PST) X-Google-Smtp-Source: APXvYqy/C/rqgDr6cScwAhYSL37GFSd8igcBqZkzckIDyJeKdjJSjBAK0Caa18YXQmW28JdWdVCm X-Received: by 2002:a17:906:49c9:: with SMTP id w9mr10873585ejv.309.1573249034750; Fri, 08 Nov 2019 13:37:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573249034; cv=none; d=google.com; s=arc-20160816; b=gOikWtdbwy2TyhuenGCI5qEwvpLYxlgnf52rgWnL8e9Hq8iJDRR/unlL2XdOdq+4yf F6vJdNSJ/rwJPdssZIrKXsVjkuucPPLE3ap3j9ad/Pa3MnIOhVc8u/NeL5itdcgyRkkq f/7k5Rg2Rgx5/wndYJc+lTFYV18Jn9RA/wkAyR02JRB3DkLD+5m00UKynlffGOkfDX4e ekZ3RtUEFHx7K3gk/bUXtuwfx/b0UlQeRYirMCYZJecqsQoY6een8aZyAlEsEJh6R93H P659bZHEzpPwvqnFvE3JPqVve/cKs0OUG8pK8cp/9mlKkifzyRvXAJjkUMNrXDpBtXon kBpQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=tdcQVmlcbd9qVHHPrGolH7/kVZArJ1/bKcQKmaujOU4=; b=tjMmauV1StsCkEAZYp7Ce5iJnO6++fMrLclhAgP9Iu6ldcojj5QBbJZ0pGLPnGKXrB xcpyGmIoFJWfv6o4eebn26Kv7T4jAkzMBMei3cbK9GlRYy3718ZAg4x/QC+d8PKShBGf ykDi9vFRaObXXmxSYnMJ1hWOZ6vv+8GA8iREdN2noBeglJJMsTNlZ2Oq7TxSBt2O8UZf vXrAeq9JjfwAqiK+qnEvDdNIehsiYBqNMqO0GA/dwkPD/WRKC2Tki4QyjCPgw14+pLwW UGHcDwXGUYBJjxMC54ANiGfvfBfAfrXJhwBAM/acSWEH12rgRNRela8ze2RevCVyOt0j zEWw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bi3si5494456edb.331.2019.11.08.13.37.14; Fri, 08 Nov 2019 13:37:14 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388171AbfKHVhL (ORCPT + 26 others); Fri, 8 Nov 2019 16:37:11 -0500 Received: from mout.kundenserver.de ([212.227.126.135]:60559 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388098AbfKHVhK (ORCPT ); Fri, 8 Nov 2019 16:37:10 -0500 Received: from threadripper.lan ([149.172.19.189]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.129]) with ESMTPA (Nemesis) id 1N1x2P-1hmtCN33vd-012Dzx; Fri, 08 Nov 2019 22:37:06 +0100 From: Arnd Bergmann To: y2038@lists.linaro.org Cc: linux-kernel@vger.kernel.org, Arnd Bergmann , Viacheslav Dubeyko , =?utf-8?q?Ernesto_A=2E_Fern=C3=A1ndez?= , Andrew Morton , linux-fsdevel@vger.kernel.org Subject: [PATCH 13/16] hfs/hfsplus: use 64-bit inode timestamps Date: Fri, 8 Nov 2019 22:32:51 +0100 Message-Id: <20191108213257.3097633-14-arnd@arndb.de> X-Mailer: git-send-email 2.20.0 In-Reply-To: <20191108213257.3097633-1-arnd@arndb.de> References: <20191108213257.3097633-1-arnd@arndb.de> MIME-Version: 1.0 X-Provags-ID: V03:K1:dFOmQMTQtnWEyRN1FoOfYEBxuK8+hd8DreubJy9bt74CPr2b+nd vT2+1QEmWCQGca4MDg4bRywB1F/gzNzmBGqy3NiCvcbAEyDw7ZB0fHGUp650Fd4r6MT0C6E irwn6c/ra7H+2MDw0UaK0CMmc/ers51foyfk7oY8kkdokn7V3DBBFxf43lLxBOFTeFp5XAB RvzzR3L0+ww7/uSh5kE9Q== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1; V03:K0:hJaojAvmzhQ=:owmkYgBYYh01+71gpm17fZ CnVZxG2ABiDYuoiyq2v7zUBtcJC3nGaOf+ipNAwmIr4MiR4vT744PnD3T6V2A+esxyVHhXhLg Z5dJzygp7izpC/QiooJhTPTcPg9WTFhkhYNjSpM+5iYKNZqI5cUbLLq7EWd+4HeQWgCwkE/XR itOW8aawVHIVLCtS6fM+qJ5VzpPia4QxxpgaJVUqmgBfX8Q9kRXjfqOW/IZlBu+uxZ/pGd3Rc xTsOVil6Jyb5gYoIVRNyWSAyO0+JWdsjtpNi2lQ8zdnZh3uJGMaQ0ncAV1tOlzb2HOnvy1EDU hSQILNs8dEMrfR0UdBk33b3CQhTuvUfaLtjzWLjc+vGkwEzLFlPcSpMrbjjP5qYCtgThV50vd 0kchu6ER/Inq2tsfCiIda8tKREzCTbz6vy74nX34dSfSQ+xk+bi8KZwgTyj2vsOoScbMJears 6/DOdonQTq4ANbRxijkHVbzeQ4FJisKDA7LIzmj9DJxVOI5wY8+rO41/YS6QKy0z7pjxRJbIX mac0zTiWzZL27TPDd65cQCc4K8lov6drjhpA9km5fVm8Mn44HubxZ52RDXiKNMSIm65XseCyG 8dFA/RSlYzaXm2ddEAbJqgmeL7aP0SaK3inWdKyg11rmtpjnnsEw1miD+q7rBAEFTt1ltFr1p tzIkrK3C59unnN6V23mQaAqw//YFGBwYVcT23MKU1Io6Kwhbt9WDD/uul1YwQHLPE7Hdicux+ o6ME5gXQL7E1pOj+uxqvIfUDQFQ8jXW0bgA6r442QaJJ+31gcFQ9fNJ4iGB2mFq6g5ym9D0X5 OUQpRWv6N4gC+JrYMhB0mfaVUHEyPXnGFkd854qkzes9mRdywG/9TamroKQ6DSEFxoVD2FVld Ztz4lVnETJRAJ/uIIqjQ== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The interpretation of on-disk timestamps in HFS and HFS+ differs between 32-bit and 64-bit kernels at the moment. Use 64-bit timestamps consistently so apply the current 64-bit behavior everyhere. According to the official documentation for HFS+ [1], inode timestamps are supposed to cover the time range from 1904 to 2040 as originally used in classic MacOS. The traditional Linux usage is to convert the timestamps into an unsigned 32-bit number based on the Unix epoch and from there to a time_t. On 32-bit systems, that wraps the time from 2038 to 1902, so the last two years of the valid time range become garbled. On 64-bit systems, all times before 1970 get turned into timestamps between 2038 and 2106, which is more convenient but also different from the documented behavior. Looking at the Darwin sources [2], it seems that MacOS is inconsistent in yet another way: all timestamps are wrapped around to a 32-bit unsigned number when written to the disk, but when read back, all numeric values lower than 2082844800U are assumed to be invalid, so we cannot represent the times before 1970 or the times after 2040. While all implementations seem to agree on the interpretation of values between 1970 and 2038, they often differ on the exact range they support when reading back values outside of the common range: MacOS (traditional): 1904-2040 Apple Documentation: 1904-2040 MacOS X source comments: 1970-2040 MacOS X source code: 1970-2038 32-bit Linux: 1902-2038 64-bit Linux: 1970-2106 hfsfuse: 1970-2040 hfsutils (32 bit, old libc) 1902-2038 hfsutils (32 bit, new libc) 1970-2106 hfsutils (64 bit) 1904-2040 hfsplus-utils 1904-2040 hfsexplorer 1904-2040 7-zip 1904-2040 Out of the above, the range from 1970 to 2106 seems to be the most useful, as it allows using HFS and HFS+ beyond year 2038, and this matches the behavior that most users would see today on Linux, as few people run 32-bit kernels any more. Link: [1] https://developer.apple.com/library/archive/technotes/tn/tn1150.html Link: [2] https://opensource.apple.com/source/hfs/hfs-407.30.1/core/MacOSStubs.c.auto.html Link: https://lore.kernel.org/lkml/20180711224625.airwna6gzyatoowe@eaf/ Cc: Viacheslav Dubeyko Suggested-by: "Ernesto A. Fernández" Signed-off-by: Arnd Bergmann --- v3: revert back to 1970-2106 time range fix bugs found in review merge both patches into one drop cc:stable tag v2: treat pre-1970 dates as invalid following MacOS X behavior, reword and expand changelog text --- fs/hfs/hfs_fs.h | 26 ++++++++++++++++++++------ fs/hfs/inode.c | 4 ++-- fs/hfsplus/hfsplus_fs.h | 26 +++++++++++++++++++++----- fs/hfsplus/inode.c | 12 ++++++------ 4 files changed, 49 insertions(+), 19 deletions(-) -- 2.20.0 Reviewed-by: Ernesto A. Fernández Reviewed-by: Vyacheslav Dubeyko diff --git a/fs/hfs/hfs_fs.h b/fs/hfs/hfs_fs.h index 6d0783e2e276..26733051ee50 100644 --- a/fs/hfs/hfs_fs.h +++ b/fs/hfs/hfs_fs.h @@ -242,19 +242,33 @@ extern void hfs_mark_mdb_dirty(struct super_block *sb); /* * There are two time systems. Both are based on seconds since * a particular time/date. - * Unix: unsigned lil-endian since 00:00 GMT, Jan. 1, 1970 + * Unix: signed little-endian since 00:00 GMT, Jan. 1, 1970 * mac: unsigned big-endian since 00:00 GMT, Jan. 1, 1904 * + * HFS implementations are highly inconsistent, this one matches the + * traditional behavior of 64-bit Linux, giving the most useful + * time range between 1970 and 2106, by treating any on-disk timestamp + * under 2082844800U (Jan 1 1970) as a time between 2040 and 2106. */ -#define __hfs_u_to_mtime(sec) cpu_to_be32(sec + 2082844800U - sys_tz.tz_minuteswest * 60) -#define __hfs_m_to_utime(sec) (be32_to_cpu(sec) - 2082844800U + sys_tz.tz_minuteswest * 60) +static inline time64_t __hfs_m_to_utime(__be32 mt) +{ + time64_t ut = (u32)(be32_to_cpu(mt) - 2082844800U); + + return ut + sys_tz.tz_minuteswest * 60; +} +static inline __be32 __hfs_u_to_mtime(time64_t ut) +{ + ut -= sys_tz.tz_minuteswest * 60; + + return cpu_to_be32(lower_32_bits(ut) + 2082844800U); +} #define HFS_I(inode) (container_of(inode, struct hfs_inode_info, vfs_inode)) #define HFS_SB(sb) ((struct hfs_sb_info *)(sb)->s_fs_info) -#define hfs_m_to_utime(time) (struct timespec){ .tv_sec = __hfs_m_to_utime(time) } -#define hfs_u_to_mtime(time) __hfs_u_to_mtime((time).tv_sec) -#define hfs_mtime() __hfs_u_to_mtime(get_seconds()) +#define hfs_m_to_utime(time) (struct timespec64){ .tv_sec = __hfs_m_to_utime(time) } +#define hfs_u_to_mtime(time) __hfs_u_to_mtime((time).tv_sec) +#define hfs_mtime() __hfs_u_to_mtime(ktime_get_real_seconds()) static inline const char *hfs_mdb_name(struct super_block *sb) { diff --git a/fs/hfs/inode.c b/fs/hfs/inode.c index da243c84e93b..2f224b98ee94 100644 --- a/fs/hfs/inode.c +++ b/fs/hfs/inode.c @@ -351,7 +351,7 @@ static int hfs_read_inode(struct inode *inode, void *data) inode->i_mode &= ~hsb->s_file_umask; inode->i_mode |= S_IFREG; inode->i_ctime = inode->i_atime = inode->i_mtime = - timespec_to_timespec64(hfs_m_to_utime(rec->file.MdDat)); + hfs_m_to_utime(rec->file.MdDat); inode->i_op = &hfs_file_inode_operations; inode->i_fop = &hfs_file_operations; inode->i_mapping->a_ops = &hfs_aops; @@ -362,7 +362,7 @@ static int hfs_read_inode(struct inode *inode, void *data) HFS_I(inode)->fs_blocks = 0; inode->i_mode = S_IFDIR | (S_IRWXUGO & ~hsb->s_dir_umask); inode->i_ctime = inode->i_atime = inode->i_mtime = - timespec_to_timespec64(hfs_m_to_utime(rec->dir.MdDat)); + hfs_m_to_utime(rec->dir.MdDat); inode->i_op = &hfs_dir_inode_operations; inode->i_fop = &hfs_dir_operations; break; diff --git a/fs/hfsplus/hfsplus_fs.h b/fs/hfsplus/hfsplus_fs.h index b8471bf05def..22d0a22c41a3 100644 --- a/fs/hfsplus/hfsplus_fs.h +++ b/fs/hfsplus/hfsplus_fs.h @@ -533,13 +533,29 @@ int hfsplus_submit_bio(struct super_block *sb, sector_t sector, void *buf, void **data, int op, int op_flags); int hfsplus_read_wrapper(struct super_block *sb); -/* time macros */ -#define __hfsp_mt2ut(t) (be32_to_cpu(t) - 2082844800U) -#define __hfsp_ut2mt(t) (cpu_to_be32(t + 2082844800U)) +/* + * time helpers: convert between 1904-base and 1970-base timestamps + * + * HFS+ implementations are highly inconsistent, this one matches the + * traditional behavior of 64-bit Linux, giving the most useful + * time range between 1970 and 2106, by treating any on-disk timestamp + * under 2082844800U (Jan 1 1970) as a time between 2040 and 2106. + */ +static inline time64_t __hfsp_mt2ut(__be32 mt) +{ + time64_t ut = (u32)(be32_to_cpu(mt) - 2082844800U); + + return ut; +} + +static inline __be32 __hfsp_ut2mt(time64_t ut) +{ + return cpu_to_be32(lower_32_bits(ut) + 2082844800U); +} /* compatibility */ -#define hfsp_mt2ut(t) (struct timespec){ .tv_sec = __hfsp_mt2ut(t) } +#define hfsp_mt2ut(t) (struct timespec64){ .tv_sec = __hfsp_mt2ut(t) } #define hfsp_ut2mt(t) __hfsp_ut2mt((t).tv_sec) -#define hfsp_now2mt() __hfsp_ut2mt(get_seconds()) +#define hfsp_now2mt() __hfsp_ut2mt(ktime_get_real_seconds()) #endif diff --git a/fs/hfsplus/inode.c b/fs/hfsplus/inode.c index d131c8ea7eb6..94bd83b36644 100644 --- a/fs/hfsplus/inode.c +++ b/fs/hfsplus/inode.c @@ -504,9 +504,9 @@ int hfsplus_cat_read_inode(struct inode *inode, struct hfs_find_data *fd) hfsplus_get_perms(inode, &folder->permissions, 1); set_nlink(inode, 1); inode->i_size = 2 + be32_to_cpu(folder->valence); - inode->i_atime = timespec_to_timespec64(hfsp_mt2ut(folder->access_date)); - inode->i_mtime = timespec_to_timespec64(hfsp_mt2ut(folder->content_mod_date)); - inode->i_ctime = timespec_to_timespec64(hfsp_mt2ut(folder->attribute_mod_date)); + inode->i_atime = hfsp_mt2ut(folder->access_date); + inode->i_mtime = hfsp_mt2ut(folder->content_mod_date); + inode->i_ctime = hfsp_mt2ut(folder->attribute_mod_date); HFSPLUS_I(inode)->create_date = folder->create_date; HFSPLUS_I(inode)->fs_blocks = 0; if (folder->flags & cpu_to_be16(HFSPLUS_HAS_FOLDER_COUNT)) { @@ -542,9 +542,9 @@ int hfsplus_cat_read_inode(struct inode *inode, struct hfs_find_data *fd) init_special_inode(inode, inode->i_mode, be32_to_cpu(file->permissions.dev)); } - inode->i_atime = timespec_to_timespec64(hfsp_mt2ut(file->access_date)); - inode->i_mtime = timespec_to_timespec64(hfsp_mt2ut(file->content_mod_date)); - inode->i_ctime = timespec_to_timespec64(hfsp_mt2ut(file->attribute_mod_date)); + inode->i_atime = hfsp_mt2ut(file->access_date); + inode->i_mtime = hfsp_mt2ut(file->content_mod_date); + inode->i_ctime = hfsp_mt2ut(file->attribute_mod_date); HFSPLUS_I(inode)->create_date = file->create_date; } else { pr_err("bad catalog entry used to create inode\n");