From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zeniv.linux.org.uk ([195.92.253.2]:51510 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750735AbdH1ESI (ORCPT ); Mon, 28 Aug 2017 00:18:08 -0400 Date: Mon, 28 Aug 2017 05:18:05 +0100 From: Al Viro To: James Morris Cc: Mimi Zohar , Christoph Hellwig , Matthew Garrett , linux-fsdevel@vger.kernel.org, linux-ima-devel@lists.sourceforge.net, linux-security-module@vger.kernel.org Subject: Re: [PATCH v6 0/6] define new fs integrity_read method Message-ID: <20170828041805.GB21125@ZenIV.linux.org.uk> References: <1502808237-2035-1-git-send-email-zohar@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Aug 16, 2017 at 12:43:58PM +1000, James Morris wrote: > On Tue, 15 Aug 2017, Mimi Zohar wrote: > > > To resolve this locking problem, this patch set introduces a new > > ->integrity_read file operation method. Until all filesystems > > define the new ->integrity_read method, files that were previously > > measured might not be currently measured and files that were > > previously appraised might fail to be appraised properly. > > Are there any such filesystems in mainline which are not getting an > integrity_read method in this patchset? A lot - all network ones, minix/sysv/ufs, isofs/udf/efs, fat/hfs/hfs+/hpfs/affs/ntfs, ecryptfs, reiserfs, romfs, cramfs, bfs, qnx[46], etc. From mboxrd@z Thu Jan 1 00:00:00 1970 From: viro@ZenIV.linux.org.uk (Al Viro) Date: Mon, 28 Aug 2017 05:18:05 +0100 Subject: [PATCH v6 0/6] define new fs integrity_read method In-Reply-To: References: <1502808237-2035-1-git-send-email-zohar@linux.vnet.ibm.com> Message-ID: <20170828041805.GB21125@ZenIV.linux.org.uk> To: linux-security-module@vger.kernel.org List-Id: linux-security-module.vger.kernel.org On Wed, Aug 16, 2017 at 12:43:58PM +1000, James Morris wrote: > On Tue, 15 Aug 2017, Mimi Zohar wrote: > > > To resolve this locking problem, this patch set introduces a new > > ->integrity_read file operation method. Until all filesystems > > define the new ->integrity_read method, files that were previously > > measured might not be currently measured and files that were > > previously appraised might fail to be appraised properly. > > Are there any such filesystems in mainline which are not getting an > integrity_read method in this patchset? A lot - all network ones, minix/sysv/ufs, isofs/udf/efs, fat/hfs/hfs+/hpfs/affs/ntfs, ecryptfs, reiserfs, romfs, cramfs, bfs, qnx[46], etc. -- To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html