Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp60992ybx; Tue, 5 Nov 2019 19:30:12 -0800 (PST) X-Google-Smtp-Source: APXvYqyGksQoGuQ3PFgQN7affqgrp+TF49sZWrBNNe0/n1qAroEffaN25D4xa36+RH1PCtbJteUO X-Received: by 2002:a17:906:66d2:: with SMTP id k18mr32332842ejp.278.1573011012385; Tue, 05 Nov 2019 19:30:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573011012; cv=none; d=google.com; s=arc-20160816; b=Wl7cfjiJAVB6tEf8JqyjipRxRjEigWNLStug4WByzKzHlMET9bC9bsBjFikRNI/hob NWu7/lUFCnJtkUADaqmm2XD6prk4yL/MCn+qgMytxU1r+QfCnD3uzzMjiN7RVorAvvqI U1ahsc8B+N2sYqMYgpkLYbwqdLnl0S63CxycNeuDfnR31ePdHrI7ElxItQc6DVBk8M+U wtIiuWSSYTdG5KXKj2k84odmoI9fBLF1heQjntw2VoRehHjIOkpf6IIluOhuYlI3FSu0 OOeTzldB6WOaR6Nlk5U/Pb+KSnNs2nfqaPa+DzXFI4TntdP/Gmdjmn/HI+GsgZJ1n4Z7 QdcA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=eXbTkeLLTPq/is4OmaGJiGnD1qywzbvGYR1C77mghk8=; b=xB6f9iQjdugbf7obmwb/Bb5zKzAb4TXx4qo0CeS9/jKMEwAa/k2MSYFtWeWk+HwXX9 qLK2QkWlnisfLvmYRGWZyx569Y8eaMjLyqW08DBjj6GbWyYt1dww/949ceBRkAUOhwnV M0mf9WGv7zMo9+7DxBZWbR1iWEpEeyGIW38ZaW8qvUd4JxwjKt18BcCC2wAJzM9Th53R VW/gFD6kSr31n0IBk8vxyEgEmfERtsoY/O/ItLm/Y6lItgVs29ZAWkbnCu9J0Ghs7FRA 3CosumGHf9zWg0weyeIFE7B/7lgthrol6+/Be8HHHcZ5GOlH0te7eWY3KsfluiNocUbI HiOA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n14si4493512ejy.134.2019.11.05.19.29.40; Tue, 05 Nov 2019 19:30:12 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730939AbfKFD0l (ORCPT + 99 others); Tue, 5 Nov 2019 22:26:41 -0500 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:57284 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730655AbfKFD0l (ORCPT ); Tue, 5 Nov 2019 22:26:41 -0500 Received: from callcc.thunk.org (ip-12-2-52-196.nyc.us.northamericancoax.com [196.52.2.12]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id xA63QMGp027897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 5 Nov 2019 22:26:23 -0500 Received: by callcc.thunk.org (Postfix, from userid 15806) id 4AC21420311; Tue, 5 Nov 2019 22:26:20 -0500 (EST) Date: Tue, 5 Nov 2019 22:26:20 -0500 From: "Theodore Y. Ts'o" To: Eric Biggers Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org, Satya Tangirala , Paul Crowley , Paul Lawrence , Jaegeuk Kim Subject: Re: [PATCH v2 2/3] ext4: add support for IV_INO_LBLK_64 encryption policies Message-ID: <20191106032620.GF26959@mit.edu> References: <20191024215438.138489-1-ebiggers@kernel.org> <20191024215438.138489-3-ebiggers@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191024215438.138489-3-ebiggers@kernel.org> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Thu, Oct 24, 2019 at 02:54:37PM -0700, Eric Biggers wrote: > From: Eric Biggers > > IV_INO_LBLK_64 encryption policies have special requirements from the > filesystem beyond those of the existing encryption policies: > > - Inode numbers must never change, even if the filesystem is resized. > - Inode numbers must be <= 32 bits. > - File logical block numbers must be <= 32 bits. > > ext4 has 32-bit inode and file logical block numbers. However, > resize2fs can re-number inodes when shrinking an ext4 filesystem. > > However, typically the people who would want to use this format don't > care about filesystem shrinking. They'd be fine with a solution that > just prevents the filesystem from being shrunk. > > Therefore, add a new feature flag EXT4_FEATURE_COMPAT_STABLE_INODES that > will do exactly that. Then wire up the fscrypt_operations to expose > this flag to fs/crypto/, so that it allows IV_INO_LBLK_64 policies when > this flag is set. > > Signed-off-by: Eric Biggers LGTM Acked-by: Theodore Ts'o - Ted