Re: [RFC PATCH V2 07/11] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
- Subject: Re: [RFC PATCH V2 07/11] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
- From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
- Date: Thu, 5 Apr 2018 16:50:36 -0400
- In-reply-to: <2019099.0S9cVZxUkm@localhost.localdomain>
- References: <20180212094347.22071-1-chandan@linux.vnet.ibm.com> <3388885.zk0F4oSU7q@localhost.localdomain> <20180405124745.GA20556@thunk.org> <2019099.0S9cVZxUkm@localhost.localdomain>
- User-agent: Mutt/1.9.4 (2018-02-28)
On Thu, Apr 05, 2018 at 06:37:24PM +0530, Chandan Rajendra wrote:
> Sorry, I wasn't clear enough with my explaination. I actually meant to say
> that not all blocks mapped by a page might be dirty and hence only a subset
> of the dirty blocks might need to be written to the disk.
But we only track dirtiness on a per-page level. That's all the page
cache gives us. Remember, the function name is ext4_bio_write_page()
or {btrfs,xfs,ext4}_writepage() --- we will always be writing a full
page at a time.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-fscrypt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[linux Cryptography]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[IETF Sipping]
[Info Cyrus]
[ALSA User]
[Fedora Linux Users]
[Linux SCTP]
[DCCP]
[Gimp]
[Yosemite News]
[Deep Creek Hot Springs]
[Yosemite Campsites]
[ISDN Cause Codes]