From: Eric Biggers Subject: [PATCH 0/4] fscrypt: remove checks for encryption key after file open Date: Mon, 22 May 2017 17:39:41 -0700 Message-ID: <20170523003945.14279-1-ebiggers3@gmail.com> Cc: Theodore Ts'o , Jaegeuk Kim , linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-mtd@lists.infradead.org, Eric Biggers To: linux-fscrypt@vger.kernel.org Return-path: Received: from mail-pf0-f196.google.com ([209.85.192.196]:34775 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934067AbdEWAj6 (ORCPT ); Mon, 22 May 2017 20:39:58 -0400 Sender: linux-ext4-owner@vger.kernel.org List-ID: From: Eric Biggers This series removes checks for a regular file's encryption key that occur after we've already opened the file. We're guaranteed to already have the key in such places, since we require it in ->open(). open() fails with ENOKEY otherwise, and a file descriptor is never made available. This pertains to regular files only. (Directories can be opened with or without their key.) Eric Biggers (4): ext4: don't bother checking for encryption key in ->mmap() f2fs: don't bother checking for encryption key in ->mmap() ubifs: don't bother checking for encryption key in ->mmap() f2fs: don't bother checking for encryption key in ->write_iter() fs/ext4/file.c | 7 ------- fs/f2fs/file.c | 13 ------------- fs/ubifs/file.c | 9 --------- 3 files changed, 29 deletions(-) -- 2.13.0.303.g4ebf302169-goog