Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp661302pxb; Tue, 3 Nov 2020 09:08:17 -0800 (PST) X-Google-Smtp-Source: ABdhPJyn6Mm1x2Lz/vzx1o5brTY5wPARlFy10IeILvlNnF2rAKAlFALBHz4Xr6P/sR7lwthjoZlP X-Received: by 2002:a17:906:2444:: with SMTP id a4mr2186963ejb.415.1604423297253; Tue, 03 Nov 2020 09:08:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604423297; cv=none; d=google.com; s=arc-20160816; b=1AufyVfzTak7UPVN6VZJ2cNszD8WvPND97cfw0/c8rfuqTXlIbrwSWLDhLEHHbx+j5 Grxl760ERhl5gokaeIKgOApyLGHVCNCaidx8dtHdfkxYv92T0Y/x2MEBgveW7xVYt2Uf mE4sonex9gasLzPeZcibFeqcoklAGCQHZzJLsQk9QFCjF0hX6Ts/PJEeGUvDJhEs1q8q DMvK1pEuvAtwH3vlUhZXLoZ1HZuw+uvlU0bgd0b5MJ/3x5OXuGEjUvrJy2Lh4eU1mdd6 cRAgZJK6LYUweeO/PjHQQBox0gGAFw/yjus/fJRzoUJXzFe1OnOFpJqevMt9zlmCFQqK STWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=P6Nqd/GTymSo6mkhELu0bxwV3r/gwkmZPBYT64Awjzw=; b=ian2VXGo/jiL05q+maZ/HjoP6pHCHwn3d9iz6RPj7EY4zhiWtaZDMxgcYhldU4FFaX nrdRXSjVbL3EZ3HZ2bK1s3n6OjHtu1gLhtN9sPvNxwf24fwGQEnZAqU8ojskCznt9iFH GQVR9SEG9l4nQbfGnSyRekdPzUM5VcNKzCM3DEZ0YYa/B0ZWB0sg43FC72Efm3mSh3gh e7ijzIVn/8t+10xW/YSCF5o/jY8v/+CzvsCkChqVGfWyC2PReG400ZaTTLv8AhZyN/Ak QK0/F3cwpm3QY0VezHGfOH05jptMXVw1Blg/rsft1KnIC8snmbyRHVgulzTMBf8qPrz4 KFSw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=AtMg9SkL; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t14si12627336ejy.440.2020.11.03.09.07.52; Tue, 03 Nov 2020 09:08:17 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=AtMg9SkL; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728302AbgKCREh (ORCPT + 99 others); Tue, 3 Nov 2020 12:04:37 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:43016 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726581AbgKCREg (ORCPT ); Tue, 3 Nov 2020 12:04:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1604423075; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=P6Nqd/GTymSo6mkhELu0bxwV3r/gwkmZPBYT64Awjzw=; b=AtMg9SkLmD8daTfJvCVedE33/KZel2QOvzczQNhuwIkWe/oT0eMYNPjEm8Rm11D3Z/AaJq zXLaOVoRGmw5y9vd7ec+2Q+HAfE+q/56eQK8qq+gVj0DJgun6WYIBT0aiCLZdcAqUtzkF4 lcPvvjkGLB1Xud2AjORC8nLWpRLypIw= Received: from mail-pf1-f197.google.com (mail-pf1-f197.google.com [209.85.210.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-481-IRH0COoaO0G5xTPdHbmLXQ-1; Tue, 03 Nov 2020 12:04:33 -0500 X-MC-Unique: IRH0COoaO0G5xTPdHbmLXQ-1 Received: by mail-pf1-f197.google.com with SMTP id z12so12554944pfa.22 for ; Tue, 03 Nov 2020 09:04:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=P6Nqd/GTymSo6mkhELu0bxwV3r/gwkmZPBYT64Awjzw=; b=gH2ooGWtMYcvi/SSsY7yyL1aERRvEW1O79ZfjfFHVHdhNFJn6R+aSqOgls5BJ7Vbvy G5NY0PQC8j2Yv7xICFHf/HPJNlpscyVQUEZztOuRn8NmH2yGoVzpNvOd+Dkz/sQTg6RM 0ktf8l1xA0jzcD2+IUG+dasjHQqFqEifiXDZugKhHnKo6wWt8qtSMEfFmiblWUfQU6eZ Fcxaqmo15bbbvFFHCuOTr2li7o3wQEDXcVGsOeyBJAwljGTgVkSFFPzzKDSM2sqrBLTn gteuJOSB3TEiCOO6LAPaMHhb9HKV0HQCGCd0hCsceTXQ4PxFcqfhWyMup7sMmRAbfqiD 8Ysw== X-Gm-Message-State: AOAM530Zop265rhHn2ozcIBRFowRC00xp8gKhh2mphkOcsaBpBr+ujBs ioEb4kGigNnZ10xLhP/o8bIPxu8kyqdTKI+QFa6blz244DfMY9k6bWmbuEDxengVhpucDxN8h3Q WU/r376zjtkwlRsqZtGnBoA/F X-Received: by 2002:a17:90a:7089:: with SMTP id g9mr160162pjk.4.1604423072874; Tue, 03 Nov 2020 09:04:32 -0800 (PST) X-Received: by 2002:a17:90a:7089:: with SMTP id g9mr160141pjk.4.1604423072675; Tue, 03 Nov 2020 09:04:32 -0800 (PST) Received: from xiangao.remote.csb ([209.132.188.80]) by smtp.gmail.com with ESMTPSA id v24sm15775598pgi.91.2020.11.03.09.04.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 03 Nov 2020 09:04:31 -0800 (PST) Date: Wed, 4 Nov 2020 01:04:21 +0800 From: Gao Xiang To: Chao Yu Cc: Chao Yu , linux-erofs@lists.ozlabs.org, LKML , nl6720 , stable Subject: Re: [PATCH] erofs: derive atime instead of leaving it empty Message-ID: <20201103170421.GB886627@xiangao.remote.csb> References: <20201031195102.21221-1-hsiangkao.ref@aol.com> <20201031195102.21221-1-hsiangkao@aol.com> <20201103025033.GA788000@xiangao.remote.csb> <275b73d7-9865-91c0-ecf2-bceed09a4dae@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <275b73d7-9865-91c0-ecf2-bceed09a4dae@kernel.org> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Chao, On Tue, Nov 03, 2020 at 11:58:42PM +0800, Chao Yu wrote: > Hi Xiang, > > On 2020-11-3 10:50, Gao Xiang wrote: > > Hi Chao, > > > > On Sun, Nov 01, 2020 at 03:51:02AM +0800, Gao Xiang wrote: > > > From: Gao Xiang > > > > > > EROFS has _only one_ ondisk timestamp (ctime is currently > > > documented and recorded, we might also record mtime instead > > > with a new compat feature if needed) for each extended inode > > > since EROFS isn't mainly for archival purposes so no need to > > > keep all timestamps on disk especially for Android scenarios > > > due to security concerns. Also, romfs/cramfs don't have their > > > own on-disk timestamp, and squashfs only records mtime instead. > > > > > > Let's also derive access time from ondisk timestamp rather than > > > leaving it empty, and if mtime/atime for each file are really > > > needed for specific scenarios as well, we can also use xattrs > > > to record them then. > > > > > > Reported-by: nl6720 > > > [ Gao Xiang: It'd be better to backport for user-friendly concern. ] > > > Fixes: 431339ba9042 ("staging: erofs: add inode operations") > > > Cc: stable # 4.19+ > > > Signed-off-by: Gao Xiang > > > > May I ask for some extra free slots to review this patch plus > > [PATCH 1/4] of > > https://lore.kernel.org/r/20201022145724.27284-1-hsiangkao@aol.com > > > > since it'd be also in linux-next for a while before sending out > > to Linus. And the debugging messages may also be an annoying > > thing for users. > > Sorry for the delay review, will check the details tomorrow. :) No problem, thanks! If we'd like to submit a -fixes pull request, it'd be better not to be in the latter half of 5.10 rc... And considering that it'd be stayed in linux-next for almost a week, so yeah... (Only these 2 patches are considered for -fixes for now.) Thanks. Gao Xiang > > Thanks, > > > > > Thanks a lot! > > > > Thanks, > > Gao Xiang > > >