Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp884981pxb; Sat, 9 Jan 2021 00:03:24 -0800 (PST) X-Google-Smtp-Source: ABdhPJwmHPx2BuSjN1NZsNxmyAxh8p9b4KClav8Em8zVW/5zOIrmV5+mccHtagdGsSMc/n310nht X-Received: by 2002:aa7:cdc3:: with SMTP id h3mr7690504edw.52.1610179404459; Sat, 09 Jan 2021 00:03:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610179404; cv=none; d=google.com; s=arc-20160816; b=Ip0Vw8t8T1ZcbWK4IwkQoGcnGS4DqQ7gfv2dBC0q7LTZs5fzPN1xs+2AgTSt7Ls2I7 VYcbfx5WejrajCxD7via3v9Xc1ok0VN9Mkx2r8NUPZXYt6gL/A33lm9KjXuN4WqiWveM BFGhJeca+CypOKLasd3WWb7IFFGCwblNVXhmKrT2r+ydyOtT40XP9sI0kHYEo5GrHr+S Yy0o+1B7fQ0DT4sCuwdT+ZOlO6Z0PieCHwETt2J0DHa+DcxNeSVuanhekASdoFmwqAAL s090+eM4e9zLU1UURCQ3zsFC7nFCcu7XoYVApQU72N9YhzV+L+ENe2qv7NXLdU1nyTan H4qg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=xoqyv7NV8FwwlAvH5l9f/qFxRF/eqIG1Bk5JcBeq18E=; b=fKjZI5MZ3J8xZQDr2vya0yANWxKKeKOOlcYGFHscFPAtHKW+mW4jitwOpq6SwtHsYD Nn1xHKycZKzZAbErAE+dDW3aMfPY+JKvTKkav5Ier0rXC5/ovXJwVUNRtr2nSJsY27AZ w/ZUt9zVWfvzJlbtjbCvOSZ7izF8ZfQ49HYr1g2YdFdFwC5VlbaYqCXTvMd6U+d8LPwq PQYCHFOZtT8nsA061kqW8dA3AEmT/irC6QnqQS27Z6wmhKn5j9XhFczTpEgHR3WyWnXk Pb8U17bh+BkMBGMRFnfWUL7igUHKOSPjw49SwGbLusJWCKbNj74LdInK3mwwEXAHcXb+ oPxw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=PMaNkhAe; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b16si4368730ejc.710.2021.01.09.00.03.00; Sat, 09 Jan 2021 00:03:24 -0800 (PST) Received-SPF: pass (google.com: domain of linux-ext4-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=@kernel.org header.s=k20201202 header.b=PMaNkhAe; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726808AbhAIIBG (ORCPT + 99 others); Sat, 9 Jan 2021 03:01:06 -0500 Received: from mail.kernel.org ([198.145.29.99]:41212 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726756AbhAIIBF (ORCPT ); Sat, 9 Jan 2021 03:01:05 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id E5A1223A80; Sat, 9 Jan 2021 07:59:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1610179187; bh=JZSK51j63244IWBr+pzm3c0JJcjJt0lF7wGH5+JpZYw=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=PMaNkhAealymfact8bgjHAPCxzIqAPBXFz2sk2rT1PY2h8twYdFOtMlzmnN6BF4ng vBn5n9MVCN6+YGMYly6jUX/157BCpKFhUOrHAMKE63Ys4a/lQmiIf3NKgjzm8Lpuun GhhUVTP98jShQWS32w73aBSq1PuIVE+ARvUs1xwi/JKrV96zeOQQiC0rbT17hOCvz0 oFpi7M0HHdwIf7EP4ZI3ssh9zSd1Z7SPhjv1wQwVQbuAuMoSP6N7MvPLrVXf9yxtOj n/8fZ+K4IEicS8rbCpTXBQ/Xq/aIaTKvFIcSYjNiEnvrJTUrt06aievapr0LGUHts0 G4I2tZ/qcZCbA== From: Eric Biggers To: linux-fsdevel@vger.kernel.org Cc: linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, Theodore Ts'o , Christoph Hellwig Subject: [PATCH v2 10/12] gfs2: don't worry about I_DIRTY_TIME in gfs2_fsync() Date: Fri, 8 Jan 2021 23:59:01 -0800 Message-Id: <20210109075903.208222-11-ebiggers@kernel.org> X-Mailer: git-send-email 2.30.0 In-Reply-To: <20210109075903.208222-1-ebiggers@kernel.org> References: <20210109075903.208222-1-ebiggers@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org From: Eric Biggers The I_DIRTY_TIME flag is primary used within the VFS, and there's no reason for ->fsync() implementations to do anything with it. This is because when !datasync, the VFS will expire dirty timestamps before calling ->fsync(). (See vfs_fsync_range().) This turns I_DIRTY_TIME into I_DIRTY_SYNC. Therefore, change gfs2_fsync() to not check for I_DIRTY_TIME. Reviewed-by: Christoph Hellwig Signed-off-by: Eric Biggers --- fs/gfs2/file.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/gfs2/file.c b/fs/gfs2/file.c index b39b339feddc9..7fe2497755a37 100644 --- a/fs/gfs2/file.c +++ b/fs/gfs2/file.c @@ -749,7 +749,7 @@ static int gfs2_fsync(struct file *file, loff_t start, loff_t end, { struct address_space *mapping = file->f_mapping; struct inode *inode = mapping->host; - int sync_state = inode->i_state & I_DIRTY_ALL; + int sync_state = inode->i_state & I_DIRTY; struct gfs2_inode *ip = GFS2_I(inode); int ret = 0, ret1 = 0; @@ -762,7 +762,7 @@ static int gfs2_fsync(struct file *file, loff_t start, loff_t end, if (!gfs2_is_jdata(ip)) sync_state &= ~I_DIRTY_PAGES; if (datasync) - sync_state &= ~(I_DIRTY_SYNC | I_DIRTY_TIME); + sync_state &= ~I_DIRTY_SYNC; if (sync_state) { ret = sync_inode_metadata(inode, 1); -- 2.30.0