From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,T_DKIMWL_WL_HIGH,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CAFAFC433F4 for ; Tue, 28 Aug 2018 07:28:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 76E47208B9 for ; Tue, 28 Aug 2018 07:28:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="w7xHdhNL" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 76E47208B9 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727285AbeH1LSR (ORCPT ); Tue, 28 Aug 2018 07:18:17 -0400 Received: from mail.kernel.org ([198.145.29.99]:58122 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726979AbeH1LSQ (ORCPT ); Tue, 28 Aug 2018 07:18:16 -0400 Received: from localhost (c-67-160-202-76.hsd1.ca.comcast.net [67.160.202.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 69049208B8; Tue, 28 Aug 2018 07:27:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1535441277; bh=mtGK/s4bZT9pzY3icNA9XWMYJLFhRGGmW+xIkRDEMLU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=w7xHdhNLzjYeSAUTyKt0gnbY7CyXxAKUuT1veq4I0V1gLhnDEhYQjSOGtibpYblBa 2f8Yd+JqAEA0nmcMKa+9R0Nn6PG5l3o0hLz2iUuvnE4zY+n6jF4qUGh1QDebNwl2BR ypOKlYPF5KuMDiz3G4np0ursEkOssZa/8WNuxMZs= Date: Tue, 28 Aug 2018 00:27:56 -0700 From: Jaegeuk Kim To: Chao Yu Cc: Eric Biggers , Chao Yu , Dmitry Kasatkin , Michael Halcrow , linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-integrity@vger.kernel.org, linux-ext4@vger.kernel.org, Mimi Zohar , Victor Hsieh Subject: Re: [f2fs-dev] [RFC PATCH 10/10] f2fs: fs-verity support Message-ID: <20180828072756.GC29049@jaegeuk-macbookpro.roam.corp.google.com> References: <20180824161642.1144-1-ebiggers@kernel.org> <20180824161642.1144-11-ebiggers@kernel.org> <20180826173507.GC728@sol.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.2 (2017-04-18) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/27, Chao Yu wrote: > Hi Eric, > > On 2018/8/27 1:35, Eric Biggers wrote: > > Hi Chao, > > > > On Sat, Aug 25, 2018 at 01:54:08PM +0800, Chao Yu wrote: > >> On 2018/8/25 0:16, Eric Biggers wrote: > >>> From: Eric Biggers > >>> #ifdef CONFIG_F2FS_CHECK_FS > >>> #define f2fs_bug_on(sbi, condition) BUG_ON(condition) > >>> #else > >>> @@ -146,7 +149,7 @@ struct f2fs_mount_info { > >>> #define F2FS_FEATURE_QUOTA_INO 0x0080 > >>> #define F2FS_FEATURE_INODE_CRTIME 0x0100 > >>> #define F2FS_FEATURE_LOST_FOUND 0x0200 > >>> -#define F2FS_FEATURE_VERITY 0x0400 /* reserved */ > >>> +#define F2FS_FEATURE_VERITY 0x0400 > >>> > >>> #define F2FS_HAS_FEATURE(sb, mask) \ > >>> ((F2FS_SB(sb)->raw_super->feature & cpu_to_le32(mask)) != 0) > >>> @@ -598,7 +601,7 @@ enum { > >>> #define FADVISE_ENC_NAME_BIT 0x08 > >>> #define FADVISE_KEEP_SIZE_BIT 0x10 > >>> #define FADVISE_HOT_BIT 0x20 > >>> -#define FADVISE_VERITY_BIT 0x40 /* reserved */ > >>> +#define FADVISE_VERITY_BIT 0x40 > >> > >> As I suggested before, how about moving f2fs' verity_bit from i_fadvise to more > >> generic i_flags field like ext4, so we can a) remaining more bits for those > >> demands which really need file advise fields. b) using i_flags bits keeping line > >> with ext4. Not sure, if user want to know whether the file is verity one, it > >> will be easy for f2fs to export the status through FS_IOC_SETFLAGS. > >> > >> #define EXT4_VERITY_FL 0x00100000 /* Verity protected inode */ > >> > >> #define F2FS_VERITY_FL 0x00100000 /* Verity protected inode */ > >> > > > > I don't like using i_advise much either, but I actually don't see either > > location being much better than the other at the moment. The real problem is an > > artificial one: the i_flags in f2fs's on-disk format are being assumed to use > > Yeah, but since most copied flags from vfs/ext4 are not actually used in f2fs, > also 0x00100000 bit is not used now, so we can just define it now directly for > verity bit. > > Cleanup and remapping in ioctl interface for those unused flags, we can do it > latter? No, it was reserved by f2fs-tools, and I think this should be aligned to the encryption bit. Moreover, we guarantee i_flags less strictly from power-cut than i_advise. > > Thanks, > > > the same numbering scheme as ext4's on-disk format, which makes it seem that > > they have to be in sync, and that all new ext4 flags (say, EA_INODE) also > > reserve bits in f2fs and vice versa, when they in fact do not. Instead, f2fs > > should use its own numbering for its i_flags, and it should map them to/from > > whatever is needed for common APIs like FS_IOC_{GET,SET}FLAGS and > > FS_IOC_FS{GET,SET}XATTR. > > > > So putting the verity flag in *either* location (i_advise or i_flags) is just > > kicking the can down the road. If I get around to it I will send a patch that > > cleans up the f2fs flags properly...> > > Thanks, > > > > - Eric > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Linux-f2fs-devel mailing list > > Linux-f2fs-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel > >