From owner-freebsd-fs@FreeBSD.ORG  Mon Nov  5 13:40:53 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 10BF79C1
 for <freebsd-fs@freebsd.org>; Mon,  5 Nov 2012 13:40:53 +0000 (UTC)
 (envelope-from fluca1978@gmail.com)
Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com
 [209.85.212.54])
 by mx1.freebsd.org (Postfix) with ESMTP id B1A6C8FC0A
 for <freebsd-fs@freebsd.org>; Mon,  5 Nov 2012 13:40:52 +0000 (UTC)
Received: by mail-vb0-f54.google.com with SMTP id l1so7655880vba.13
 for <freebsd-fs@freebsd.org>; Mon, 05 Nov 2012 05:40:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:content-type;
 bh=Wznlw0koCOciiGRyRZy4en2cBWuP8Timy/end6kQUpo=;
 b=CsqUaAWek47xi1sgZQO47fSTzYEw7e78Wv2NdPgTXcLvjtB6j4wFSvmoMPXadseLj2
 Ib9a9faEkPwY4x17OyNVm+XewhetxYgFyAxhv87OuiHhoryt9NbZteOfyenmeefsB248
 XW1H3U5FpXBcQ8NRRVBb7CXXN7FOo2T74gE8eGgAy0CQ8ZiCZIHPb0O5vc718pHTq7zP
 LRuP90JKZXq9/v1BVlE34Mlj+l69qF5t31RP/3dqgN26sx3kHVfUCYPdmQGBI5P1XZW/
 x+DdMc5AAyjMt1SuVH+7CNUGi0x45RxN1l3mfv89trOThVBcLCvk+e3SQerMQghxMKkm
 CYPQ==
MIME-Version: 1.0
Received: by 10.52.77.101 with SMTP id r5mr8220358vdw.25.1352122851862; Mon,
 05 Nov 2012 05:40:51 -0800 (PST)
Sender: fluca1978@gmail.com
Received: by 10.220.2.135 with HTTP; Mon, 5 Nov 2012 05:40:51 -0800 (PST)
In-Reply-To: <CAKoxK+65_JEBR5izKZzKNyuiGw4MT1Wf7CV7DKLiN-Caj=Qikw@mail.gmail.com>
References: <CAKoxK+43SDu-gYN7+HF0-fX+Q-OdwjTC-i0_U2R1i_S95Ynjtw@mail.gmail.com>
 <CAFMmRNzZ5vma7_MP3X-rWEM7Wmaf_Mq_YAzcajoVzkbcRGunfg@mail.gmail.com>
 <CAKoxK+65_JEBR5izKZzKNyuiGw4MT1Wf7CV7DKLiN-Caj=Qikw@mail.gmail.com>
Date: Mon, 5 Nov 2012 14:40:51 +0100
X-Google-Sender-Auth: 2c7MxSJNU19XtVmubNvu9f-5Mw4
Message-ID: <CAKoxK+5xK5ZNe4ycfgOB-AhsnfstAdb-4BU+KBEiA=EBnXB2RA@mail.gmail.com>
Subject: Fwd: vop setattr and secure levels
From: Luca Ferrari <fluca1978@infinito.it>
To: freebsd-fs@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 13:40:53 -0000

Ops...I just realized I have not pushed the message to the list.
Sorry.


---------- Forwarded message ----------
From: Luca Ferrari <fluca1978@infinito.it>
Date: Tue, Oct 30, 2012 at 7:58 AM
Subject: Re: vop setattr and secure levels
To: Ryan Stone <rysto32@gmail.com>


Thanks Ryan,
therefore is it correct that pretty mich any file system operation
generates a VOP_SETATTR call and that such call will check against the
secure levels?

Luca

> The kernel build process generates some .c and .h files which define
> VOP_SETATTR, VOP_SETATTR_AP and VOP_SETATTR_APV, which are called from
> various places in the kernel.  These functions are what end up calling
> vop_setattr.