From: Christoph Hellwig <hch@infradead.org>
To: Chandan Rajendra <chandan@linux.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
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: [PATCH V1 02/14] Consolidate "post read processing" into a new file
Date: Wed, 24 Apr 2019 07:24:23 -0700 [thread overview]
Message-ID: <20190424142423.GA12761@infradead.org> (raw)
In-Reply-To: <6353008.fQNhCuxumZ@localhost.localdomain>
On Wed, Apr 24, 2019 at 03:34:17PM +0530, Chandan Rajendra wrote:
> To clarify, Are you suggesting that a new kconfig option (say
> CONFIG_FS_READ_CALLBACKS) be provided to the user so that the following could
> occur,
>
> 1. User selects CONFIG_FS_ENCRYPTION and/or CONFIG_FS_VERITY and this causes
> CONFIG_FS_READ_CALLBACKS to be set to 'y'.
> 2. User selects CONFIG_FS_READ_CALLBACKS explicitly.
If you don't add a user description to a Kconfig entry it won't be
visible to users, but only selectable by other options. That is what
I suggest.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Chandan Rajendra <chandan@linux.ibm.com>
Cc: ebiggers@kernel.org, tytso@mit.edu,
linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@infradead.org>,
linux-fscrypt@vger.kernel.org, adilger.kernel@dilger.ca,
linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH V1 02/14] Consolidate "post read processing" into a new file
Date: Wed, 24 Apr 2019 07:24:23 -0700 [thread overview]
Message-ID: <20190424142423.GA12761@infradead.org> (raw)
In-Reply-To: <6353008.fQNhCuxumZ@localhost.localdomain>
On Wed, Apr 24, 2019 at 03:34:17PM +0530, Chandan Rajendra wrote:
> To clarify, Are you suggesting that a new kconfig option (say
> CONFIG_FS_READ_CALLBACKS) be provided to the user so that the following could
> occur,
>
> 1. User selects CONFIG_FS_ENCRYPTION and/or CONFIG_FS_VERITY and this causes
> CONFIG_FS_READ_CALLBACKS to be set to 'y'.
> 2. User selects CONFIG_FS_READ_CALLBACKS explicitly.
If you don't add a user description to a Kconfig entry it won't be
visible to users, but only selectable by other options. That is what
I suggest.
next prev parent reply other threads:[~2019-04-24 14:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 4:37 [PATCH V1 00/14] Consolidate Post read processing code Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 01/14] ext4: Clear BH_Uptodate flag on decryption error Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 02/14] Consolidate "post read processing" into a new file Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 5:35 ` Christoph Hellwig
2019-04-24 5:35 ` Christoph Hellwig
2019-04-24 10:04 ` Chandan Rajendra
2019-04-24 10:04 ` Chandan Rajendra
2019-04-24 14:24 ` Christoph Hellwig [this message]
2019-04-24 14:24 ` Christoph Hellwig
2019-04-24 14:59 ` Chandan Rajendra
2019-04-24 14:59 ` Chandan Rajendra
2019-04-24 8:31 ` Jaegeuk Kim
2019-04-24 8:31 ` Jaegeuk Kim
2019-04-24 11:01 ` Chandan Rajendra
2019-04-24 11:01 ` Chandan Rajendra
2019-04-24 12:06 ` Jaegeuk Kim
2019-04-24 12:06 ` Jaegeuk Kim
2019-04-24 14:49 ` Chandan Rajendra
2019-04-24 14:49 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 03/14] fsverity: Add call back to decide if verity check has to be performed Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 04/14] fsverity: Add call back to determine readpage limit Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 05/14] fs/mpage.c: Integrate post read processing Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 06/14] ext4: Wire up ext4_readpage[s] to use mpage_readpage[s] Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 07/14] Remove the term "bio" from post read processing Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 08/14] Add decryption support for sub-pagesized blocks Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 09/14] ext4: Decrypt all boundary blocks when doing buffered write Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 10/14] ext4: Decrypt the block that needs to be partially zeroed Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 11/14] fscrypt_encrypt_page: Loop across all blocks mapped by a page range Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 12/14] ext4: Compute logical block and the page range to be encrypted Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 13/14] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page Chandan Rajendra
2019-04-24 4:37 ` Chandan Rajendra
2019-04-24 4:37 ` [PATCH V1 14/14] ext4: Enable encryption for subpage-sized blocks Chandan Rajendra
2019-04-24 4:37 ` 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=20190424142423.GA12761@infradead.org \
--to=hch@infradead.org \
--cc=adilger.kernel@dilger.ca \
--cc=chandan@linux.ibm.com \
--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=linux-fsdevel@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.