Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp1404989ybp; Thu, 17 Oct 2019 12:17:34 -0700 (PDT) X-Google-Smtp-Source: APXvYqyESF+cr0MFYnPjusIKtSoBAj/IVvkUwEHZC9meNlkGjNxgEbPrJHlIxDkD3ja0IZwXrLKA X-Received: by 2002:a17:906:4a97:: with SMTP id x23mr4944187eju.218.1571339854229; Thu, 17 Oct 2019 12:17:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571339854; cv=none; d=google.com; s=arc-20160816; b=Kvi3QUdVb/2Q6m5oboHwIUJ4H+GH3j2rR3iO/1C/X2MXbGOgyZ8ValNL+vLU0Q84z4 Iiz0/F+FEgfvHEm+ltgArxuEO5ampJTMKfW0aVrTwhK1BX4JDVrCr6cZ4tM5wwV8uvcx 5MyYD05NgZMCn0jS//GQEgavNcZ1qbVRel9d0AbO4ihK2ix8c4ejQrVlh7NzyT4jm56h y3HbUcV81vCSAcXsvI4GywBalV1RVXbJw9wfLM6lRG2qg+J4TWxIDHCcjsedJW7CCSmv JMzTQmY3mYEUdLORgjwlZMu117sUiYpQRwGyYPDKz18pc0ovt0Gb3ynTrLM3BeUXIkz+ agNA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=/Hk+iJLCSl6I7Y5entkfeg+vvho1zr5G+NCwuntzsW8=; b=Cckq/8fYlWIvTcNRkmXO27+8fIOVwMT5u9C6/h7KeYhjbHLwCSHDD2KLwfHJ2ZAB7e yiuHxZe/dXo/lyXMDbtHC1cQs/CpvOdXls78tJNSootcDGIOAYKaz3Gj5nuFYWwlY5Hq 49jPDzDf2Wb+Ph3hgHDXGIeze1XqqqMCz0XFXtyYLM0RaHTZCZryuh3A1hxXaflk6/3q 4mxlTEdnwekuB3i75OTIjYvSKH7bzQ9xTaoLN3TcFEcQXX8Kx25IPwWGGBTKyDTiUIFN yPwOEGToQIRFvSHVDlbWglyZHXN8nJZ5mdeWrRTGnh4xse73FCwLTtcumsN4eU+CcPoa C37Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=WqQ6y51k; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id x51si2301610eda.272.2019.10.17.12.16.56; Thu, 17 Oct 2019 12:17:34 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=WqQ6y51k; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 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 S2393384AbfJPWOq (ORCPT + 99 others); Wed, 16 Oct 2019 18:14:46 -0400 Received: from mail.kernel.org ([198.145.29.99]:38046 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389800AbfJPWOp (ORCPT ); Wed, 16 Oct 2019 18:14:45 -0400 Received: from sol.localdomain (c-24-5-143-220.hsd1.ca.comcast.net [24.5.143.220]) (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 CE46E21925; Wed, 16 Oct 2019 22:14:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1571264085; bh=Cvg2PFZHPVa4AAS2swiVhNcTA6EzxWj+yJWCIgQ3vDc=; h=From:To:Cc:Subject:Date:From; b=WqQ6y51kgOkzvCHAZ517xjc/L5E4NpggyFQsAe7uBBXuQEEX7aV+RJP7T2hs/TYjV d6hwQ8jKlqhlwom3K2oGy9TFgIu1IIf/XPjNAqCNHCAEatdDhAuMZiutZKFPnO9zPe WAfs6n7cBWOnfOflB4wfU1LpB4kbEglU5eO8Ifcw= From: Eric Biggers To: linux-ext4@vger.kernel.org Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org, Chandan Rajendra Subject: [PATCH 0/2] ext4: support encryption with blocksize != PAGE_SIZE Date: Wed, 16 Oct 2019 15:11:40 -0700 Message-Id: <20191016221142.298754-1-ebiggers@kernel.org> X-Mailer: git-send-email 2.23.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org Hello, This patchset makes ext4 support encryption on filesystems where the filesystem block size is not equal to PAGE_SIZE. This allows e.g. PowerPC systems to use ext4 encryption. Most of the work for this was already done in prior kernel releases; now the only part missing is decryption support in block_read_full_page(). Chandan Rajendra has proposed a patchset "Consolidate FS read I/O callbacks code" [1] to address this and do various other things like make ext4 use mpage_readpages() again, and make ext4 and f2fs share more code. But it doesn't seem to be going anywhere. Therefore, I propose we simply add decryption support to block_read_full_page() for now. This is a fairly small change, and it gets ext4 encryption with subpage-sized blocks working. Note: to keep things simple I'm just allocating the work object from the bi_end_io function with GFP_ATOMIC. But if people think it's necessary, it could be changed to use preallocation like the page-based read path. Tested with 'gce-xfstests -c ext4/encrypt_1k -g auto', using the new "encrypt_1k" config I created. All tests pass except for those that already fail or are excluded with the encrypt or 1k configs, and 2 tests that try to create 1023-byte symlinks which fails since encrypted symlinks are limited to blocksize-3 bytes. Also ran the dedicated encryption tests using 'kvm-xfstests -c ext4/1k -g encrypt'; all pass, including the on-disk ciphertext verification tests. [1] https://lkml.kernel.org/linux-fsdevel/20190910155115.28550-1-chandan@linux.ibm.com/T/#u Chandan Rajendra (1): ext4: Enable encryption for subpage-sized blocks Eric Biggers (1): fs/buffer.c: support fscrypt in block_read_full_page() Documentation/filesystems/fscrypt.rst | 4 +-- fs/buffer.c | 47 ++++++++++++++++++++++++--- fs/ext4/super.c | 7 ---- 3 files changed, 44 insertions(+), 14 deletions(-) -- 2.23.0