From: Eric Biggers <ebiggers@kernel.org>
To: fsverity@lists.linux.dev
Cc: linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] fsverity: simplify initcall and move sysctl registration
Date: Wed, 5 Jul 2023 14:27:41 -0700 [thread overview]
Message-ID: <20230705212743.42180-1-ebiggers@kernel.org> (raw)
This series simplifies handling of errors during the fsverity_init()
initcall, and moves the sysctl registration out of signature.c so that
it is not unnecessarily tied to the builtin signature feature.
Eric Biggers (2):
fsverity: simplify handling of errors during initcall
fsverity: move sysctl registration out of signature.c
fs/verity/fsverity_private.h | 12 +++----
fs/verity/init.c | 56 ++++++++++++++++++++-------------
fs/verity/open.c | 18 +++--------
fs/verity/signature.c | 61 +++++-------------------------------
fs/verity/verify.c | 11 ++-----
5 files changed, 55 insertions(+), 103 deletions(-)
base-commit: ace1ba1c9038b30f29c5759bc4726bbed7748f15
--
2.41.0
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: fsverity@lists.linux.dev
Cc: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 0/2] fsverity: simplify initcall and move sysctl registration
Date: Wed, 5 Jul 2023 14:27:41 -0700 [thread overview]
Message-ID: <20230705212743.42180-1-ebiggers@kernel.org> (raw)
This series simplifies handling of errors during the fsverity_init()
initcall, and moves the sysctl registration out of signature.c so that
it is not unnecessarily tied to the builtin signature feature.
Eric Biggers (2):
fsverity: simplify handling of errors during initcall
fsverity: move sysctl registration out of signature.c
fs/verity/fsverity_private.h | 12 +++----
fs/verity/init.c | 56 ++++++++++++++++++++-------------
fs/verity/open.c | 18 +++--------
fs/verity/signature.c | 61 +++++-------------------------------
fs/verity/verify.c | 11 ++-----
5 files changed, 55 insertions(+), 103 deletions(-)
base-commit: ace1ba1c9038b30f29c5759bc4726bbed7748f15
--
2.41.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2023-07-05 21:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 21:27 Eric Biggers [this message]
2023-07-05 21:27 ` [f2fs-dev] [PATCH 0/2] fsverity: simplify initcall and move sysctl registration Eric Biggers
2023-07-05 21:27 ` [PATCH 1/2] fsverity: simplify handling of errors during initcall Eric Biggers
2023-07-05 21:27 ` [f2fs-dev] " Eric Biggers
2023-07-05 21:27 ` [PATCH 2/2] fsverity: move sysctl registration out of signature.c Eric Biggers
2023-07-05 21:27 ` [f2fs-dev] " Eric Biggers
[not found] ` <CGME20230906134906eucas1p18f20ec4bd1aa89ce9c8c6495255d442f@eucas1p1.samsung.com>
2023-09-06 13:49 ` Joel Granados
2023-09-07 4:12 ` Eric Biggers
2023-09-07 4:12 ` [f2fs-dev] " Eric Biggers
2023-09-04 18:11 ` [f2fs-dev] [PATCH 0/2] fsverity: simplify initcall and move sysctl registration patchwork-bot+f2fs
2023-09-04 18:11 ` patchwork-bot+f2fs
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=20230705212743.42180-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.