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 X-Spam-Level: X-Spam-Status: No, score=-10.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 291E1C433E1 for ; Thu, 2 Jul 2020 01:32:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 00CBB206BE for ; Thu, 2 Jul 2020 01:32:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1593653529; bh=MqbJuaMdE5G91py8qFrKcQTEIsoxFQOPbiruB5rMRaE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=Xah2ccuViLLYdTbv7yOSSloN0ubCIFez3102Lf5js8IoGQ9/BWE/D/T5ZoC4rjaWx 9mMOp+DsWSiao49fjv/N8bTfB63KHHSbUUAWzzcFtN1EEX+eH/LGp+SXrEUbreNc65 0fJXBwTpnJma+FxlXitppSDr0BN3ExfnaQ5jUZqg= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729165AbgGBB0Z (ORCPT ); Wed, 1 Jul 2020 21:26:25 -0400 Received: from mail.kernel.org ([198.145.29.99]:57270 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729056AbgGBB0F (ORCPT ); Wed, 1 Jul 2020 21:26:05 -0400 Received: from sasha-vm.mshome.net (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CF027206BE; Thu, 2 Jul 2020 01:26:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1593653164; bh=MqbJuaMdE5G91py8qFrKcQTEIsoxFQOPbiruB5rMRaE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=vAi/t1QkE9d3kFtbNHqALnSYQDpSbZEmKqRTD3WEBPjPd6Tt3USr3FjgpyUHF1XIp tGeTjPXmCXgQZiaJKkDkr3o125s69LkHUpyk4cD3S+n/iuvS97mK9yyt3U3OF+m6qq hmw2HLNtT3qFYXeC+pUNRP95WY+GEc9tFa3AQY40= From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Zhang Xiaoxu , Hulk Robot , Steve French , Sasha Levin , linux-cifs@vger.kernel.org, samba-technical@lists.samba.org Subject: [PATCH AUTOSEL 5.4 32/40] cifs: update ctime and mtime during truncate Date: Wed, 1 Jul 2020 21:23:53 -0400 Message-Id: <20200702012402.2701121-32-sashal@kernel.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20200702012402.2701121-1-sashal@kernel.org> References: <20200702012402.2701121-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Zhang Xiaoxu [ Upstream commit 5618303d8516f8ac5ecfe53ee8e8bc9a40eaf066 ] As the man description of the truncate, if the size changed, then the st_ctime and st_mtime fields should be updated. But in cifs, we doesn't do it. It lead the xfstests generic/313 failed. So, add the ATTR_MTIME|ATTR_CTIME flags on attrs when change the file size Reported-by: Hulk Robot Signed-off-by: Zhang Xiaoxu Signed-off-by: Steve French Signed-off-by: Sasha Levin --- fs/cifs/inode.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/fs/cifs/inode.c b/fs/cifs/inode.c index 5e6bc8fa4e461..eb2e3db3916f0 100644 --- a/fs/cifs/inode.c +++ b/fs/cifs/inode.c @@ -2264,6 +2264,15 @@ cifs_set_file_size(struct inode *inode, struct iattr *attrs, if (rc == 0) { cifsInode->server_eof = attrs->ia_size; cifs_setsize(inode, attrs->ia_size); + + /* + * The man page of truncate says if the size changed, + * then the st_ctime and st_mtime fields for the file + * are updated. + */ + attrs->ia_ctime = attrs->ia_mtime = current_time(inode); + attrs->ia_valid |= ATTR_CTIME | ATTR_MTIME; + cifs_truncate_page(inode->i_mapping, inode->i_size); } -- 2.25.1