From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: [PATCH 0/4] fsverity cleanups
Date: Wed, 14 Dec 2022 14:43:00 -0800 [thread overview]
Message-ID: <20221214224304.145712-1-ebiggers@kernel.org> (raw)
This series implements a few cleanups that have been suggested
in the thread "[RFC PATCH 00/11] fs-verity support for XFS"
(https://lore.kernel.org/linux-fsdevel/20221213172935.680971-1-aalbersh@redhat.com/T/#u).
This applies to mainline (commit 93761c93e9da).
Eric Biggers (4):
fsverity: optimize fsverity_file_open() on non-verity files
fsverity: optimize fsverity_prepare_setattr() on non-verity files
fsverity: optimize fsverity_cleanup_inode() on non-verity files
fsverity: pass pos and size to ->write_merkle_tree_block
fs/btrfs/verity.c | 19 ++++-------
fs/ext4/verity.c | 6 ++--
fs/f2fs/verity.c | 6 ++--
fs/verity/enable.c | 4 +--
fs/verity/open.c | 46 ++++---------------------
include/linux/fsverity.h | 74 +++++++++++++++++++++++++++++++++-------
6 files changed, 84 insertions(+), 71 deletions(-)
base-commit: 93761c93e9da28d8a020777cee2a84133082b477
--
2.38.1
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 0/4] fsverity cleanups
Date: Wed, 14 Dec 2022 14:43:00 -0800 [thread overview]
Message-ID: <20221214224304.145712-1-ebiggers@kernel.org> (raw)
This series implements a few cleanups that have been suggested
in the thread "[RFC PATCH 00/11] fs-verity support for XFS"
(https://lore.kernel.org/linux-fsdevel/20221213172935.680971-1-aalbersh@redhat.com/T/#u).
This applies to mainline (commit 93761c93e9da).
Eric Biggers (4):
fsverity: optimize fsverity_file_open() on non-verity files
fsverity: optimize fsverity_prepare_setattr() on non-verity files
fsverity: optimize fsverity_cleanup_inode() on non-verity files
fsverity: pass pos and size to ->write_merkle_tree_block
fs/btrfs/verity.c | 19 ++++-------
fs/ext4/verity.c | 6 ++--
fs/f2fs/verity.c | 6 ++--
fs/verity/enable.c | 4 +--
fs/verity/open.c | 46 ++++---------------------
include/linux/fsverity.h | 74 +++++++++++++++++++++++++++++++++-------
6 files changed, 84 insertions(+), 71 deletions(-)
base-commit: 93761c93e9da28d8a020777cee2a84133082b477
--
2.38.1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2022-12-14 22:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 22:43 Eric Biggers [this message]
2022-12-14 22:43 ` [f2fs-dev] [PATCH 0/4] fsverity cleanups Eric Biggers
2022-12-14 22:43 ` [PATCH 1/4] fsverity: optimize fsverity_file_open() on non-verity files Eric Biggers
2022-12-14 22:43 ` [f2fs-dev] " Eric Biggers
2022-12-14 22:43 ` [PATCH 2/4] fsverity: optimize fsverity_prepare_setattr() " Eric Biggers
2022-12-14 22:43 ` [f2fs-dev] " Eric Biggers
2022-12-14 22:43 ` [PATCH 3/4] fsverity: optimize fsverity_cleanup_inode() " Eric Biggers
2022-12-14 22:43 ` [f2fs-dev] " Eric Biggers
2022-12-14 22:43 ` [PATCH 4/4] fsverity: pass pos and size to ->write_merkle_tree_block Eric Biggers
2022-12-14 22:43 ` [f2fs-dev] " Eric Biggers
[not found] ` <20230125122227.lgwp2t5tdzten3dk@aalbersh.remote.csb>
2023-01-25 18:12 ` Eric Biggers
2023-01-25 18:12 ` [f2fs-dev] " Eric Biggers
2022-12-14 23:10 ` [PATCH 0/4] fsverity cleanups Dave Chinner
2022-12-14 23:10 ` [f2fs-dev] " Dave Chinner
2023-01-04 6:58 ` Eric Biggers
2023-01-04 6:58 ` [f2fs-dev] " Eric Biggers
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=20221214224304.145712-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.