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=0.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FSL_HELO_FAKE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 2A963C5DF65 for ; Wed, 6 Nov 2019 21:57:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E698F217D7 for ; Wed, 6 Nov 2019 21:57:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1573077444; bh=7sER/moXfyFUCLPKujherydIaD5s2ggVDodB0ZuwT+M=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=ZAsej3qwsC2eChhaNgqPEj/K1THs+bpBvp94Rbr6OFMJPjozkMqMEcCZM47F/Z2pQ 2QA39mmeD19va7H2iTuu2JYksAaOWmVPFLkcZ/sAFpW01i3YOfK3fiwZU/NluiDdhg ylbba7r7+X25Y4xnLLm1FoT07SKnF0Q2sXgBfvHE= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727073AbfKFV5X (ORCPT ); Wed, 6 Nov 2019 16:57:23 -0500 Received: from mail.kernel.org ([198.145.29.99]:33278 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726779AbfKFV5X (ORCPT ); Wed, 6 Nov 2019 16:57:23 -0500 Received: from gmail.com (unknown [104.132.1.77]) (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 1CBAD2173E; Wed, 6 Nov 2019 21:57:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1573077442; bh=7sER/moXfyFUCLPKujherydIaD5s2ggVDodB0ZuwT+M=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=KXQ989co5T5zuGUY3xiXOlxt1pwdFozDP5LJM6vZo2e886Y7nWRvRxGCJ5d8Gl1x8 ZfJ9edkjSHIhb0xHddY3u/Q+iOI3VKdX2WifaKh6Xu7HP+S/LGsc+YPT0G7Pxttf6X ojykarHulCqdIL31fYSHwT9zDu0I366d7+7o3FeI= Date: Wed, 6 Nov 2019 13:57:20 -0800 From: Eric Biggers To: linux-fscrypt@vger.kernel.org Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-api@vger.kernel.org, David Howells , Theodore Ts'o , Jaegeuk Kim , Victor Hsieh Subject: Re: [PATCH 0/4] statx: expose the fs-verity bit Message-ID: <20191106215719.GD139580@gmail.com> Mail-Followup-To: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-api@vger.kernel.org, David Howells , Theodore Ts'o , Jaegeuk Kim , Victor Hsieh References: <20191029204141.145309-1-ebiggers@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191029204141.145309-1-ebiggers@kernel.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Tue, Oct 29, 2019 at 01:41:37PM -0700, Eric Biggers wrote: > This patchset exposes the verity bit (a.k.a. FS_VERITY_FL) via statx(). > > This is useful because it allows applications to check whether a file is > a verity file without opening it. Opening a verity file can be > expensive because the fsverity_info is set up on open, which involves > parsing metadata and optionally verifying a cryptographic signature. > > This is analogous to how various other bits are exposed through both > FS_IOC_GETFLAGS and statx(), e.g. the encrypt bit. > > This patchset applies to v5.4-rc5. > > Eric Biggers (4): > statx: define STATX_ATTR_VERITY > ext4: support STATX_ATTR_VERITY > f2fs: support STATX_ATTR_VERITY > docs: fs-verity: mention statx() support > > Documentation/filesystems/fsverity.rst | 8 ++++++++ > fs/ext4/inode.c | 5 ++++- > fs/f2fs/file.c | 5 ++++- > include/linux/stat.h | 3 ++- > include/uapi/linux/stat.h | 2 +- > 5 files changed, 19 insertions(+), 4 deletions(-) > Any more comments on this? - Eric