Date: Wed, 19 May 2004 16:48:05 -0700 (PDT) From: Chris Vance <cvance@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 53086 for review Message-ID: <200405192348.i4JNm5VX011376@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=53086 Change 53086 by cvance@cvance_sony on 2004/05/19 16:47:52 On second thought, I should leave the thread argument in the cap_check_cred function until I can figure out why it was added in the first place. Affected files ... .. //depot/projects/trustedbsd/sebsd/sys/kern/kern_cap.c#5 edit .. //depot/projects/trustedbsd/sebsd/sys/sys/capability.h#4 edit Differences ... ==== //depot/projects/trustedbsd/sebsd/sys/kern/kern_cap.c#5 (text+ko) ==== @@ -134,7 +134,8 @@ } int -cap_check_cred(struct ucred *cred, cap_value_t cap, int jailflags) +cap_check_cred(struct ucred *cred, struct thread *td, cap_value_t cap, + int jailflags) { int error; ==== //depot/projects/trustedbsd/sebsd/sys/sys/capability.h#4 (text+ko) ==== @@ -195,7 +195,8 @@ struct ucred; struct vnode; -int cap_check_cred(struct ucred *, cap_value_t, int jailflag); +int cap_check_cred(struct ucred *, struct thread *, cap_value_t, + int jailflag); int cap_check(struct thread *, cap_value_t); const char *capv_to_text(cap_value_t capv);
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405192348.i4JNm5VX011376>