lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 22 Feb 2019 09:59:31 +0530 From: Chandan Rajendra <chandan@...ux.ibm.com> To: Eric Biggers <ebiggers@...nel.org> Cc: linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, linux-fscrypt@...r.kernel.org, tytso@....edu, adilger.kernel@...ger.ca, jaegeuk@...nel.org, yuchao0@...wei.com Subject: Re: [RFC PATCH 00/10] Consolidate Post read processing code On Friday, February 22, 2019 12:08:28 AM IST Eric Biggers wrote: > On Thu, Feb 21, 2019 at 07:02:03PM +0530, Chandan Rajendra wrote: > > On Wednesday, February 20, 2019 6:11:07 AM IST Eric Biggers wrote: > > > On Mon, Feb 18, 2019 at 03:34:23PM +0530, Chandan Rajendra wrote: > > > > 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. > > > > > > Is that really possible? F2FS has other functionality in its ->readpages(), > > > such as support for filesystems that use multiple block devices. > > > > > > > Hmm. I didn't know that. Thanks for pointing that out. I will read up that > > code and if it isn't really possible to get F2FS to use mpage_readpage[s](), > > then I would limit the patchset to Ext4. > > > > But we can make F2FS use the shared bio_post_read functions even if it can't use > mpage_readpage[s](), right? > Yes, that should be possible. I will include those changes in the next version of the patchset. -- chandan
Powered by blists - more mailing lists