From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CEE7DC001B0 for ; Wed, 9 Aug 2023 14:44:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-ID:Date:References :In-Reply-To:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=zlJUB59kCQHEiCxB0kTI4/9xwsW7qVQmZbd4mI7ouRo=; b=11VF/Bvi3Hs9um fzbQPzw/PKkutQR/emQuQbvCfZWv9mGbRr0GFGfq9MqjW+uSxAC+Lfmx+I0OggzlpWuIqDHvaRtd8 F28df2tGzavSiTD86cRb7jTjWM0BZx/fLGOLyzOQdhDQ+ODAlS9GoxCuYNp13ol47ilVKW6FkXphK RNl5sQo8l5uPjiO3wWuWj8BQ/kr0+G6CYIUHlYBVGUFkL69gk0QRZiXxlvkc4LYfkaNCnuViiYBn4 pmQLQohRVVPLFJkR7o7dZ1IyySH0AOezd37wZgBfe3ED7TA3LzBfvJdJiKQ2MukdwPnLJ/lbfl9bs g63tgIDXAljtA8L3HL2A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qTkQT-005DAC-2h; Wed, 09 Aug 2023 14:44:41 +0000 Received: from mail.parknet.co.jp ([210.171.160.6]) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qTkQQ-005D72-2C; Wed, 09 Aug 2023 14:44:40 +0000 Received: from ibmpc.myhome.or.jp (server.parknet.ne.jp [210.171.168.39]) by mail.parknet.co.jp (Postfix) with ESMTPSA id 593222055FA0; Wed, 9 Aug 2023 23:44:33 +0900 (JST) Received: from devron.myhome.or.jp (foobar@devron.myhome.or.jp [192.168.0.3]) by ibmpc.myhome.or.jp (8.17.2/8.17.2/Debian-1) with ESMTPS id 379EiWdd218003 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Wed, 9 Aug 2023 23:44:33 +0900 Received: from devron.myhome.or.jp (foobar@localhost [127.0.0.1]) by devron.myhome.or.jp (8.17.2/8.17.2/Debian-1) with ESMTPS id 379EiV6k197737 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Wed, 9 Aug 2023 23:44:31 +0900 Received: (from hirofumi@localhost) by devron.myhome.or.jp (8.17.2/8.17.2/Submit) id 379EiQ5o197730; Wed, 9 Aug 2023 23:44:26 +0900 From: OGAWA Hirofumi To: Jeff Layton Cc: Alexander Viro , Christian Brauner , Eric Van Hensbergen , Latchesar Ionkov , Dominique Martinet , Christian Schoenebeck , David Howells , Marc Dionne , Chris Mason , Josef Bacik , David Sterba , Xiubo Li , Ilya Dryomov , Jan Harkes , coda@cs.cmu.edu, Tyler Hicks , Gao Xiang , Chao Yu , Yue Hu , Jeffle Xu , Namjae Jeon , Sungjong Seo , Jan Kara , "Theodore Ts'o" , Andreas Dilger , Jaegeuk Kim , Miklos Szeredi , Bob Peterson , Andreas Gruenbacher , Greg Kroah-Hartman , Tejun Heo , Trond Myklebust , Anna Schumaker , Konstantin Komarov , Mark Fasheh , Joel Becker , Joseph Qi , Mike Marshall , Martin Brandenburg , Luis Chamberlain , Kees Cook , Iurii Zaikin , Steve French , Paulo Alcantara , Ronnie Sahlberg , Shyam Prasad N , Tom Talpey , Sergey Senozhatsky , Richard Weinberger , Hans de Goede , Hugh Dickins , Andrew Morton , Amir Goldstein , "Darrick J. Wong" , Benjamin Coddington , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, v9fs@lists.linux.dev, linux-afs@lists.infradead.org, linux-btrfs@vger.kernel.org, ceph-devel@vger.kernel.org, codalist@telemann.coda.cs.cmu.edu, ecryptfs@vger.kernel.org, linux-erofs@lists.ozlabs.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, cluster-devel@redhat.com, linux-nfs@vger.kernel.org, ntfs3@lists.linux.dev, ocfs2-devel@lists.linux.dev, devel@lists.orangefs.org, linux-cifs@vger.kernel.org, samba-technical@lists.samba.org, linux-mtd@lists.infradead.org, linux-mm@kvack.org, linux-unionfs@vger.kernel.org, linux-xfs@vger.kernel.org Subject: Re: [PATCH v7 05/13] fat: make fat_update_time get its own timestamp In-Reply-To: <7edc9239f73022b9c2a1d3f4f946153f85f94739.camel@kernel.org> (Jeff Layton's message of "Wed, 09 Aug 2023 10:22:54 -0400") References: <20230807-mgctime-v7-0-d1dec143a704@kernel.org> <20230807-mgctime-v7-5-d1dec143a704@kernel.org> <87msz08vc7.fsf@mail.parknet.co.jp> <52bead1d6a33fec89944b96e2ec20d1ea8747a9a.camel@kernel.org> <878rak8hia.fsf@mail.parknet.co.jp> <7edc9239f73022b9c2a1d3f4f946153f85f94739.camel@kernel.org> Date: Wed, 09 Aug 2023 23:44:26 +0900 Message-ID: <874jl88ed1.fsf@mail.parknet.co.jp> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230809_074438_924515_9026481D X-CRM114-Status: GOOD ( 28.35 ) X-BeenThere: linux-mtd@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-mtd" Errors-To: linux-mtd-bounces+linux-mtd=archiver.kernel.org@lists.infradead.org Jeff Layton writes: > I'm a little confused too. Why do you believe this will break > -o relatime handling? This patch changes two things: > > 1/ it has fat_update_time fetch its own timestamp (and ignore the "now" > parameter). This is in line with the changes in patch #3 of this series, > which explains the rationale for this in more detail. > > 2/ it changes fat_update_time to also update the i_version if any of > S_CTIME|S_MTIME|S_VERSION are set. relatime is all about the S_ATIME, > and it is specifically excluded from that set. > > The rationale for the second change is is also in patch #3, but > basically, we can't guarantee that current_time hasn't changed since we > last checked for inode_needs_update_time, so if any of > S_CTIME/S_MTIME/S_VERSION have changed, then we need to assume that any > of them may need to be changed and attempt to update all 3. > > That said, I think the logic in fat_update_time isn't quite right. I > think want something like this on top of this patch to ensure that the > S_CTIME and S_MTIME get updated, even if the flags only have S_VERSION > set. > > Thoughts? I'm not talking about "relatime" at all, I'm always talking about "lazytime". I_DIRTY_TIME delays to update on disk inode only if changed timestamp. But you changed it to I_DIRTY_SYNC, i.e. always update on disk inode by timestamp. Thanks. > ---------------------8<----------------------- > > diff --git a/fs/fat/misc.c b/fs/fat/misc.c > index 080a5035483f..313eef02f45c 100644 > --- a/fs/fat/misc.c > +++ b/fs/fat/misc.c > @@ -346,15 +346,21 @@ int fat_update_time(struct inode *inode, int flags) > if (inode->i_ino == MSDOS_ROOT_INO) > return 0; > > - if (flags & (S_ATIME | S_CTIME | S_MTIME)) { > - fat_truncate_time(inode, NULL, flags); > - if (inode->i_sb->s_flags & SB_LAZYTIME) > - dirty_flags |= I_DIRTY_TIME; > - else > - dirty_flags |= I_DIRTY_SYNC; > - } > + /* > + * If any of the flags indicate an expicit change to the file, then we > + * need to ensure that we attempt to update all of 3. We do not do > + * this in the case of an S_ATIME-only update. > + */ > + if (flags & (S_CTIME | S_MTIME | S_VERSION)) > + flags |= S_CTIME | S_MTIME | S_VERSION; > + > + fat_truncate_time(inode, NULL, flags); > + if (inode->i_sb->s_flags & SB_LAZYTIME) > + dirty_flags |= I_DIRTY_TIME; > + else > + dirty_flags |= I_DIRTY_SYNC; > > - if ((flags & (S_VERSION|S_CTIME|S_MTIME)) && inode_maybe_inc_iversion(inode, false)) > + if ((flags & S_VERSION) && inode_maybe_inc_iversion(inode, false)) > dirty_flags |= I_DIRTY_SYNC; > -- OGAWA Hirofumi ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/