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 linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 27 Nov 2018 19:01:28 +0530 From: Chandan Rajendra <chandan@...ux.vnet.ibm.com> To: Eric Biggers <ebiggers@...nel.org> Cc: linux-fscrypt@...r.kernel.org, linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, tytso@....edu Subject: Re: [PATCH 7/7] fsverity: Remove filesystem specific build config option On Tuesday, November 27, 2018 6:15:30 AM IST Eric Biggers wrote: > Hi Chandan, > > On Mon, Nov 19, 2018 at 10:53:24AM +0530, Chandan Rajendra wrote: > > In order to have a common code base for fsverity "post read" processing > > for all filesystems which support per-file verity, this commit removes > > filesystem specific build config option (e.g. CONFIG_EXT4_FS_VERITY) and > > replaces it with a build option (i.e. CONFIG_FS_VERITY) whose value > > affects all the filesystems making use of fsverity. > > > > Signed-off-by: Chandan Rajendra <chandan@...ux.vnet.ibm.com> > > Like the corresponding fscrypt patch, this is missing changing > > #if IS_ENABLED(CONFIG_FS_VERITY) > > in include/linux/fs.h to > > #ifdef CONFIG_FS_VERITY > > There are also references to the filesystem-specific config options in > Documentation/filesystems/fsverity.rst that need to be updated. > > I also suggest updating the Kconfig help text for CONFIG_FS_VERITY and > CONFIG_FS_ENCRYPTION to mention the supported filesystems, similar to how > CONFIG_QUOTA lists the filesystems it supports. > I will fix this one too. -- chandan
Powered by blists - more mailing lists