From patchwork Wed Jul 5 19:00:30 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jeff Layton X-Patchwork-Id: 699349 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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id ABA03C001B0 for ; Wed, 5 Jul 2023 19:03:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233406AbjGETDT (ORCPT ); Wed, 5 Jul 2023 15:03:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42876 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233333AbjGETDS (ORCPT ); Wed, 5 Jul 2023 15:03:18 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2F6341730; Wed, 5 Jul 2023 12:03:15 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id B5149616C4; Wed, 5 Jul 2023 19:03:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 623D6C433C7; Wed, 5 Jul 2023 19:03:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1688583794; bh=kM0aleIbcnRzUxbHQknvyJkwiNG9CJKpnUbOghkokco=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=phaRUhycINZtI8zYHg2fG+4V1LUiUO/5B9eREQVACAzMMyozSUi/ITEr6/5RK7bsR iz7VqtRyVBoSBmASgtj/FnMd27l66LZTn80QtUDRsBzil07NF6x7PGdMR8LyBlxUPZ opM56Z0PcwVH5XjNxm2R/QgwYZEuIUE1VBns+KCJ7wKFUz9phIWV2LI4vrEKu1OJ5n Eww0q6XNhtkREiEuJHMjdtbc7WAyXu8ftTasC7vEfj1Gz/0oK+tCMYh98ztMflFc6m lS0QrRTSmiv3w4N+JNZXRaXgcQOX/lWJlc3E0uJzhvYwyQwFaiW7eK0iXEQJNbpj9z 35fi6aJ+Q580w== From: Jeff Layton To: Christian Brauner , Jeremy Kerr , Ard Biesheuvel Cc: Al Viro , Jan Kara , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org Subject: [PATCH v2 03/92] efivarfs: update ctime when mtime changes on a write Date: Wed, 5 Jul 2023 15:00:30 -0400 Message-ID: <20230705190309.579783-3-jlayton@kernel.org> X-Mailer: git-send-email 2.41.0 In-Reply-To: <20230705190309.579783-1-jlayton@kernel.org> References: <20230705185755.579053-1-jlayton@kernel.org> <20230705190309.579783-1-jlayton@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-efi@vger.kernel.org POSIX says: "Upon successful completion, where nbyte is greater than 0, write() shall mark for update the last data modification and last file status change timestamps of the file..." Add the missing ctime update. Signed-off-by: Jeff Layton --- fs/efivarfs/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/efivarfs/file.c b/fs/efivarfs/file.c index d57ee15874f9..375576111dc3 100644 --- a/fs/efivarfs/file.c +++ b/fs/efivarfs/file.c @@ -51,7 +51,7 @@ static ssize_t efivarfs_file_write(struct file *file, } else { inode_lock(inode); i_size_write(inode, datasize + sizeof(attributes)); - inode->i_mtime = current_time(inode); + inode->i_mtime = inode->i_ctime = current_time(inode); inode_unlock(inode); }