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=-8.3 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_GIT autolearn=unavailable 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 789CFC4727D for ; Thu, 24 Sep 2020 04:29:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1519323899 for ; Thu, 24 Sep 2020 04:29:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1600921742; bh=rO/bNcZHwLT9QTBkuyjZ4ahgv+SZFROlqsq/52bymt0=; h=From:To:Cc:Subject:Date:List-ID:From; b=t9ryqNPKQJ9NPqSFZGIpKim4j0/l5rMUlEAShLUX+PX0LYEURDFZ6+BNOQH5jvRC8 75BP2KXTY0o13A8hkOvIiuqdoQzbjAcJa3pruwDm8eJ2n70PuqY17Te7LlTblnVYdt f6UI+dVjHGf656i9GLQF7oLNOx4rp2zMm0OO5BNc= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726683AbgIXE3B (ORCPT ); Thu, 24 Sep 2020 00:29:01 -0400 Received: from mail.kernel.org ([198.145.29.99]:48564 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726466AbgIXE3B (ORCPT ); Thu, 24 Sep 2020 00:29:01 -0400 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 C260E20888; Thu, 24 Sep 2020 04:29:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1600921741; bh=rO/bNcZHwLT9QTBkuyjZ4ahgv+SZFROlqsq/52bymt0=; h=From:To:Cc:Subject:Date:From; b=Rs5Fnpx1+kMOIPp6FrLcwizUYAmnr1trqn6z58T4WhfCNzSfjwSkIuvmrCLNNKuYV h83JFF9l8jBLk1oFYxyaFvH/LUHYjCSMon4nXUxTY7K8bQM01kFjKU3t49ioWLBDsM ZJzba7PzU5Ino48o+muguuzoP2FYvRDOSDaHNrdQ= From: Eric Biggers To: linux-fscrypt@vger.kernel.org Cc: linux-fsdevel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, Daniel Rosenberg , Jeff Layton Subject: [PATCH 0/2] fscrypt: avoid ambiguous terms for "no-key name" Date: Wed, 23 Sep 2020 21:26:22 -0700 Message-Id: <20200924042624.98439-1-ebiggers@kernel.org> X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org This series fixes overloading of the terms "ciphertext name" and "encrypted name" to also sometimes mean "no-key name". The overloading of these terms has caused some confusion. No change in behavior. Eric Biggers (2): fscrypt: don't call no-key names "ciphertext names" fscrypt: rename DCACHE_ENCRYPTED_NAME to DCACHE_NOKEY_NAME fs/crypto/fname.c | 16 ++++++++-------- fs/crypto/hooks.c | 13 ++++++------- fs/f2fs/dir.c | 2 +- include/linux/dcache.h | 2 +- include/linux/fscrypt.h | 25 ++++++++++++------------- 5 files changed, 28 insertions(+), 30 deletions(-) -- 2.28.0