From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967072AbeAOQkT (ORCPT + 1 other); Mon, 15 Jan 2018 11:40:19 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:40826 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933790AbeAOQkR (ORCPT ); Mon, 15 Jan 2018 11:40:17 -0500 Subject: Re: [PATCH] ima: define new policy condition based on the filesystem name From: Mimi Zohar To: Christoph Hellwig Cc: linux-integrity , linux-security-module , linux-fsdevel , linux-kernel , Dongsu Park , Alban Crequy , Seth Forshee Date: Mon, 15 Jan 2018 11:40:07 -0500 In-Reply-To: <20180115162726.GB15686@infradead.org> References: <1516033236.6607.6.camel@linux.vnet.ibm.com> <20180115162726.GB15686@infradead.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 18011516-0008-0000-0000-000004C1F7D8 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18011516-0009-0000-0000-00001E555F3B Message-Id: <1516034407.6607.26.camel@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-01-15_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1801150238 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Mon, 2018-01-15 at 08:27 -0800, Christoph Hellwig wrote: > On Mon, Jan 15, 2018 at 11:20:36AM -0500, Mimi Zohar wrote: > > Some filesystems do not export the filesystem's magic number, as it is > > considered internal, private data. In other cases, the policy rule > > needs to identify a specifically mounted filesystem (eg. rootfs). > > No, it doesn't. Policies based on a file system type are complete and > utterly bogus. rootfs should not be treated any different from other > file systems. rootfs IS different than other filesystems, as other filesystems uniquely identify the underlying filesystem type.  rootfs can be a ramfs or tmpfs filesystem.  Only tmpfs supports xattrs. Mimi