Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp6913pxb; Tue, 10 Nov 2020 17:53:42 -0800 (PST) X-Google-Smtp-Source: ABdhPJzrFcXI8y0eoItu08vNnyH9RRV5F34AebYI6X61U4Qy6nKOtSgsez4HuS/iUEij3sDNFhS9 X-Received: by 2002:a05:6402:22ab:: with SMTP id cx11mr2401884edb.98.1605059622350; Tue, 10 Nov 2020 17:53:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605059622; cv=none; d=google.com; s=arc-20160816; b=VBKBYyPy6IXeHZuO/M4y0oIWbebrgIWbVMcRmjrXjgw2vHMjrMG+g/8q5b2WyFBrkh eYDK6DHCHYK21vA8IIn5UHSqe/6xfLeA6b7gle8GuE0RjesG6TcpCBfG0bzJDcR9cykv l/cUudiJR09Pl3IwrqP5tm7ByQfE8LK16R6u+zb4nN74Gl9S1iKVbQH8ttEit/CuudlB xEy+LyIU0qHm8JugrpRLusimjKGdFMP0PfL6gwbU1hMvEbmIzNr1oALpuJ60PuOTJDi4 wlGwWHTqPM8Ae02h9XNH8OF78S3OWYzEkxJ3jD69WensjDo/RHjTyc+EUTIQEAwzU4YG ii0w== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=NDEuXEVbtFDkpOxMeI5pFl6hVBMn27GMTDAWO61+/XE=; b=At2UwL0S8TbMNmaHGN3jt1dDhqfEMIZniMutIvpvQT53mZlDi3z0pVSJ/Hh0H7EzM5 HF8lTQfPq24Z3I8eXl+bb/llEMBgG7BjJta5AgnY0KIxkqDBnpKqNO7NtVvWhxoPgPkw 0lH3+SQNtVo+gVWF4Q6SjjlbexgmPbrepQq1s4GAdrN3k7HhkbGrdfRhDO229RuuPvAm AWIGh5VH2NFXRNPx+67ipIO6H/12zsQCv56pTSAWcdz7qcvqREz8pkYtQ2JZiseCF0NR eE0MuYvIVw9uWRCVvDGFqdizS4dZOZXewa7RfI1nYVe7Aa6f8BunVwHOJfOcMI+tpb5M vjUA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=U5Fjvl1q; 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 x9si306398ejc.745.2020.11.10.17.52.58; Tue, 10 Nov 2020 17:53:42 -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=default header.b=U5Fjvl1q; 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 S1731657AbgKKBwv (ORCPT + 99 others); Tue, 10 Nov 2020 20:52:51 -0500 Received: from mail.kernel.org ([198.145.29.99]:37720 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731610AbgKKBwu (ORCPT ); Tue, 10 Nov 2020 20:52:50 -0500 Received: from sol.attlocal.net (172-10-235-113.lightspeed.sntcca.sbcglobal.net [172.10.235.113]) (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 71F5C216C4; Wed, 11 Nov 2020 01:52:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1605059569; bh=TJ6ir93AFmz8PfLOms2XdxoiadqyHjUx+rfVbMNTzUg=; h=From:To:Cc:Subject:Date:From; b=U5Fjvl1qn+Nyza7ZGY4YG9S3NiLz86CYAekL3oJLA/+AcX9S0hMtr6khHYNtvAmyk x8L1xNfrOXDdvfQ+DccFHc8oppV3MsudwyKw8sTO198OFmKHpnm+kQZrMmR4F3UYXQ 1zzRTIcpp1B6bdwhUGdyzSpcJ2bBVqRwgqulc5To= From: Eric Biggers To: linux-fscrypt@vger.kernel.org Cc: linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, Satya Tangirala , Jaegeuk Kim Subject: [PATCH] fscrypt: fix inline encryption not used on new files Date: Tue, 10 Nov 2020 17:52:24 -0800 Message-Id: <20201111015224.303073-1-ebiggers@kernel.org> X-Mailer: git-send-email 2.29.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org From: Eric Biggers The new helper function fscrypt_prepare_new_inode() runs before S_ENCRYPTED has been set on the new inode. This accidentally made fscrypt_select_encryption_impl() never enable inline encryption on newly created files, due to its use of fscrypt_needs_contents_encryption() which only returns true when S_ENCRYPTED is set. Fix this by using S_ISREG() directly instead of fscrypt_needs_contents_encryption(), analogous to what select_encryption_mode() does. I didn't notice this earlier because by design, the user-visible behavior is the same (other than performance, potentially) regardless of whether inline encryption is used or not. Fixes: a992b20cd4ee ("fscrypt: add fscrypt_prepare_new_inode() and fscrypt_set_context()") Signed-off-by: Eric Biggers --- fs/crypto/inline_crypt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/crypto/inline_crypt.c b/fs/crypto/inline_crypt.c index 89bffa82ed74a..c57bebfa48fea 100644 --- a/fs/crypto/inline_crypt.c +++ b/fs/crypto/inline_crypt.c @@ -74,7 +74,7 @@ int fscrypt_select_encryption_impl(struct fscrypt_info *ci) int i; /* The file must need contents encryption, not filenames encryption */ - if (!fscrypt_needs_contents_encryption(inode)) + if (!S_ISREG(inode->i_mode)) return 0; /* The crypto mode must have a blk-crypto counterpart */ base-commit: 92cfcd030e4b1de11a6b1edb0840e55c26332d31 -- 2.29.2