Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1413045pxk; Sun, 13 Sep 2020 01:38:57 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwuQebaGSN+IxeznE+5nsM2Ok8BfDUQ83V4FUuydJwRGTlg03zZYEBW0Src39yrBmngmqDU X-Received: by 2002:a17:906:4046:: with SMTP id y6mr9857620ejj.148.1599986337258; Sun, 13 Sep 2020 01:38:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599986337; cv=none; d=google.com; s=arc-20160816; b=uyMf8PZPR1Ri0w1w+6BUdVaVE3uRDT8P4zDnpEaTSBO4dy91Rszy/9VKe31Tyjuyci EanV5Oi/nV/3ttTusKL+XBSB9tMoAMAVyOE4yLuPKAXNcvOTfax67IGnK0kRKOzWOZo+ sz+qBQ4CdYFlr4BfChs+ipYS/jQFaPelHS5dGDalIJ8H7Zm+pHDGCgQDYIQXP956MMqJ lo7VcomOtX5it2dEz5+S7LjCt2eKKKOKqYe1eCCzQBUC+WH6mD67YfOgF72tlb8Sl6k4 1QTJJq7lpy6Yc7dfu0Vav/kpmd36HFmmwL4qnJDdA5iQZBslg3EHVRYJZ3f25V4LeX8k h4WA== 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=JOBuLpP6IEEa2DHqiURsxve3xc4icKz1GYHTKwuxscE=; b=LEF5NA/rWh+T2REFeYeB+FGKA2ogNNRAuu77TqsOxTeu1nyEbbajwCwx+B2KWP63bB sfA0FO9dzh/pTM8JJpC0SQroTgyG4/wbQsKQ0GCv/4inSYqa3WzDTW73OJUpAfo4vhRO T2LHm//VCHke34GBt5KS9TMp0XSSx4P2AqY5AF3QiOEgegJ+E2eWIjQVozAMHRdUog06 CYaLvl3LL0mEkeSRxsUlQmupR3/NJjLaIwFPvubb0K1d4uMMtSokT1+XjPNnJrN1K1Sy yOY6FVGhEQg2jQ66ZhfF7sLU0mk6rnd/nPt38vwOBfNSbE4hskG0NGovqNJwh1wro5+b UGMA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ipJmfRdP; 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 p2si4744802ejw.176.2020.09.13.01.38.27; Sun, 13 Sep 2020 01:38:57 -0700 (PDT) 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=ipJmfRdP; 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 S1725975AbgIMIiF (ORCPT + 99 others); Sun, 13 Sep 2020 04:38:05 -0400 Received: from mail.kernel.org ([198.145.29.99]:60726 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725944AbgIMIiA (ORCPT ); Sun, 13 Sep 2020 04:38:00 -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 9F603207C3; Sun, 13 Sep 2020 08:37:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1599986277; bh=1dWd0eaN+m2UtgMk0cP4qKXLdHH/WAl+lzlyqYHMukk=; h=From:To:Cc:Subject:Date:From; b=ipJmfRdPkFyhu56cjRGr0ZeqiutvWztlif5XXFufzYsh3cnphGpzhFj2St50YuRzV UEc86raNPAcu7mQKxuK5RikeZDuMTvQ05Qd714yLvl9T7hh+qV9FTm54tRi7DnLjpa b5bXy5JjPybx7ZRKtencxAsn2Ls25CJ+ro5fI+7A= From: Eric Biggers To: linux-fscrypt@vger.kernel.org Cc: linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-mtd@lists.infradead.org, ceph-devel@vger.kernel.org, Jeff Layton , Daniel Rosenberg Subject: [PATCH v2 00/11] fscrypt: improve file creation flow Date: Sun, 13 Sep 2020 01:36:09 -0700 Message-Id: <20200913083620.170627-1-ebiggers@kernel.org> X-Mailer: git-send-email 2.28.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 series reworks the implementation of creating new encrypted files by introducing new helper functions that allow filesystems to set up the inodes' keys earlier, prior to taking too many filesystem locks. This fixes deadlocks that are possible during memory reclaim because fscrypt_get_encryption_info() isn't GFP_NOFS-safe, yet it's called during an ext4 transaction or under f2fs_lock_op(). It also fixes a similar deadlock where f2fs can try to recursively lock a page when the test_dummy_encryption mount option is in use. It also solves an ordering problem that the ceph support for fscrypt will have. For more details about this ordering problem, see the discussion on Jeff Layton's RFC patchsets for ceph fscrypt support (v1: https://lkml.kernel.org/linux-fscrypt/20200821182813.52570-1-jlayton@kernel.org/T/#u v2: https://lkml.kernel.org/linux-fscrypt/20200904160537.76663-1-jlayton@kernel.org/T/#u). Note that v2 of the ceph patchset is based on v1 of this patchset. Patch 1 adds the above-mentioned new helper functions. Patches 2-5 convert ext4, f2fs, and ubifs to use them, and patches 6-8 clean up a few things afterwards. Finally, patches 9-11 change the implementation of test_dummy_encryption to no longer set up an encryption key for unencrypted directories, which was confusing and was causing problems. This patchset applies to the master branch of https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git. It can also be retrieved from tag "fscrypt-file-creation-v2" of https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git. I'm looking to apply this for 5.10; reviews are greatly appreciated! Changed v1 => v2: - Added mention of another deadlock this fixes. - Added patches to improve the test_dummy_encryption implementation. - Dropped an ext4 cleanup patch that can be done separately later. - Lots of small cleanups, and a couple small fixes. Eric Biggers (11): fscrypt: add fscrypt_prepare_new_inode() and fscrypt_set_context() ext4: factor out ext4_xattr_credits_for_new_inode() ext4: use fscrypt_prepare_new_inode() and fscrypt_set_context() f2fs: use fscrypt_prepare_new_inode() and fscrypt_set_context() ubifs: use fscrypt_prepare_new_inode() and fscrypt_set_context() fscrypt: remove fscrypt_inherit_context() fscrypt: require that fscrypt_encrypt_symlink() already has key fscrypt: stop pretending that key setup is nofs-safe fscrypt: make "#define fscrypt_policy" user-only fscrypt: move fscrypt_prepare_symlink() out-of-line fscrypt: handle test_dummy_encryption in more logical way fs/crypto/fname.c | 11 ++- fs/crypto/fscrypt_private.h | 10 +- fs/crypto/hooks.c | 65 +++++++++---- fs/crypto/inline_crypt.c | 7 +- fs/crypto/keysetup.c | 163 +++++++++++++++++++++++-------- fs/crypto/keysetup_v1.c | 8 +- fs/crypto/policy.c | 180 +++++++++++++++++++++-------------- fs/ext4/ext4.h | 6 +- fs/ext4/ialloc.c | 119 ++++++++++++----------- fs/ext4/super.c | 17 ++-- fs/f2fs/dir.c | 2 +- fs/f2fs/f2fs.h | 25 +---- fs/f2fs/namei.c | 7 +- fs/f2fs/super.c | 16 ++-- fs/ubifs/dir.c | 38 ++++---- include/linux/fscrypt.h | 121 ++++++++--------------- include/uapi/linux/fscrypt.h | 6 +- 17 files changed, 446 insertions(+), 355 deletions(-) -- 2.28.0