From: Eric Biggers <ebiggers@kernel.org>
To: Chandan Rajendra <chandan@linux.ibm.com>
Cc: tytso@mit.edu, linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, adilger.kernel@dilger.ca,
jaegeuk@kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [RFC PATCH 08/10] fsverity: Add call back to verify file holes
Date: Tue, 19 Feb 2019 16:35:07 -0800 [thread overview]
Message-ID: <20190220003507.GH12177@gmail.com> (raw)
In-Reply-To: <20190218100433.20048-9-chandan@linux.ibm.com>
On Mon, Feb 18, 2019 at 03:34:31PM +0530, Chandan Rajendra wrote:
> readpage() implmentations zero out part of the page-cache page mapping a
> file hole. This commit adds a call back to "struct fsverity_operations"
> which readpage() can invoke to verify the file hole.
I don't see why this is needed. Since now CONFIG_FS_VERITY will be a bool,
can't you just call fsverity_verify_hole() directly?
>
> Signed-off-by: Chandan Rajendra <chandan@linux.ibm.com>
> ---
> fs/ext4/super.c | 1 +
> include/linux/fsverity.h | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 4493ddc357c6..94e0d4b56653 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -1459,6 +1459,7 @@ static const struct fsverity_operations ext4_verityops = {
> .read_metadata_page = ext4_read_verity_metadata_page,
> .verity_required = ext4_verity_required,
> .readpage_limit = ext4_readpage_limit,
> + .check_hole = fsverity_check_hole,
> };
> #endif /* CONFIG_FS_VERITY */
>
> diff --git a/include/linux/fsverity.h b/include/linux/fsverity.h
> index fc8113acbbfe..8bc28b07d550 100644
> --- a/include/linux/fsverity.h
> +++ b/include/linux/fsverity.h
> @@ -20,6 +20,7 @@ struct fsverity_operations {
> struct page *(*read_metadata_page)(struct inode *inode, pgoff_t index);
> bool (*verity_required)(struct inode *inode, pgoff_t index);
> loff_t (*readpage_limit)(struct inode *inode);
> + bool (*check_hole)(struct inode *inode, struct page *page);
> };
>
> #ifdef CONFIG_FS_VERITY
> --
> 2.19.1
>
next prev parent reply other threads:[~2019-02-20 0:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 10:04 [RFC PATCH 00/10] Consolidate Post read processing code Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 01/10] ext4: use IS_ENCRYPTED() to check encryption status Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 02/10] f2fs: " Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 03/10] fscrypt: remove filesystem specific build config option Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 04/10] Consolidate "post read processing" into a new file Chandan Rajendra
2019-02-19 23:22 ` Eric Biggers
2019-02-21 12:51 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 05/10] fsverity: Add call back to decide if verity check has to be performed Chandan Rajendra
2019-02-19 23:26 ` Eric Biggers
2019-02-21 12:54 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 06/10] Introduce REQ_POST_READ_PROC bio flag Chandan Rajendra
2019-02-20 0:21 ` Eric Biggers
2019-02-21 13:03 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 07/10] fsverity: Add call back to determine readpage limit Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 08/10] fsverity: Add call back to verify file holes Chandan Rajendra
2019-02-20 0:35 ` Eric Biggers [this message]
2019-02-21 13:05 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 09/10] fs/mpage.c: Integrate post read processing Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 10/10] ext4: Wire up ext4_readpage[s] to use mpage_readpage[s] Chandan Rajendra
2019-02-18 10:19 ` [RFC PATCH 00/10] Consolidate Post read processing code Chandan Rajendra
2019-02-19 21:17 ` Eric Biggers
2019-02-21 13:29 ` Chandan Rajendra
2019-02-20 0:41 ` Eric Biggers
2019-02-21 13:32 ` Chandan Rajendra
2019-02-21 18:38 ` Eric Biggers
2019-02-22 4:29 ` Chandan Rajendra
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=20190220003507.GH12177@gmail.com \
--to=ebiggers@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=chandan@linux.ibm.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).