From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Matthew Wilcox <willy@infradead.org>
Subject: [PATCH 0/2] ext4, f2fs: stop using PG_error for fscrypt and fsverity
Date: Sun, 26 Jun 2022 23:50:48 -0700 [thread overview]
Message-ID: <20220627065050.274716-1-ebiggers@kernel.org> (raw)
This series changes ext4 and f2fs to stop using PG_error to track
decryption and verity errors. This is a step towards freeing up
PG_error for other uses, as discussed at
https://lore.kernel.org/linux-fsdevel/Yn10Iz1mJX1Mu1rv@casper.infradead.org
Note: due to the interdependencies with fs/crypto/ and fs/verity/, I
couldn't split this up into separate patches for each filesystem.
Eric Biggers (2):
fscrypt: stop using PG_error to track error status
fsverity: stop using PG_error to track error status
fs/crypto/bio.c | 16 +++++++----
fs/ext4/readpage.c | 16 +++++------
fs/f2fs/compress.c | 61 ++++++++++++++++++++---------------------
fs/f2fs/data.c | 60 +++++++++++++++++++++-------------------
fs/verity/verify.c | 12 ++++----
include/linux/fscrypt.h | 5 ++--
6 files changed, 88 insertions(+), 82 deletions(-)
base-commit: 0840a7914caa14315a3191178a9f72c742477860
--
2.36.1
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 0/2] ext4, f2fs: stop using PG_error for fscrypt and fsverity
Date: Sun, 26 Jun 2022 23:50:48 -0700 [thread overview]
Message-ID: <20220627065050.274716-1-ebiggers@kernel.org> (raw)
This series changes ext4 and f2fs to stop using PG_error to track
decryption and verity errors. This is a step towards freeing up
PG_error for other uses, as discussed at
https://lore.kernel.org/linux-fsdevel/Yn10Iz1mJX1Mu1rv@casper.infradead.org
Note: due to the interdependencies with fs/crypto/ and fs/verity/, I
couldn't split this up into separate patches for each filesystem.
Eric Biggers (2):
fscrypt: stop using PG_error to track error status
fsverity: stop using PG_error to track error status
fs/crypto/bio.c | 16 +++++++----
fs/ext4/readpage.c | 16 +++++------
fs/f2fs/compress.c | 61 ++++++++++++++++++++---------------------
fs/f2fs/data.c | 60 +++++++++++++++++++++-------------------
fs/verity/verify.c | 12 ++++----
include/linux/fscrypt.h | 5 ++--
6 files changed, 88 insertions(+), 82 deletions(-)
base-commit: 0840a7914caa14315a3191178a9f72c742477860
--
2.36.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-06-27 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 6:50 Eric Biggers [this message]
2022-06-27 6:50 ` [f2fs-dev] [PATCH 0/2] ext4, f2fs: stop using PG_error for fscrypt and fsverity Eric Biggers
2022-06-27 6:50 ` [PATCH 1/2] fscrypt: stop using PG_error to track error status Eric Biggers
2022-06-27 6:50 ` [f2fs-dev] " Eric Biggers
2022-06-27 6:50 ` [PATCH 2/2] fsverity: " Eric Biggers
2022-06-27 6:50 ` [f2fs-dev] " Eric Biggers
2022-07-19 18:49 ` [PATCH 0/2] ext4, f2fs: stop using PG_error for fscrypt and fsverity Eric Biggers
2022-07-19 18:49 ` [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=20220627065050.274716-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.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.