Date: Sat, 9 Jul 2005 18:59:11 GMT From: Robert Watson <rwatson@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 79855 for review Message-ID: <200507091859.j69IxBsZ083454@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
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;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507091859.j69IxBsZ083454>