From owner-p4-projects@FreeBSD.ORG Sat Jul 9 18:59:12 2005 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 2498116A420; Sat, 9 Jul 2005 18:59:12 +0000 (GMT) X-Original-To: perforce@freebsd.org Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBD3916A41F for ; Sat, 9 Jul 2005 18:59:11 +0000 (GMT) (envelope-from bb+lists.freebsd.perforce@cyrus.watson.org) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3CC743D48 for ; Sat, 9 Jul 2005 18:59:11 +0000 (GMT) (envelope-from bb+lists.freebsd.perforce@cyrus.watson.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.13.1/8.13.1) with ESMTP id j69IxBol083457 for ; Sat, 9 Jul 2005 18:59:11 GMT (envelope-from bb+lists.freebsd.perforce@cyrus.watson.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.13.1/8.13.1/Submit) id j69IxBsZ083454 for perforce@freebsd.org; Sat, 9 Jul 2005 18:59:11 GMT (envelope-from bb+lists.freebsd.perforce@cyrus.watson.org) Date: Sat, 9 Jul 2005 18:59:11 GMT Message-Id: <200507091859.j69IxBsZ083454@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to bb+lists.freebsd.perforce@cyrus.watson.org using -f From: Robert Watson To: Perforce Change Reviews Cc: Subject: PERFORCE change 79855 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2005 18:59:13 -0000 http://perforce.freebsd.org/chv.cgi?CH=79855 Change 79855 by rwatson@rwatson_zoo on 2005/07/09 18:58:32 Catch up with FreeBSD 5.x: there's now a common "pipe_pair" object describing the results of the pipe() system call, and the label is hung off of that structure. This doesn't affect functionality in SEBSD, as only certain entry point functions used the wrong (old) structure name, but fixes valid warnings. Affected files ... .. //depot/projects/trustedbsd/sebsd/sys/security/sebsd/sebsd.c#35 edit Differences ... ==== //depot/projects/trustedbsd/sebsd/sys/security/sebsd/sebsd.c#35 (text+ko) ==== @@ -757,7 +757,7 @@ * in a pseudo filesystem. */ static void -sebsd_create_pipe(struct ucred *cred, struct pipe *pipe, +sebsd_create_pipe(struct ucred *cred, struct pipepair *pipe, struct label *pipelabel) { struct task_security_struct *tsec; @@ -1075,7 +1075,7 @@ } static int -sebsd_check_pipe_write(struct ucred *cred, struct pipe *pp, +sebsd_check_pipe_write(struct ucred *cred, struct pipepair *pp, struct label *pipelabel) { @@ -1253,7 +1253,7 @@ } static void -sebsd_relabel_pipe(struct ucred *cred, struct pipe *pipe, +sebsd_relabel_pipe(struct ucred *cred, struct pipepair *pipe, struct label *pipelabel, struct label *newlabel) { struct vnode_security_struct *source, *dest;