From: Daniel Vacek <neelx@suse.com>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: Daniel Vacek <neelx@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/7] btrfs: add fscrypt support, PART 1
Date: Tue, 18 Nov 2025 17:00:35 +0100 [thread overview]
Message-ID: <20251118160043.3005684-1-neelx@suse.com> (raw)
This is a revive of former work [1] of Omar, Sweet Tea and Josef to bring
native encryption support to btrfs.
It will come in more parts. The first part this time is splitting the simple
and isolated stuff out first to reduce the size of the final patchset.
Changes:
* v7 - Drop the checksum patch for now. It will make more sense later.
- Drop the btrfs/330 fix. It seems no longer needed after the years.
* v6 vs v5 [1] is mostly rebase to the latest for-next and cleaning up the
conflicts.
The remaining part needs further cleanup and a bit of redesign and it will
follow later.
[1] https://lore.kernel.org/linux-btrfs/cover.1706116485.git.josef@toxicpanda.com/
Josef Bacik (4):
btrfs: add orig_logical to btrfs_bio
btrfs: don't rewrite ret from inode_permission
btrfs: move inode_to_path higher in backref.c
btrfs: don't search back for dir inode item in INO_LOOKUP_USER
Omar Sandoval (1):
btrfs: disable various operations on encrypted inodes
Sweet Tea Dorminy (1):
btrfs: disable verity on encrypted inodes
fs/btrfs/backref.c | 68 +++++++++++++++++++++-----------------------
fs/btrfs/bio.c | 10 +++++++
fs/btrfs/bio.h | 2 ++
fs/btrfs/file-item.c | 2 +-
fs/btrfs/inode.c | 4 +++
fs/btrfs/ioctl.c | 27 +++---------------
fs/btrfs/reflink.c | 7 +++++
fs/btrfs/verity.c | 3 ++
8 files changed, 63 insertions(+), 60 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-18 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 16:00 Daniel Vacek [this message]
2025-11-18 16:00 ` [PATCH v7 1/6] btrfs: disable various operations on encrypted inodes Daniel Vacek
2025-11-18 16:00 ` [PATCH v7 2/6] btrfs: disable verity " Daniel Vacek
2025-11-18 16:00 ` [PATCH v7 3/6] btrfs: add orig_logical to btrfs_bio Daniel Vacek
2025-11-18 16:00 ` [PATCH v7 4/6] btrfs: don't rewrite ret from inode_permission Daniel Vacek
2025-11-18 16:00 ` [PATCH v7 5/6] btrfs: move inode_to_path higher in backref.c Daniel Vacek
2025-11-18 16:00 ` [PATCH v7 6/6] btrfs: don't search back for dir inode item in INO_LOOKUP_USER Daniel Vacek
2025-11-18 16:10 ` [PATCH v7 0/7] btrfs: add fscrypt support, PART 1 Daniel Vacek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251118160043.3005684-1-neelx@suse.com \
--to=neelx@suse.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox