From: Chandan Rajendra <chandan@linux.ibm.com>
To: linux-ext4@vger.kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, ebiggers@kernel.org,
jaegeuk@kernel.org, yuchao0@huawei.com
Subject: Re: [RFC PATCH 00/10] Consolidate Post read processing code
Date: Mon, 18 Feb 2019 15:49:13 +0530 [thread overview]
Message-ID: <2149979.e1aSEps7Pq@localhost.localdomain> (raw)
In-Reply-To: <20190218100433.20048-1-chandan@linux.ibm.com>
On Monday, February 18, 2019 3:34:23 PM IST Chandan Rajendra wrote:
> This patchset moves the "post read processing" code into a file of its
> own and gets the generic do_mpage_readpge() to make use of the
> functionality provided. With these changes in place, the patchset
> changes Ext4 to use mpage_readpage[s] instead of its own custom
> ext4_readpages() function. This is done to reduce duplicity of code
> across filesystems. Based on the reviews provided for this patchset, I
> will change F2FS to use mpage_readpage[s] and post the next version of
> this patchset to linux-fsdevel mailing list.
>
> The patchset also includes patches from previous postings i.e.
> patches to replace per-filesystem encryption config options with a
> single config option that affects all filesystems making use of
> fscrypt code.
The patchset is based on fsverity_2019-01-30 branch of Eric's git tree. It can
also be obtained from "https://github.com/chandanr/linux.git
use-mpage-readpage-rfc".
>
> Chandan Rajendra (10):
> ext4: use IS_ENCRYPTED() to check encryption status
> f2fs: use IS_ENCRYPTED() to check encryption status
> fscrypt: remove filesystem specific build config option
> Consolidate "post read processing" into a new file
> fsverity: Add call back to decide if verity check has to be performed
> Introduce REQ_POST_READ_PROC bio flag
> fsverity: Add call back to determine readpage limit
> fsverity: Add call back to verify file holes
> fs/mpage.c: Integrate post read processing
> ext4: Wire up ext4_readpage[s] to use mpage_readpage[s]
>
> Documentation/filesystems/fscrypt.rst | 4 +-
> arch/mips/configs/generic_defconfig | 2 +-
> arch/nds32/configs/defconfig | 2 +-
> arch/s390/configs/debug_defconfig | 2 +-
> arch/s390/configs/performance_defconfig | 2 +-
> fs/Makefile | 3 +-
> fs/crypto/Kconfig | 5 +-
> fs/crypto/bio.c | 21 +-
> fs/crypto/crypto.c | 1 +
> fs/crypto/fscrypt_private.h | 4 +-
> fs/ext4/Kconfig | 15 -
> fs/ext4/Makefile | 2 +-
> fs/ext4/dir.c | 10 +-
> fs/ext4/ext4.h | 14 +-
> fs/ext4/ext4_jbd2.h | 2 +-
> fs/ext4/extents.c | 4 +-
> fs/ext4/ialloc.c | 2 +-
> fs/ext4/inode.c | 29 +-
> fs/ext4/ioctl.c | 4 +-
> fs/ext4/move_extent.c | 3 +-
> fs/ext4/namei.c | 18 +-
> fs/ext4/page-io.c | 9 +-
> fs/ext4/readpage.c | 444 ------------------------
> fs/ext4/super.c | 43 ++-
> fs/ext4/sysfs.c | 4 +-
> fs/f2fs/Kconfig | 12 +-
> fs/f2fs/data.c | 4 +-
> fs/f2fs/dir.c | 10 +-
> fs/f2fs/f2fs.h | 14 +-
> fs/f2fs/file.c | 10 +-
> fs/f2fs/inode.c | 4 +-
> fs/f2fs/namei.c | 6 +-
> fs/f2fs/super.c | 8 +-
> fs/f2fs/sysfs.c | 4 +-
> fs/mpage.c | 77 +++-
> fs/post_read_process.c | 128 +++++++
> fs/ubifs/Kconfig | 12 +-
> fs/ubifs/Makefile | 2 +-
> fs/ubifs/ioctl.c | 4 +-
> fs/ubifs/sb.c | 2 +-
> fs/ubifs/super.c | 2 +-
> fs/ubifs/ubifs.h | 5 +-
> fs/verity/verify.c | 12 +
> include/linux/blk_types.h | 2 +
> include/linux/fs.h | 4 +-
> include/linux/fscrypt.h | 405 ++++++++++++++++++++-
> include/linux/fscrypt_notsupp.h | 231 ------------
> include/linux/fscrypt_supp.h | 204 -----------
> include/linux/fsverity.h | 3 +
> include/linux/post_read_process.h | 21 ++
> 50 files changed, 757 insertions(+), 1078 deletions(-)
> delete mode 100644 fs/ext4/readpage.c
> create mode 100644 fs/post_read_process.c
> delete mode 100644 include/linux/fscrypt_notsupp.h
> delete mode 100644 include/linux/fscrypt_supp.h
> create mode 100644 include/linux/post_read_process.h
>
>
--
chandan
WARNING: multiple messages have this Message-ID (diff)
From: Chandan Rajendra <chandan@linux.ibm.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, linux-f2fs-devel@lists.sourceforge.net,
ebiggers@kernel.org, linux-fscrypt@vger.kernel.org,
adilger.kernel@dilger.ca, jaegeuk@kernel.org
Subject: Re: [RFC PATCH 00/10] Consolidate Post read processing code
Date: Mon, 18 Feb 2019 15:49:13 +0530 [thread overview]
Message-ID: <2149979.e1aSEps7Pq@localhost.localdomain> (raw)
In-Reply-To: <20190218100433.20048-1-chandan@linux.ibm.com>
On Monday, February 18, 2019 3:34:23 PM IST Chandan Rajendra wrote:
> This patchset moves the "post read processing" code into a file of its
> own and gets the generic do_mpage_readpge() to make use of the
> functionality provided. With these changes in place, the patchset
> changes Ext4 to use mpage_readpage[s] instead of its own custom
> ext4_readpages() function. This is done to reduce duplicity of code
> across filesystems. Based on the reviews provided for this patchset, I
> will change F2FS to use mpage_readpage[s] and post the next version of
> this patchset to linux-fsdevel mailing list.
>
> The patchset also includes patches from previous postings i.e.
> patches to replace per-filesystem encryption config options with a
> single config option that affects all filesystems making use of
> fscrypt code.
The patchset is based on fsverity_2019-01-30 branch of Eric's git tree. It can
also be obtained from "https://github.com/chandanr/linux.git
use-mpage-readpage-rfc".
>
> Chandan Rajendra (10):
> ext4: use IS_ENCRYPTED() to check encryption status
> f2fs: use IS_ENCRYPTED() to check encryption status
> fscrypt: remove filesystem specific build config option
> Consolidate "post read processing" into a new file
> fsverity: Add call back to decide if verity check has to be performed
> Introduce REQ_POST_READ_PROC bio flag
> fsverity: Add call back to determine readpage limit
> fsverity: Add call back to verify file holes
> fs/mpage.c: Integrate post read processing
> ext4: Wire up ext4_readpage[s] to use mpage_readpage[s]
>
> Documentation/filesystems/fscrypt.rst | 4 +-
> arch/mips/configs/generic_defconfig | 2 +-
> arch/nds32/configs/defconfig | 2 +-
> arch/s390/configs/debug_defconfig | 2 +-
> arch/s390/configs/performance_defconfig | 2 +-
> fs/Makefile | 3 +-
> fs/crypto/Kconfig | 5 +-
> fs/crypto/bio.c | 21 +-
> fs/crypto/crypto.c | 1 +
> fs/crypto/fscrypt_private.h | 4 +-
> fs/ext4/Kconfig | 15 -
> fs/ext4/Makefile | 2 +-
> fs/ext4/dir.c | 10 +-
> fs/ext4/ext4.h | 14 +-
> fs/ext4/ext4_jbd2.h | 2 +-
> fs/ext4/extents.c | 4 +-
> fs/ext4/ialloc.c | 2 +-
> fs/ext4/inode.c | 29 +-
> fs/ext4/ioctl.c | 4 +-
> fs/ext4/move_extent.c | 3 +-
> fs/ext4/namei.c | 18 +-
> fs/ext4/page-io.c | 9 +-
> fs/ext4/readpage.c | 444 ------------------------
> fs/ext4/super.c | 43 ++-
> fs/ext4/sysfs.c | 4 +-
> fs/f2fs/Kconfig | 12 +-
> fs/f2fs/data.c | 4 +-
> fs/f2fs/dir.c | 10 +-
> fs/f2fs/f2fs.h | 14 +-
> fs/f2fs/file.c | 10 +-
> fs/f2fs/inode.c | 4 +-
> fs/f2fs/namei.c | 6 +-
> fs/f2fs/super.c | 8 +-
> fs/f2fs/sysfs.c | 4 +-
> fs/mpage.c | 77 +++-
> fs/post_read_process.c | 128 +++++++
> fs/ubifs/Kconfig | 12 +-
> fs/ubifs/Makefile | 2 +-
> fs/ubifs/ioctl.c | 4 +-
> fs/ubifs/sb.c | 2 +-
> fs/ubifs/super.c | 2 +-
> fs/ubifs/ubifs.h | 5 +-
> fs/verity/verify.c | 12 +
> include/linux/blk_types.h | 2 +
> include/linux/fs.h | 4 +-
> include/linux/fscrypt.h | 405 ++++++++++++++++++++-
> include/linux/fscrypt_notsupp.h | 231 ------------
> include/linux/fscrypt_supp.h | 204 -----------
> include/linux/fsverity.h | 3 +
> include/linux/post_read_process.h | 21 ++
> 50 files changed, 757 insertions(+), 1078 deletions(-)
> delete mode 100644 fs/ext4/readpage.c
> create mode 100644 fs/post_read_process.c
> delete mode 100644 include/linux/fscrypt_notsupp.h
> delete mode 100644 include/linux/fscrypt_supp.h
> create mode 100644 include/linux/post_read_process.h
>
>
--
chandan
next prev parent reply other threads:[~2019-02-18 10:18 UTC|newest]
Thread overview: 57+ 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 ` 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 ` [f2fs-dev] " Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 02/10] f2fs: " Chandan Rajendra
2019-02-18 10:04 ` 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 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 04/10] Consolidate "post read processing" into a new file Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-19 23:22 ` Eric Biggers
2019-02-19 23:22 ` [f2fs-dev] " Eric Biggers
2019-02-19 23:22 ` Eric Biggers
2019-02-21 12:51 ` Chandan Rajendra
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-18 10:04 ` [f2fs-dev] " Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-19 23:26 ` [f2fs-dev] " Eric Biggers
2019-02-19 23:26 ` Eric Biggers
2019-02-21 12:54 ` [f2fs-dev] " Chandan Rajendra
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-18 10:04 ` [f2fs-dev] " Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-20 0:21 ` [f2fs-dev] " Eric Biggers
2019-02-20 0:21 ` Eric Biggers
2019-02-21 13:03 ` [f2fs-dev] " Chandan Rajendra
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 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 08/10] fsverity: Add call back to verify file holes Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-20 0:35 ` Eric Biggers
2019-02-20 0:35 ` Eric Biggers
2019-02-21 13:05 ` Chandan Rajendra
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 ` 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:04 ` Chandan Rajendra
2019-02-18 10:19 ` Chandan Rajendra [this message]
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-19 21:17 ` [f2fs-dev] " Eric Biggers
2019-02-19 21:17 ` Eric Biggers
2019-02-21 13:29 ` Chandan Rajendra
2019-02-21 13:29 ` Chandan Rajendra
2019-02-20 0:41 ` Eric Biggers
2019-02-20 0:41 ` Eric Biggers
2019-02-21 13:32 ` Chandan Rajendra
2019-02-21 13:32 ` Chandan Rajendra
2019-02-21 18:38 ` Eric Biggers
2019-02-21 18:38 ` Eric Biggers
2019-02-22 4:29 ` Chandan Rajendra
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=2149979.e1aSEps7Pq@localhost.localdomain \
--to=chandan@linux.ibm.com \
--cc=adilger.kernel@dilger.ca \
--cc=ebiggers@kernel.org \
--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 \
--cc=yuchao0@huawei.com \
/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.